I Don't Like Existing CMS Options, So I'm Building a New One

Here is a complete incomplete list of all most CMS solutions:

• 
  
  

  I sure have. And that's where the idea came from: Why not add another to that list?

  
  
  

  
  
  
  The Current Ecosystem
  

  
  
  

  and
  
  (Photo by Ashkan Forouzani on Unsplash)

  
  
  

  As I stated before, it all revolves around the principle of modularity and composability. Small, independent pieces that fit nicely together, like a puzzle. This core detail will help shape the future of this and hopefully many more CMS solutions.

  
  
  

  Let's look at what core modules I'm planning to feature:

  
  
  
  
  

  • Objects: Small key-value pairs of any standard data type: strings, numbers, booleans, arrays, and of course, other objects. This provides the foundation for anyone to create any data type.

  
  

  • Documents: Documents are essentially larger objects, with special formatting and extra features. Documents are made up of a custom template or schema, which define what data fields will exist. Data can be entered for each of those fields, specific to their own data type.

  
  

  • Media: Simply put, file uploads. A perfect place to store images, videos, documents, and more all with metadata and attributes.

  
  

  • Widgets: Widgets are pieces or sections of a website. They can be considered as documents with a twist: they have a custom renderer. This renderer enables a widget to be converted from a component template (ie. Astro, React, Vue, Svelte) into rendered HTML by the framework of your choice.

  
  

  • Pages: Pages work will with widgets, allowing you to put together documents and widgets to form a page, perfect for any modern site. Pages also can be rendered to output page previews with whatever technology stack you are currently using.

  
  
  
  
  

  These modules will provide the foundation for many new and unique data structures defined by the developers, all of which are extendable via plugins.

  
  
  

  
  
  
  What's In It For Me?
  

  
  
  

  This is an ambitious project, and I'm well aware of the challenges that lay ahead. I've decided to document every step of this journey openly, from the initial architecture decisions to the inevitable roadblocks I'll face. My experience has taught me that even failed projects can be valuable learning opportunities for the developer community. When I was starting out, I learned lots of valuable lessons from other developers who were open about their struggles and decision-making processes.

  
  
  

  I'm putting my heart into this project because I genuinely believe it can succeed. My goal isn't to build another CMS, but to demonstrate that we can challenge the status quo when we see problems worth solving, even if we are the only ones with that problem (honestly, if we've faced a problem before, I can almost guarentee someone else has faced that same problem ;) ). If this CMS takes off, that's fantastic. But even if it only serves to inspire other developers to tackle ambitious projects they care about, or helps someone else build a better solution down the line, I'll consider that a win. After all, every innovation in our field started with someone looking at a problem and thinking "I believe there's a better way." Which leads me to the actual project.

  
  
  

  
  
  
  Introducing LuxeCMS
  

  
  
  

  The project has taken the name of LuxeCMS, and will be a 100% open-source project.

  
  
  

  and let's chat!

  
  
  

  I'm excited for this opportunity to grow as a developer, and to build a community of like-minded individuals to bring something new to the world! If you've experienced pain points of existing CMS solutions or are excited about this project, comment down below!

  
  
  

  If you want to follow updates on LuxeCMS, consider following us on X/Twitter.

  Vollständiger Original-Bericht

  Ausführliche Details, Code-Beispiele & Hersteller-Stellungnahme auf dev.to.

  ↗ Original-Artikel auf dev.to lesen