switch out decap for static-cms #53
Open
+10
−14
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
update index
✅ Deploy Preview for cyf-pd ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
I think these are distinct post types not params on posts
not sure what they do, but they don't create sorting options
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PD vols would like Grammarly to work in the CMS, which is not unreasonable.
Decap 3 works ok now but only on top level editable fields. Any nested block is still inert. It feels like it might be easier to switch out the CMS for this fork than get into the weeds with the grammarly API. I'm not massively inclined to learn it.
I'm opening this exploratory PR to see how it goes. Static CMS is a fork of netlify-cms, as is decap
Addressing #36