<story><title>Netlify CMS – An open-source CMS for Git workflows</title><url>https://www.netlifycms.org/</url></story><parent_chain><item><author>bradgessler</author><text>This will sound crazy, but I recently deployed a content management workflow for a rails app that mounts a WebDAV drive inside of a staging rails application that&amp;#x27;s running &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;sitepress.cc&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;sitepress.cc&amp;#x2F;&lt;/a&gt; (think Middleman in Rails, without all the dependencies)&lt;p&gt;If the marketing team wants to edit something, they mount the content drive, make changes using their text editor of choice, and are able to preview when they hit Save.&lt;p&gt;After they make a bunch of changes and add whatever media an engineer copies the changes off of the drive into a commit and deploys to production.&lt;p&gt;So far it&amp;#x27;s been working pretty well. The marketing and CS team are all able to edit markdown copy and run it easier through their content editing processes since it&amp;#x27;s just files. They don&amp;#x27;t need to learn or care about git. Designers can throw images in the volume without thinking too much about it.&lt;p&gt;Engineering is happy because they control their git history and commits. When it&amp;#x27;s time to optimize PNGs, compress assets, etc. the engineer can deal with and deploy to product with confidence.&lt;p&gt;We also run rspecs against every single page of content to enforce SEO, branding, etc.&lt;p&gt;Happy to answer questions or write something more detailed about it if others are interested.</text></item></parent_chain><comment><author>chocolatebunny</author><text>I setup winscp to automatically sync a directory from a coworkers laptop to a webserver so he can edit his html documents in Microsoft Frontpage locally and have it sync with the remote server.</text></comment>
<story><title>Netlify CMS – An open-source CMS for Git workflows</title><url>https://www.netlifycms.org/</url></story><parent_chain><item><author>bradgessler</author><text>This will sound crazy, but I recently deployed a content management workflow for a rails app that mounts a WebDAV drive inside of a staging rails application that&amp;#x27;s running &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;sitepress.cc&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;sitepress.cc&amp;#x2F;&lt;/a&gt; (think Middleman in Rails, without all the dependencies)&lt;p&gt;If the marketing team wants to edit something, they mount the content drive, make changes using their text editor of choice, and are able to preview when they hit Save.&lt;p&gt;After they make a bunch of changes and add whatever media an engineer copies the changes off of the drive into a commit and deploys to production.&lt;p&gt;So far it&amp;#x27;s been working pretty well. The marketing and CS team are all able to edit markdown copy and run it easier through their content editing processes since it&amp;#x27;s just files. They don&amp;#x27;t need to learn or care about git. Designers can throw images in the volume without thinking too much about it.&lt;p&gt;Engineering is happy because they control their git history and commits. When it&amp;#x27;s time to optimize PNGs, compress assets, etc. the engineer can deal with and deploy to product with confidence.&lt;p&gt;We also run rspecs against every single page of content to enforce SEO, branding, etc.&lt;p&gt;Happy to answer questions or write something more detailed about it if others are interested.</text></item></parent_chain><comment><author>cobookman</author><text>I&amp;#x27;ve done something similar by grabbing a google doc by url, scraping its html markup, and generating a site from it.&lt;p&gt;Some people have even done a google doc markup like language.</text></comment>