Project Clay

[hacdias]

Warning

This is an issue where I am mostly thinking. It does not mean that I am going to fully work towards making Eagle completely usable by others. At the moment, my setup is quite tightly connected, and disconnecting pieces may be complicated.

What is Project Clay?

Project Clay is the codename for what is being tracked in this issue, which are two main things:

1. Making Eagle usable by others.
2. Implement functionalities that would make it a better citizen of the IndieWeb.

I have always marketed Eagle as a personal-only project, and I have always been clear about not supporting other people's use cases. However, the past time I have been thinking that maybe returning to Hugo was not the smartest decision, and that maybe I wish I had stayed with my own full-blown CMS.

What would need to be done?

The items below do not necessarily constitute a MVP.

• --configDir directory. This directory must contain eagle.yaml for configuration and the rest will be handled by Eagle. Remove DataDirectory (use bolt/).
• make sure rebuilds happen after linking, bookmarks, etc
• Decouple interface or make it clear how to make it work with your own templates. Maybe create eagle directory for eagle configuration stuff inside SourceDirectory, like better templates.
• Re-add support for Webmention.
  • Also support without relaying on webmention.io
• Re-add support for Micropub.
• Re-add support for ActivityPub.
• Plugin system to let others add functionality.
• No downtime restart to reload settings and whatnot.
• Daily Squashed Commits #197

If I decide to stop using Hugo again:

• Understand what features from Hugo (especially "given" things such as shortcodes) are necessary.
• Must: have a build command that statically outputs all the content. Good for preservation and peace of mind. It does not need to be blazingly fast as Hugo. It just needs to be able to do its job.

Current Hugo Wishlist

• Add ability to generate per-{year, month, day} archives gohugoio/hugo#448
• File system paths would match URLS (e.g., could create /about/external-links/index.md without having to make about a section, as well as multi-level sections)