Replies: 1 comment 4 replies
-
|
Deploy previews are done with the editorial workflow and deploy preview links in Netlify/Decap CMS. Sveltia CMS will implement the feature in v2.0. It’s overkill though, especially when you’re the only user of the CMS. This is a relevant issue, and I plan to solve it in Sveltia CMS: |
Beta Was this translation helpful? Give feedback.
-
|
@kyoshino , do you have a plan of how this functionality would work on a technical level? The discussion in the Decap CMS issue revolves around UI/UX but not that much around technical implementation. |
Beta Was this translation helpful? Give feedback.
-
|
There are actually a bunch of issues with the editorial workflow in Netlify/Decap CMS, not just UX. I haven’t started any work, but I assume the implementation won’t be easy.
|
Beta Was this translation helpful? Give feedback.
-
|
I noticed pagescms.org (same family as Decap / Sveltia ) uses a GitHub app on Cloudflare to authenticate multiple users. I briefly tried to replicate the, but didn't get that far. It's a small hurdle (emphasis small) to have additional editors create GitHub users that you can share your repo with - that's how I solved it for now. |
Beta Was this translation helpful? Give feedback.
-
|
@mimecine a Git gateway is planned for v2.0 or later. See the Future section in the README.
Ouch... Indeed... 😅 Are you interested to discuss and brainstorm alternatives to the full editorial workflow? When I think of it, I think the bottom line often comes down to being able to preview draft content in a production-like environment and easily validate it so it replaces the prod content. I am almost tempted to hack the i18n feature to create a 'draft' language that my SSG only builds on non-prod environments... That is a hack and it would definitely feel like it with the current UI but I think it would solve 90% of the problem I am trying to solve. Anyway, I'll try and keep you updated if I come up with a pragmatic solution. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey.
I am starting to look at how to manage git(hub) branches from the CMS.
I am guessing this is not among the top priorities for Sveltia but I just want to open the discussion and share what I build. I think I can build most things independently and it can be integrated when it is pertinent to do so.
The reason:
All static hosting providers automatically handle multiple environments in sync with git branches. So it is very convenient to have a staging branch in parallel with the production branch to edit content and preview it before making it live. To handle that process in a fluid way, the staging branch has to be merged into the main branch. This cannot be done from Github's frontend. We have to create a pull request to be able to merge. This is meant for disposable "feature branches", not for parallel "environment branches".
This leaves a huge gap in the User Experience.
The user either misses out on the super practical (and free) multi-environment feature of all hosting providers or has to play with git locally which largely defeats the purpose of having an online CMS directly connected to Github or another git platform.
The MVP:
I'll create a small piece of interface to list available branches and their status (behind or ahead of the main branch) and a
mergebutton if fast forward is possible.To display this interface in the admin UI, my plan is to mount the Sveltia app on a specific html element instead of letting it take over the whole page.
Possible Inspiration
Keystatic has some branch management built in: Video
Just for reference
As a starting point, I played 5 minutes in the console and was able to list my branches with this piece of code.
Beta Was this translation helpful? Give feedback.
All reactions