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.

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

Allow completely removing the CMS on build #199

Open
jimafisk opened this issue Jun 22, 2022 · 0 comments
Open

Allow completely removing the CMS on build #199

jimafisk opened this issue Jun 22, 2022 · 0 comments
Labels
cms Git-backed content editing

Comments

@jimafisk
Copy link
Member

It would be great to implement a --cms flag for the CLI tool that we could set to false to completely remove all CMS files from build.

This would be useful not only for folks who want a simple SSG without a CMS, but also for people who want to make edits only on a protected URL and do prod deployments without editing capabilities. For example, you could have a site like edit.mysite.com that sits behind GitLab auth that users make content changes to, then merging into the main branch could kick off a plenti build --cms=false build that deploys to mysite.com that is publicly available. This would increase both the security and performance of the prod site.

We would have to change the static import statements in router.svelte to dynamic imports and account for the default user and adminMenu props that end users could potentially be using in their apps.

@jimafisk jimafisk added the cms Git-backed content editing label Jun 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cms Git-backed content editing
Projects
None yet
Development

No branches or pull requests

1 participant