Offer Support for Nontechnical Content Creators

[frastlin]

This issue was started in #25 and was moved here because it is another issue.

Problem:

Most of the users in our company have never heard of Github or Markdown and have a hard enough time using Google Docs. We need a way for them to write documentation that can be presented in am amazing interface like Cupper.
I see two problems:

1. Users needing to know Git and Github
2. Users needing to know Markdown

Please comment on the below solutions or if you have any better ideas for allowing nontechnical users to write documentation.

Related Discussions

There was an issue on the Jekyll repository, but the conclusion was that this is a Github problem and not really a Jekyll problem.

Possible solutions

Headless CMS

@Heydon commented in #25:

Your best bet is probably to use Hugo/Cupper with a headless CMS like https://www.datocms.com/cms/hugo/

This is a great option, but most headless CMS are rather expensive for a documentation site. They also require hooks for Hugo which are not always there. They also require an external server.

Content Editor for Github

There is a content editor for Github called Prose that allows users to edit content in a rich content editor that solves the need for creators not needing to know Markdown. I am not sure what the process is for submitting content, but I think for something like a documentation site where the only thing that changes is the content, Prose would be perfect.

[Erioldoesdesign]

Honestly I think that something that would help the not so techy folks in using cupper would be having sample files that aren't the main hugo repo that download with the theme