Great read. I'm a huge advocate of using files and version control (specifically markdown and git) for published content, so I hope this workflow catches on.
Two improvements that are worth thinking about:
1) A public repository for content, separate from the main codebase. I was excited by the inclusion of "anyone" in the post title, assuming that they accepted pull requests on existing content (typos, improved documentation, FAQs) from outsiders. Turns out anyone, in this case, refers to anyone on the Pixlee team with access to the private repo.
2) Adopting the GitHub Flow [1] for content. I didn't see any mention of approval before publishing, which is an awesome freebie from piggybacking on git. They did mention that a technical member reviews all changes before deploying, but this is hardly a substitute for an editor or manager overseeing content.
While I'm not sure of the practicality of the first point (as in the people who care enough about a SaaS site to make improvements also being able to send a pull request), I certainly agree with it in principle and will think about the best way to implement something like that in the future.
The second one is something that I think we'll be working on as we grow.
Btw, big fan of what you're doing at Penflip. Definitely appreciate making Git more accessible to non-developers (which is basically what we're doing with our CMS)
Two improvements that are worth thinking about:
1) A public repository for content, separate from the main codebase. I was excited by the inclusion of "anyone" in the post title, assuming that they accepted pull requests on existing content (typos, improved documentation, FAQs) from outsiders. Turns out anyone, in this case, refers to anyone on the Pixlee team with access to the private repo.
2) Adopting the GitHub Flow [1] for content. I didn't see any mention of approval before publishing, which is an awesome freebie from piggybacking on git. They did mention that a technical member reviews all changes before deploying, but this is hardly a substitute for an editor or manager overseeing content.
[1] http://scottchacon.com/2011/08/31/github-flow.html