icinga-migration
commented
8 years ago Updated by elippmann on 2016-02-16 15:46:54 +00:00
- Tracker changed from Bug to Feature
- Subject changed from Please define HTML/CSS class name best practices to CSS + LESS Style Guide
- Category set to Documentation
- Target Version set to Backlog
This issue has been migrated from Redmine: https://dev.icinga.com/issues/10297
Created by tgelf on 2015-10-05 08:43:09 +00:00
Assignee: (none) Status: New Target Version: Backlog Last Update: 2016-02-16 15:46:54 +00:00 (in Redmine)
We created an unmaintainable mixture of expressive CSS (class="author") and layout hints (class="pull-right nav-item nav") in our view scripts. My personal preference is expressiveness. I love to see semantic in the generated HTML. I hurts me to see layout information in my HTML code. However, I know that this is a matter of personal preference. As an OSS project we should agree on one way or the other, try to find consent and clean up our HTML.
It's important to find our very own preferred style of doing things. This will help to settle down and avoid "refactoring" commits again and again. We should not behave like all those lemmings running behind the currently hyped CSS frameworks (as bootstrap used to be). They are usually over faster than we are able to prepare a new release.
Cheers, Thomas
Relations: