"Purple is a UI kit for all of Heroku's digital properties"
They are not releasing a Bootstrap clone, they are simply creating documentation for their own design standards.
Yeah, and they seem to make the purpose fairly obvious all throughout the docs. Not sure how people are being confused other than skimming very quickly.
I do like how they've included patterns at the end, e.g the blank slate. Adding basic UX like that into your style guide seems very useful. I might look into something like that for my team.
Is it just me, or is this just bootstrap in purple?
I don't think so, but ironically, bootstrap is purple.
It's just you. ha
It's not just you... This is bootstrap with a heroku theme. They use the exact same syntax as the bootstrap classes, and even reference the bootstrap grid in the docs.
And the template twitter accounts are @mdo and @fat. :)
My largest concern here is the including of Benton Sans. Last time I checked it's pretty expensive so does that mean this kit includes a license to use it?
Font Bureau sells the family for $3k (granted that's 80 fonts).
A quick view-source reveals usage of three fonts: Book, Regular and Medium. I guess italics are out.
Curious what the license agreement looks like.
No, this is for internal Heroku use.
The @fontface urls for benton sans are included in the kit though...
And using them on your site will probably get you a nasty email from Font Bureau.
Oh god, I don't what it is but I have a serious love for things that are simply designed and get straight to the point. I realise it's more about the actual kit and documentation content, but can't ignore the good presentation.
Side note: The link to the GitHub repo is 404'ing https://github.com/heroku/purple I'm guessing the repo is still private?
So whats the point of this?
I really don't think the industry needs another bootstrap.
That's not the point.
"Purple is a UI kit for all of Heroku's digital properties. Purple provides guidelines for the aesthetic, function and form of user interfaces to provide a consistent experience for our customers. This is a living document and is under constant interation."
It says right there, top of the page.
Shame this was taken down. It was a really useful example.
The CSS for the loading spinner module is a good example of why I don't like BEM and being too religious about standards. Why are there such complex classnames for each dot inside the spinner? Even worse, .spinner is too generic name for a class to wrap the whole thing, and it don't even spin.