Feature: Tool to generate config based on an existent site

[calavera]

- Do you want to request a feature or report a bug?

Feature

- What is the current behavior?

Currently, if you want to use Netlify CMS, you have to generate a YAML file manually. This process is usually slow and error prone.

- What is the expected behavior?

It would be very nice if we could have a tool that parses a site, extracts metadata information and generates an initial configuration for you. Since the CMS is not tied to any site generator, this tool should be pluggable. It not necessary to support all cases from the beginning, but having support for Hugo and Jekyll to start would be awesome.

Finally, this tool doesn't need to leave in this repository, nor being part of this project directly, but we don't have any other place to put these kind of feature requests at the moment.

[erquhart]

@calavera what are your thoughts on first providing a UI for generating a config file from scratch?

Benefits:

• simple(r) to implement
• suitable for any build system out of the box
• works for everyone (not just those with an existing site)

We could then extend that with framework specific boilerplate generation (pluggable) and advanced stuff like parsing existing sites (also pluggable).

[tech4him1]

I would also appreciate something like this for CMSs that have example files (like Hugo's archetypes), so you don't have the field definitions in multiple places. Example:

collections:
  - name: "blog"
    folder: "_posts/blog"
    ...
    fieldFile: "archetypes/post.md" 

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[martinjagodic]

Closing as stale and/or outdated.