Scaling Asana.com
eng.asana.com
eng.asana.com
I've tackled the problem so many times and had so many different solutions depending on the client.
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.
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.
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.
Presentation issues aside: I think it would also be neat if I didn't have to host/maintain/setup anything at all. Simply point a service at a (my) github repo where I can commit my client's sites, and let the service take care of the rest, providing a nice admin for me and something I can do for my client. That way, I don't need to have a server setup and running PHP if they don't need it. Makes it less expensive for me to setup and less expensive for the client to run.
It could store my templates, so I could easily fire up a new service and send a link to the client. Hell, maybe even use a template each time and say: "Here, provide your copy while I go build some stuff. We'll marry them together as we complete our respective sides of the agreement."
If that's where Statmatic, Stamatica, err... Statamic, is going, then I think that's pretty neat. But, it's not terribly clear at the moment.
Statamic is both a content management system (in that it has a nice, responsive, client-friendly admin area for managing content) and a website-building platform (in that the admin area is completely optional if you're someone that's comfortable with writing content files, and you can fully create and maintain a site easily without it). A license gets you the software itself and allows you to run it on one domain.
At the moment, there's a folder where you place all of your content files. I've seen people play with syncing that up with systems like Dropbox and even maintaining that folder as its own git submodule. There's no ability to do that automatically at this time, but I bet someone could figure out how to make that happen.
It seems out marketing message could be a bit more direct in that instance, certainly noted!
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.
I don't know anything about Asana, but there is this iceberg illusion where people judge the size of a company by the size of the UI. The size of the company is probably more related to the size of its customer base, among other things.
Most of the carousels are partials where we feed in some basic variables around copy/image - but since they're at the top of the Markdown file, anyone can change them easily.
JIRA's UI tends to be geared towards project management types. I wanted to bring the focus back onto the engineer.
However, Jira fundamentally is about managers tracking work, and not about workers actually getting stuff done. There's no way I can track all my tasks in Jira even if I have a nicer GUI for it.
I'm actually part of the way towards writing a program to sync tasks between Asana and Jira using their APIs. I'm hoping that that'll let me continue working in Asana while it handles Jira (which I've always found incomprehensible) for me.
You can create your own lists inside of Bee which filter issues based on your own rules (http://neat.io/bee/docs/smart-lists.html). It's helpful because you just define the rules one-time and then flick to it whenever you need to.
Bee also has a menubar helper which tracks your short-term tasks and queues up your next issue so you always know what you're working on (http://neat.io/bee/docs/the-short-list.html).
Also you can add your own Notes list which is just a series of text files (easily synced via Dropbox) if you want to track your own local tasks.
I'm constantly iterating based on user feedback so if you have time, please let me know how it works out for you :)
Everything can always be better, but I appreciate that they have them :)
Yes it's good to "fail fast" and all that feel good stuff, but when you KNOW something is terribad, it's better to just wait and release than to put out something so awful.
Take charge of the experience your users are exposed to.
http://timmyomahony.com/blog/autodeploy-jekyll-using-bitbuck...
It's surprisingly satisfying
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.
The owner has access to the github repo and can edit everything whenever she feels like it.
No need for a non functional cms, a wysiwyg editor or me for simple text updates!
One of our tag lines is "develop everywhere, deploy anywhere" – as in, sites are file-based and can be developed locally or in the cloud on our web service. Grow can deploy to a variety of servers (S3, GCS, Dropbox, etc.).
The project's not quite ready for use yet but the SDK will be released as an open source project under the MIT License.
Someone submitted my introductory blog post about Grow on HN a few months ago: https://news.ycombinator.com/item?id=6562182 – Right now you can sign up for the mailing list, and when a developer preview is ready I'll send out updates. :) I hope to have something ready in a few weeks, actually.
Semantics aside about the source being available to read but not effectively use, that is...