[
https://issues.apache.org/jira/browse/COUCHDB-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Young resolved COUCHDB-2029.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
This is really ongoing work, but the first (heavy) pass of it is complete and
merged in these commits:
https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=commit;h=6ea2b081bccb77acd04b59dc392be74c26714f82
and more recently:
https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=commit;h=5d17c204dbcefc389420fef79810a58be91cde71
> Consolidate CSS/LESS class name usage to minimize custom-ness
> -------------------------------------------------------------
>
> Key: COUCHDB-2029
> URL: https://issues.apache.org/jira/browse/COUCHDB-2029
> Project: CouchDB
> Issue Type: Improvement
> Components: Fauxton
> Reporter: Benjamin Young
> Assignee: Benjamin Young
> Fix For: 1.6.0
>
>
> Right now Fauxton has loads of non-Bootstrap class names and styles for
> things that Bootstrap has a name for (ex: .button vs. .btn). Often those
> class names and styles compete and sometimes are even used together causing a
> pretty tangled mess.
> Focusing our use of class names on the Bootstrap defined ones gives new
> comers to the code documentation on what classes mean what--and we don't even
> have to maintain it! :D If you know Bootstrap, you should be able to know how
> to add buttons, etc to Fauxton without getting tripped up by .button .red
> .outlineGray, etc.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
