Colby Fayock

@Azanul sounds good to me! would love to hear your thoughts then before moving forward including the work that needs to be done and what you see as the 2...

Got it, I would still like 2 issues to have concise details around the problems each are solving so that we're not creating 2 PRs for the sake of creating...

from what i understand i think thats part of it. i was also under the impression there would be more attributes than classes, such as "roles" and such, but i...

yeah haha that might be it! :D i trust whatever you find out through your research

i don't think it makes sense to create a new PR for every component, but if you'd like to break up the work another way, such as one for pages...

let's do pages vs components as that sounds a little bit like a more logical difference /src/pages vs /src/components that sound good?

yup, sounds great

I did some parsing in my spacejelly.dev site that can also use as inspiration: https://github.com/colbyfayock/spacejelly.dev/blob/main/src/pages/posts/%5Bslug%5D.js#L128 https://github.com/colbyfayock/spacejelly.dev/blob/28cff627a9dbd1f31aee667944a9831328277a7d/src/lib/parse.js#L44

if any work here is done it should be in a way that makes it easy to add new configurations and transformations in a plugin-able way

sounds great to me!