chore: copy over demo files, lightly abstract

[drewbo]

Changes proposed in this pull request:

• copy over demo files, lightly abstract

Security considerations

None

[apburnes]

Should we switch to an lts version?

[apburnes]

I think we can remove this platform specific env variable process.env.VERCEL_PROJECT_PRODUCTION_URL?

[apburnes]

Could probably remove platform specific env vars like:

Suggested change

	const NEXT_PUBLIC_SERVER_URL = process.env.VERCEL_PROJECT_PRODUCTION_URL
	? `https://${process.env.VERCEL_PROJECT_PRODUCTION_URL}`
	: undefined || process.env.NEXT_PUBLIC_SERVER_URL || 'http://localhost:3000'
	const NEXT_PUBLIC_SERVER_URL = process.env.NEXT_PUBLIC_SERVER_URL || 'http://localhost:3000'

[apburnes]

This first run commit has a lot of boilerplate but added a few comments based on a few env vars that are not applicable to the cg platform. As we continue to flush out this editor experience, do you have any thoughts on how we can we incorporate unit and integration testing along with UI deviations?

With this initial prototype, do you have any concerns that could manifest into future impediments while managing and upgrading this product? Are they're an possible abstractions we could leverage to facilitate future development?

All together this is a exciting development with fairly low level of effort to prototype. This is 🥇 work.

[drewbo]

As we continue to flush out this editor experience, do you have any thoughts on how we can we incorporate unit and integration testing along with UI deviations?

I haven't done a deep look into their test suite but purely by volume, I'd assume the built-in payload components are decently well tested. I think we should focus more on e2e testing with cypress/playwright to assure that our primary UX pathways do what we want

With this initial prototype, do you have any concerns that could manifest into future impediments while managing and upgrading this product? Are there any possible abstractions we could leverage to facilitate future development?

I'm going to ask @sknep to review a bit more because I do have a gnawing concern that there will be some awful UX or model pattern that we'll need to build a big workaround for but I haven't seen much of anything yet (and the one I did find can actually be fixed with a label change). I'm leaning more and more toward multi-tenancy which will make the initial build and compliance journey more difficult but I think will have a huge payoff when it comes to upgrading.

I'm going to add one more piece to this prior to merge (customizable Post type) just to map out that concept and then I think we can make more decisions about what to do with this

[sknep]

this isn't a key to worry about, is it?

[sknep]

not worth the edit but just in case you end up editing anyways:

Suggested change

	- Avoid login through Github
	- Avoid login through GitHub