Site Class / ontology

[joepio]

Building websites with AtomicServer should be as easy as possible. We already have an Article class which we use on some pages in production (example). We also have an argu-site which I made when migrating a bunch of our Argu customers to AtomicServer. This Class has some issues:

• The URL is odd
• It's tightly coupled to Argu and this github project

Customizability vs interoperability

• We want developers to be able to very easily make any changes to classes & properties
• We want to encourage re-use of classes and properties to improve interoperability

How can get both:

• We host standard classes (e.g. /classes/Site, /classes/MenuItem /classes/Article)
• We host the properties (e.g./properties/menu-item)
• User clones the classes, turning them into local classes.

Todo

• Site class
• GUI for this class
• menu-item list of pages to link to
• redeploy-link item that when opened, triggers a redeploy
• default-image for seo / socials
• default-description
• social-links, maybe just add a bunch of links and assume some icons
• mapping onto a config.toml from Zola might make sense
• tags. We already have tags in Table class
• Add an Ontology for websites? Or stick to one class?
• Update atomic-sveltekit-demo to use this new class, update readme.

[Polleps]

We could make a create-template package that allows users to do things like npm create @tomic/template
Since these are just executable scripts we can do things like generate a users ontologies and have some options like what framework to use.

[joepio]

Polle went for a very different approach in #952, closing