This is a fantastic approach to the "But how am I going to be able to edit it?" question that inevitably gets asked by clients or bosses.<p>I've tackled the problem so many times and had so many different solutions depending on the client.<p>Instead of providing a stupid and bloated CMS to do things I don't want it to do and let the user break things that they shouldn't be breaking, there's this.<p>I could possibly just provide them with access to edit some markdown with a link or two and instructions on how to make the edits. It puts a bit more burden on the user, but it also means they don't have to pay to run or setup a dynamic and crazy CMS platform too.<p>If someone could productize this as a service, provide a pretty interface for it, and let it be an easy CMSaaS that gives me, the developer, lots of options and access, but provides a dead simple and easy editor that I could give to my clients, I think that'd be great.
I'd be wary of using Statamic, at least the admin panel portion. I did a code review of it recently and it's pretty insecure, if you can disable/delete admin.php I'd recommend it.<p>After a quick look I found a few basic CSRF and session hijacking exploits going back several versions (including the latest). The PHP code is pretty amateur - I imagine somebody with more skill could find many many more holes.
A hundred people to work on Asana? Asana is a great task manager, but that's a lot of people. Basecamp for example has 43 people, which still strikes me as a lot of people. I guess having mobile apps requires at least a few people working on each there. A backend team, and the webapp team. 100 seems like a lot though.
I'd be interested in knowing more details. It doesn't seem like some of their pages (e.g. <a href="https://asana.com/product" rel="nofollow">https://asana.com/product</a> ) would be very easy to represent in markdown, especially considering the image carousels.
I do something similar with my own personal site. It's using Jekyll and the repo is in bitbucket. When I commit to the repo, my server is pinged (to a lightweight Flask app) and the server pulls the changes and recompiles the static pages:<p><a href="http://timmyomahony.com/blog/autodeploy-jekyll-using-bitbucket-post-commit-service-hooks-and-flask/" rel="nofollow">http://timmyomahony.com/blog/autodeploy-jekyll-using-bitbuck...</a><p>It's surprisingly satisfying
Often when I try to open Asana it will take minutes to load. I also find it very hard to organize things inside of the product to the point where I prefer vim. There's not way to specify blocking/dependencies and linking inside the product always carries your search context with you.<p>For small todo style lists it seems fine, if not overkill and if it eventually loads, but for more complex task tracking I just really haven't gotten it at all.
I think this is great. If only more people agreed on writing and maintaining markdown. Often it's the non-technical folks who are driving how a marketing site is run.
Last weekend I actually built a self deploying website with Github Pages, Travis CI and Middleman.<p>The owner has access to the github repo and can edit everything whenever she feels like it.<p>No need for a non functional cms, a wysiwyg editor or me for simple text updates!<p><a href="https://github.com/Egbert/vonb-tv" rel="nofollow">https://github.com/Egbert/vonb-tv</a>