They also give you the option of hosting your CSS file on their servers, which is why you'd need the link to that CSS file.
It's all explained on their website which you might not have read/understood, or maybe I am missing something.
As a web developer working on quite a few projects, this tool seems great, although I can't have them hosting CSS for internal projects.
The hosting of your CSS files on their servers is also not suited for a development environment that has more than 1 environment, as I would not want to be editing files that are on a live server on a regular basis without first making those changes locally (and possibly checking them into an SCM of some sort first) because my css would quickly become out of sync across environments.
May I ask, the projects that you work on, do you have more than 1 environment that you use and do you collaborate with any other developers on these projects?
As far as working on teams, they're "thinking about how to expose your CSS in a versioned way so that you can keep it in Mercurial (with Kiln!), or Git, or whatever other version control software you might be using". Perhaps you're right, it's better to wait until that is implemented if you have that kind of setup.
EDIT: I've started testing it, and you can add other admins and editor users for sites, very nice.
Seems like a Web Putty browser plugin would help preserve the "local transparent editing a la Firebug" use case. Transparent meaning, no edits to your existing HTML required to demo different CSS stylings. Or am I misunderstanding this?
Doing the same thing with WebPutty would take maybe a dozen lines of code. I'm assuming anyone with multiple environments can make it happen in their language/framework of choice.
We're also releasing this very early, for a Fog Creek project, to see what people think. It might be that this becomes a desktop tool using something like Titanium, or we might try to integrated version control into it as an alternative to publishing. As such, we're open to suggestions and feedback.
We actually did look into getting Mercurial (which is what we use internally and what we provide via Kiln) up and running in AppEngine, which has been done before, but was just beyond the scope of the first phase of the project.
And I agree, I don't think we'd ever host FogBugz's or Kiln's CSS with it on AppEngine, but I do really want to be able to use the editor and SCSS with those projects, so we'll be keeping an eye towards making that more natural.
I think there is a lot of changes that can be done to make this a better solution. But as it stands if being used by a small company I can see some merits.
However, I would be cautious about putting something in a beta stage on any site with enough value.
Any site I've ever worked on I've always had atleast 2 environments, a local environment and a live environment. Any company I've ever been a part of has had at least 3 environments (sandbox/qa/live) and it's very common to have a dev and staging environment on top of those as well. The reason you have a minimum of 2 environments is so that you can do all of your testing without breaking the live environment, which is what this tool seems to ignore.
"You can always export a pretty-printed version of your website’s CSS at any time (both the preview and published versions)."
See my other post, I believe you have not understood their product very well.
Not sure how I feel about the inclusion of the link/script tags in order to make this work but it all seems geared to someone who maybe has their own blog or very low-trafficked site and this would be their alternative to editing the files on the live server.