netlify / netlify-cms-www Goto Github PK

Docs file content is stored in the netlify-cms code repo, then pulled into this site using Markdown Magic. This means that visitors may read docs on this site, at netlifycms.org, or directly within the repo, either in GitHub or a local clone.

This causes problems when docs link to each other, as referenced in netlify-cms issue #471. The latest comments detail the current setup and possible sources for a solution.

With the 0.4.0 release, the CMS's UI changed a bit — we should update the video on the homepage to reflect that.

I can take care of this, but just wanted to create the issue for future reference. 👍

I think there is something wrong with your site's header.

The "Fork Me on GitHub" verbiage in the header button may not be ideal, and should perhaps be changed to "Contribute on GitHub", or even just a GH icon.

Original issue raised in this PR: decaporg/decap-cms#714

We need a favicon for the site 👍

Here's my experience coming to Netlify CMS & Netlify in general.

1. See interesting link on Hacker News & takes me to setting up a demo site. Demo impresses me! I want more!
2. Check out Netlify & see it'll do all this for me & for cheap! There is a static site generator called Hugo & it drops all my files into GitHub. Awesome. How on earth does this all work together?

@biilmann explained the process well on Gitter, so maybe a graphic or just a similar explanation could be used. Here's how I understand it.

• Netlify CMS gives you a nice web UI to edit your content without code
• GitHub (or another Git repo) is where your content is stored for you & versioned
• Hugo/Jekyll or any other (Node/Ruby/Go) static site generator of your choice can be used to copy your repo locally & create a static site from the content
• Netlify is a service that will track your GitHub repo & run your static site generator process for you whenever you make changes. It will also host your static site.

Currently docs sections are positioned via numbers in each entry, so multiple entries must be updated to change the order. Instead we should introduce a settings collection with a list of relations so sections can be re-ordered via drag and drop.

Migration from a previously reported issue in the other repo. I also ended on the broken link from this intro page. I am still reading the docs, so I'm not sure what could be the correct resource.