Shawn Erquhart

Solid response, thanks for that! This would work, but basically boils down to an extra build step where the order parameter is added to each frontmatter based on filename and...

Agreed. There's a similar issue with more info, and the real challenge is outlined in a comment there: https://github.com/netlify/netlify-cms/issues/54#issuecomment-424154915 tl;dr: paginated endpoints are a challenge. But we could do it...

Update: this doesn't have to be that difficult, actually. We're certainly not ready for a PR on it, as there still needs to be a plan of attack for the...

stop it stale bot

#348 only affected markdown frontmatter. #238 will address this issue, but if someone wants to document it as a stop gap, it'd help.

Currently the CMS config only works in yaml, but we may as well support any other data format that we can handle (currently yaml, json, and toml).

@schalkventer actually, this issue is focused on multiple _data_ formats, eg. json, toml, etc. What you're trying to do can already be done via injecting config during initialization: https://www.netlifycms.org/docs/beta-features/#manual-initialization I've...

After considering this a bit more, I remembered that manual initialization is the only way to do this. Without manual initialization, the CMS auto bootstraps, so loading the config is...

Yeah that's the one. So the way you do JavaScript config, in case you haven't tried it: ```js import { init } from 'netlify-cms' init({ config: { backend: { name:...

Resolving this issue should entail config support for all of the formats that Netlify CMS can parse, which is YAML, JSON, and TOML. Technically JSON is already supported, as YAML...