I'll start with contributing a modern html5 / css3 theme blueprint. None of the existing themes yet gave me the solid base to develop individual corporate designs. So I tried to find my own way ... I hope others will benefit too. My theme consists of a base theme (roots) that takes care of a html5 conform css reset and establishes a typographic system along with other css goodies. Based on roots I include a sub-theme (sprout) that includes a usability oriented back end design and and at the same time leaves all doors open for the designer to implement his desired front end design.
Next I plan to release a sub-modul to the inline API to make it even more usefull for designers in regards to image sizing, styling and positioning.
Comments
Comment #1
cialog commentedPlease see http://roots.cialog.com for the demo server.
Comment #2
cialog commented#D7CX: I pledge that Roots will have a full Drupal 7 release on the day that Drupal 7 is released.
Comment #3
avpadernoHello, and thank you for applying for a CVS account. I am adding the review tags, and some volunteers will report what needs to be changed in the code.
As per requirements, the motivation should include more features of the theme (how many columns are supported, which kind of layout is implemented, if the theme supports any colorization scheme, etc); it should also include a screenshot of the theme (which should be big enough to be seen).
Comment #4
cialog commentedHi, thank you very much for taking care of my application.
As requested, I'll include two screenshots of the theme itself and it's included sub-theme illustrating some of the main features.
* roots theme - css reset, html 5 templates, typographic base, optional visual aid (horiz. and vert. raster lines)
* sprout sub-theme - usability oriented back end (admin pages) design, flexible blueprint for any front end design
This theme is made for the user with html5 and css3 knowledge. It will provide a solid base and allow to
implement almost any kind of layout or color scheme.
For details please notice the included readme files:
***************************************************************************************
Roots - an overview
-------------------
Roots theme takes you back to the roots. It's a modern HTML5 + CSS3 theme blueprint
tailored to fit drupal. It is inspired by drupal `HTML5 boilerplate` (Paul Irish and
Divya Manian) and drupal theme 'tao'.
The main features are:
* browser default style reset
* complete drupal core style reset
* server side css browser selection - no more hacks or conditional markup
* implementation of a meaningfull typographic base grid / style
* css expert skill included (kudos boilerplate)
* theme preprocessors (kudos tao theme)
* custom theme settings for design development
What's next? Just implement your design as a sub-theme to roots to benfit from a lean
and clean base. As a starting point for rapid development the sub-theme `Sprout` is in
the package. Sprout provides basically a clean admin theme and some ideas about
how to build up on roots.
Under the hood
--------------
## Style reset
The roots style reset is a HTML5 reset (including deprecated html tags).
To overcome the annoying work of re-styling drupal core elements (eg. ul.menu)
the roots base theme excludes all drupal core style sheets. Saved bandwidth is a
free addon.
Some functional drupal styles (auto-complete, draggables ..) are re-implemented via
the `roots.drupal` stylesheet in a way that does not affect the overall clean look.
Please note that all addon modules are free to add their own styles.
As we all don't like ugly css hacks or browser specific style-sheet, a server side
css browser selection is included. You can target almost any browser type or feature
by just using the classes automatically added to the body tag.
All stylesheet inclusion is done media-specific - never use media=all. It makes
your layout a lot more predictable.
For the screen media the following stylesheets are included:
* roots.reset - the bwroser default reset
* roots.base - basic definitions for readability and usability
* roots.grid - just a raw layout
* roots.type - the typographic rythm
* roots.table - base styles for tables
* roots.form - base styles for form elements
* roots.drupal - essential drupal core styles
For the print media we define the following stylesheets:
* roots.reset - the bwroser default reset
* roots.base - basic definitions for readability and usability
* roots.print - all the print specific stuff
## Typographic base style
So many design blueprints take care of your layout grid while there's so much
need for vertical rythm and typographic sensibility. Roots adds this while providing
full freedom of choice to the designer via the sub theme.
The templates will add the class "prose" to areas containing output rendered
by drupal filters. Only those areas benefit from the typographical base style while
all other content is left quite untouched (as is the page layout).
## Alterations to core markup
Roots leaves most core element markup alone - but implements some very good
overrides from tao theme:
* theme('fieldset')
The `fieldset` element in core has been retained but with additional markup
for simpler theming. The `legend` element contains a sub-element `span` that
can be positioned properly across browsers and the main contents of the
fieldset follow other object templates with a `.fieldset-content` div.
* theme('form_element')
To distinguish between different instances of the `.form-item` wrapper, Tao
adds a `.form-item-labeled` class to labeled items and `.form-item-option` to
checkboxes and radios.
* theme('pager')
All numeric page links are grouped together into a `ul.pager-list` set.
Next/previous links are grouped together under `ul.pager-links`.
* theme('username')
All username instances are wrapped in an `a.username` or `span.username`.
## Print style preview
Roots allows a site's print stylesheets to be previewed by checking whether
`$_GET['print']` is set. For example, to preview a node's print stylesheets, you
would go to `http://example.com/node/1?print`.
## Templates
All template files are located in the `templates` sub-folder. They're designed to
follow a strict pattern. Each element is classed as such:
`[theme_hook]-[element_type]`
with the name of its hook and then the type of wrapping element within the template.
## Theme settings
In the theme settings for roots you can toggle settings that provide visual aid
while growing your very own theme based on roots.
***************************************************************************************
Sprout - an overview
-------------------
Sprout is a sub-theme to roots. Sprout is where all the customizing happens.
The main features are:
* reasonable backend style
* some (minimal) inspiration for your individual frontend style
What's next? Sprout is a work in progress. It is meant as a starting
point - so go ahead and enjoy.
Comment #5
cialog commentedComment #6
cialog commentedHi everybody,
i would be really very happy if someone could take the time and have a look. Please :)
best regards
stefan
Comment #7
lvadillo commentedLooks very nice and promissing eStefan, congratulations. Waiting for it to be part of the Drupal themes and, if possible, with a D7 version too.
Comment #8
cialog commentedI really appreciate your feedback lvadillo - like you I hope that somebody will approve my application ...
Comment #9
tlattimore commentedThanks for applying for CVS access stefan. After my first initial look at your theme here's a few things that need to be changed:
First,
LICENSE.txtshould be removed. This file will be added by the Drupal.org packaging system when a project release is made.Second, what are the
README.mdfiles? If these are supposed to be basic readme files they should just be .txt.Make these changes than upload an updated zip file.
Comment #10
tlattimore commentedBlast! Tagging
Comment #11
cialog commented... as requested - and thanks for taking your time !!
Comment #12
avpadernoComment #13
zzolo commentedHi. Please read all the following and the links provided as this is very important information about your CVS Application:
Drupal.org has moved from CVS to Git! This is a very significant change for the Drupal community and for your application. Please read the following documentation on how this affects and benefits you and the application process:
Migrating from CVS Applications to (Git) Full Project Applications
Comment #14
cialog commentedSorry, didn't know that I could convert the CVS application. Thus you'll find my new GIT project application here: http://drupal.org/node/1072648
Please be so kind and review the theme ... I'm desperately waiting / hoping for approval!
Comment #15
zzolo commentedMarking as duplicate, see http://drupal.org/node/1072648