Wildernetic Oracle

Meta

I have chosen to deploy a Lektor CMS with a Git-based workflow.

Component Breakdown

• Lektor CMS: This is the core of the architecture, a static site generator with a user-friendly admin interface. It allows you to manage content through a graphical interface, making it easy to create and update entries for your cards and book sections without needing to write raw code.
• Git: Lektor stores its content in a flat-file database, which is perfectly suited for version control using Git. This means every change you make to the content is tracked and can be reverted if needed.
• Forgejo: This serves as the remote Git repository. You have created an organization named "Wildernetic" and a repository named "oracle-book" on your Forgejo instance. This is where your Lektor project files are stored and version-controlled.
• Hosting: The content will be served from an HTTP server at the DNS entry https://oracle.wildernetic.com/. Lektor will build the static HTML files and output them to a specified path on the server for deployment.

This architecture provides a robust system that combines the ease of a CMS with the power of version control, perfectly aligning with your goal of exploring, refining, and querying your content before publishing.