Why Automad No Longer Uses Any Frontend or Backend Framework

March 26, 2025  — 
 Automad, Web, Dev

Long-term open-source projects, such as Automad, require stability and independence from third-party libraries. Relying on external frameworks introduces risks that can impact maintainability, long-term support, and overall project longevity.

Removing dependencies on jQuery and UIkit in preparation for Automad 2 was a painful process that ultimately led to an entire re-write. This transition required significant effort to replace legacy implementations with modern, native solutions while ensuring feature parity and long-term stability.

The Appeal of Frameworks

In my day job as a software engineer, I work extensively with React and Svelte, along with their respective metaframeworks, Next.js and SvelteKit. These tools provide significant advantages in modern development workflows, including:

  • Support for teams with varying skill levels
    • Rapid development
      • Easy onboarding
        • Common industry knowledge

          However, these benefits come with a hidden cost: dependency on the decisions of framework authors.

          The Hidden Costs of Framework Dependency

          When adopting a frontend or backend framework, you are not just using a tool — you are also agreeing to follow the evolution of that tool. This means:

          • Breaking changes
            • Shifting paradigms
              • Ecosystem lock-in
                • Uncertain longevity

                  For a project like Automad, which aims for long-term maintainability and minimal dependencies, these issues present a real challenge.

                  The Case for Native Solutions

                  Instead of relying on third-party frameworks, Automad embraces native web technologies where possible. Native solutions, such as Web Components, provide:

                  • Stable APIs
                    • No external dependencies
                      • Built-in browser support
                        • Full component lifecycle management

                          Despite these advantages, Web Components have often been met with skepticism, primarily due to negative perceptions perpetuated by framework maintainers. Many articles critiquing Web Components come from authors with vested interests in framework adoption.

                          That being said, using smaller libraries and packages is not a problem as long as they can be easily isolated and replaced. Unlike monolithic frameworks, modular libraries provide flexibility without locking a project into a particular ecosystem or paradigm.

                          Conclusion

                          Automad's decision to move away from frontend and backend frameworks is driven by a long-term vision of stability, maintainability, and independence. While frameworks provide immediate benefits, they also introduce long-term risks that are incompatible with the goals of an open-source CMS that seeks to remain lightweight, flexible, and future-proof. By leveraging native solutions, Automad ensures a stable foundation that is not subject to the shifting priorities of third-party framework maintainers.

                            Related Pages

                          The Inflation of "Security Researchers" and Its Consequences for Open Source
                          March 31, 2025
                           Security, Web

                          As an open-source maintainer, I deeply appreciate the importance of cybersecurity. Security is a shared responsibility — both for users who rely on software to be secure and for developers who build and maintain open-source projects. Responsible vulnerability reporting strengthens the ecosystem, helping us all build better, safer software. However, in recent years, the term "security researcher" has been stretched to the point where it is becoming counterproductive.

                          Setting Up Neovim for Automad Theme Development
                          March 23, 2025
                           Automad, Neovim, Dev

                          As the developer of Automad, I wanted to make working with Automad themes in Neovim as smooth as possible. Automad has its own templating syntax, so I created tree-sitter-automad to provide proper syntax highlighting. Since it’s not yet an official parser, you need to manually register it in Neovim. To speed up template writing, you can also add custom snippets using LuaSnip. Here's how to set everything up.

                          How to Create a Multilingual Website Using Automad 2
                          March 19, 2025
                           Automad, Web

                          Creating a multilingual website can significantly expand your reach and user engagement by catering to a global audience. Automad 2, a lightweight CMS that prides itself on simplicity and flexibility, makes it easy to create and manage multilingual websites.

                          Fancy Open-Graph Images with Automad
                          December 15, 2024
                           Automad, Web

                          Starting with the latest alpha 16 of Automad 2, Open-Graph images are rendered automatically for every page on the fly. Colors can be customized, a logo can be added. No further setup needed. 

                          Automad 2.0 Alpha
                          October 4, 2024
                           Automad, Web

                          After a long development process, the stable release of Automad 2 is getting closer. While many aspects of the system have evolved, the core vision remains the same — delivering a fast, flexible, and file-based content management system with a powerful templating engine.