Create a way to store data within the repository

[RyannosaurusRex]

The long-term goal for this project is to create a blog, pages for TriDev members (to create backlinks to their own sites by contributing a PR), and to store other information to generate the static site (sponsor list, other meetup and community links, etc).

Most likely we need these entries in Markdown/.md files that we can read with yaml headers for other metadata, but JSON will likely also work.

The benefit of Markdown files as data in a folder is that it will be easier to edit long-form content directly in markdown, and we can make a "postPage" component that will render the markdown, similar to a Wordpress type post.

[mackenly]

Adding as research:

This post seems to do a good job at explaining the various options for building a blog with Svelte. Using mdsvex seems to be the key takeaway.
https://joshcollinsworth.com/blog/build-static-sveltekit-markdown-blog

[RyannosaurusRex]

I've also used NetlifyCMS before, that is a running app that sits with your static webapp that stores the content as JSON, and when you make changes in the UI, on the backend it will create a PR and update the repo with the data in the JSON files.

https://www.netlifycms.org/

[RyannosaurusRex]

https://joshcollinsworth.com/blog/build-static-sveltekit-markdown-blog

One thing I think we should stay away from is putting Svelte components in the markdown content. I did this with React previously, and it instantly makes the markdown content not portable. Probably not a big deal for a page or two, but if we start a blog or something and start getting more content, we probably don't want our content to be stuck with svelte forever most likely.