Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migrate to Greenwood + AWS Adapter #32

Open
thescientist13 opened this issue Nov 23, 2023 · 0 comments · May be fixed by #44
Open

Migrate to Greenwood + AWS Adapter #32

thescientist13 opened this issue Nov 23, 2023 · 0 comments · May be fixed by #44
Assignees
@thescientist13
Labels
enhancement

Comments

@thescientist13
Copy link
Contributor

thescientist13 commented Nov 23, 2023 •
edited
Loading

Since Greenwood can easily operate to serve exclusively API endpoints, with a (soon to be coming) ProjectEvergreen/greenwood#1142, it would be nice to invert the development model here to be standards based instead of owned by Architect.

As its own ticket, perhaps the Greenwood frontend could act as a local only admin dashboard? And then maybe all content could be hosted in PlanetScale, including Contentful?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@thescientist13 thescientist13

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feature/issue 32 migrate to greenwood AnalogStudiosRI/api
1 participant
@thescientist13