Cloning for new events

[SQLDBAWithABeard]

To discuss methods, solutions for cloning the website for new events

[Stuart-Moore]

Are you expecting each event to have it's own site or just it's own page on the main site?

For the former, maybe look at a simple Jekyll template. Easily cloned, just edit the Markdown, and off you go. This is how we did Data Platform Discovery Day - https://github.com/dataplatformdiscoveryday/dataplatformdiscoveryday.github.io - all content is in the _posts folder. Design isn't great, but that's a limitation of me rather than the platform. Free hosting on github, just need to buy the domain name.

If the latter, then I'd suggest something similar using templates and allow people to populate it with snippets. Keep the type/amount of content simple and limited to avoid issues. Again, Github and a pipeline would make it easy to maintain and control.

[way0utwest]

Is there an expectation that most of the site is not the same with data driven elements on it? I would expect the overall look feel of each site should be similar, with some level of customization.

My initial feeling is that we ought to keep some general template for the site with tokens for some elements. As an example:

• event name
• event date
• event location

We would then copy rows from the template table(s) to some event table and replace tokens with information that is entered by the organizer.

If we look at more static pages for each event, which certainly lowers resources, I would still store the code the pages in a store, read/update as needed, and then rewrite pages.

[stephlocke]

We built a hugo site template for individual events https://github.com/satRdays/satRday_site_template These all get subdomains and hosting on netlify under their open source plan

[SQLDBAWithABeard]

completed with #149