Scaling Asana.com(eng.asana.com)
eng.asana.com
Scaling Asana.com
http://eng.asana.com/2014/02/scaling-asana-com/
45 comments
Statamic actually does include an Admin interface where you can do (basically) this. We really like having the Git version control and we really like the Github editor, which is why we don't use the Admin pages, but they definitely exist in Statamic already.
That is certainly helpful. The website makes it confusing as to whether I need to host this somewhere, with every client site, or if I need to run a single server and point things to it, or if they do the hosting and run a service for me? What exactly am I paying for when I buy this?
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.
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.
Hello, I'm one of the Statamic developers.
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!
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!
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.
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.
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.
they've been super-responsive fixing any issues we've found (although we don't use the admin interface)... you should shoot them a message if you have specific concerns.
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.
Asana employee here. We have 58 people, about 20 of which are engineers. Even just focusing on engineers, there's so much we'd like to do and growing the team enables us to work on more of those things. It took 3 engineers to build the recently launched calendar feature, for example. And then there are other product features, growth, mobile, platform, data, and a bunch of us working on infrastructure (from keeping the site running to making it fast).
nice. now: task dependencies. get on it. please.. :-)
When I started at Google, everybody said the same thing. What do you need 3000 people for? They thought it should require like 50 people. It's just a box on a web page that you type into. But there was a lot going on behind the scenes to make that happen :)
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.
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.
I find that I have a (probably irrational) inclination to think that about virtually every technology company I hear about, regardless of size. This can range anywhere from "how can they employ FIVE engineers, it's just a simple app that does X" to "how can they employ TWO HUNDRED salespeople, it's just a simple website that does Y."
I'd be interested in knowing more details. It doesn't seem like some of their pages (e.g. https://asana.com/product ) would be very easy to represent in markdown, especially considering the image carousels.
Statamic includes a short YAML snippet at the top of the markdown files where you can specify the layout/theme you want to use (or you can just use defaults). The YAML can also include variables that can be used in the theme, such as "Headline," "Subhead," etc... and lists. It's pretty awesome.
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.
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.
I got sent an Asana invite from the boss earlier today. Apparently we are going all-in on using it.
You're lucky. I use Asana for my personal tasks at work and I wish we all used it, but the PHBs want burn-down charts and such so we officially use Jira.
I used to be in that situation which is why I wrote Bee (http://neat.io/bee/). Its a Mac client for JIRA (amongst other services) and makes JIRA much more pleasant to use.
JIRA's UI tends to be geared towards project management types. I wanted to bring the focus back onto the engineer.
JIRA's UI tends to be geared towards project management types. I wanted to bring the focus back onto the engineer.
Happy to know about Bee. Trying it right now.
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.
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.
Well you'd be surprised. I've also tried to solve this problem.
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 :)
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 :)
Just bought Bee (to track github issues). That's a pretty convincing video you have there!
The Asana mobile apps are garbage, I don't know if you're ever used them, but it's like they didn't even try.
I recommend trying Hill88. It's a third-party iOS (universal) app for Asana and it's fantastic. Mostly wonderful UI, frequently updated, etc. We use Asana at work and this app has made it a lot nicer to use on the mobile.
http://hill88app.com/
http://hill88app.com/
Thank you for the tip. I was looking for such an app for a long time! It is really worth its money.
It's a bit steep to call them garbage, I use both the iPhone and iPad apps from Asana, but only do jot down ideas I have at the time before I forget. Later back at my desk I'll do the more "advanced" stuff
Everything can always be better, but I appreciate that they have them :)
Everything can always be better, but I appreciate that they have them :)
we're actively developing better ones. stay tuned for updates!
I absolutely can. Not. Wait for this to happen.
Honestly y'all were better off not releasing the versions that are out right now.
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.
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.
iPad app still is missing...
Yes they're bad. You can't even view your completed tasks. What's even worse is I tried to tell mobile Chrome (the app is the same as the mobile site) to show the desktop version but I still wound up with the crappy mobile site.
Sometimes, if your subtask names (in the list below the description when you click on their parent task) are too long they run off the edge of the screen and don't wrap (on Android at least)
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:
http://timmyomahony.com/blog/autodeploy-jekyll-using-bitbuck...
It's surprisingly satisfying
http://timmyomahony.com/blog/autodeploy-jekyll-using-bitbuck...
It's surprisingly satisfying
Nicely done. I'm literally (seriously, right at this moment) attempting something similar right now. I have a Middleman site building up on Heroku and being served with nginx. That part is perfect. The content is being fed into Middleman via Siteleaf on build, but Siteleaf doesn't yet have any sort of webhook on publish/edit of an article :( I think I'm going to just have to rebuild on cron every 10 minutes or something...
nice!
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.
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.
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.
[deleted]
Last weekend I actually built a self deploying website with Github Pages, Travis CI and Middleman.
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!
https://github.com/Egbert/vonb-tv
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!
https://github.com/Egbert/vonb-tv
Does something like Statamic exist as open source?
I'm building Grow and the Grow SDK (http://growsdk.org) which has a lot of overlap with Statamic (file-based, content in Markdown, YAML things).
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.
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.
http://getkirby.com/ is close, although doesn't seem as polished as Statamic
This seem to be commercial software as well. https://github.com/bastianallgeier/kirbycms/blob/master/lice...
Semantics aside about the source being available to read but not effectively use, that is...
Semantics aside about the source being available to read but not effectively use, that is...
It is open source. You just have to pay for a licence to use it, but it's open source.
For clarity, Statamic is not open source. A license will get you the zip file full of code, and you can tinker with it as much as you'd like, but this is the actual license agreement: http://statamic.com/license-agreement
didnt know Asana needed scaling :/
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.