-
Notifications
You must be signed in to change notification settings - Fork 310
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
Use Netlify CMS as the editing UI #203
Conversation
That looks/works awesome! For running Jekyll locally from docker compose I had to add: I like the idea of supporting using netlify-cms locally in addition to potentially adding the github backend. |
Okay, I'll break this out into issues to track the work. I managed to get site settings added to the editor UI this morning, which was surprisingly easy. |
This was necessary to support editing in Netlify CMS. See #207. I've added a line in index.html that should provide backwards compatibility. Note that this commit breaks editing. This could be fixed as well, but since it's being removed as part of the Netlify CMS milestone, I haven't included it here.
license, category, maintainer, maintainer_email
…nd always show them Closes #208
Let's get a version that just works locally for now, and keep Netlify bits for a future enhancement. Getting some version of this and #213 committed makes further work much easier. We are hoping to make our fork for OpenDataPhilly some time in the next couple weeks - and want to finish these (and other) big changes first. |
Okay, I've created a P.S. Where are you planning to host OpenDataPhilly? Are you up for using Netlify? |
Following on from #198
I've been really impressed with Netlify CMS. It worked out of the box with JKAN. You just add a configuration file, where you define the schema of your collections, and it generates a nice looking editing user interface.
It also ticks a lot of boxes for us:
The only downside I can think of is that it's a single page app, so it requires JavaScript to run.
This pull request is just a demo. It's currently configured to run locally using the local backend feature. To try it out:
netlify-cms
)npx netlify-cms-proxy-server
(requires Node.js)bundle exec jekyll serve
localhost:4000/manage/
You should then be able to save changes to your local files, rather than to the repository on GitHub. When it's running in production we would remove the
local_backend
config option, and you would authenticate via GitHub.If we agree this is the way forward, some of the remaining steps, I'd imagine, would be:
_data/schemas/default.yml
Thoughts?