2624
Comment:
|
3936
|
Deletions are marked like this. | Additions are marked like this. |
Line 16: | Line 16: |
= FAQ = * '''Could you remove the left margin and use the '''full''' width?''' See [[http://kalleswork.net/projects/debian/img/margin-comparisons.png|this image]] for a comparison and note how the top lef corner becomes congested and the whole layout looks less organised. The version of the debian logo used also looks better with significant white space beneath it. Since the logo forms an integrated part of the breadcrumbs (the text of the logo is the first crumb) its position is rather locked in by quite a few design decisions so that a change would unravel a significant part of the design. The left margin is also quite comfortable when scanning the text. For these reasons, and a few other :) I would much rather '''not''' remove the left margin. If someone has a very compelling argument I am of course willing to be convinced. * '''Could you make the logo bigger it's to small!''' The smaller logo makes the header quite space-efficient and the wider left margin sites the logo on a column of white space that makes it prominent despite the small size. Also see other heavily branded commercial sites that despite commercial pressures keep their logo resonably small. Making debian pushier than say... [[http://www.mirosoft.com|Microsoft]] would feel uncomfortable ;) |
Debian website redesign proposal
A resource for documenting, developing and discussing the design proposal.
Contents
TODO
- Make breadcrumbs work on w.d.o. Adjust wml template to print parent dirs.
Solve navbar scaling for mini font sizes. Solution it git
- Extend and document style "templates".
- Define workflow to update stylesheets on all sites
- Make sure search boxes specify what is being searched. Ie. replace "Search" above with "Search Wiki"
- Resolve side bars to avoid clashes with content/footer when sidebar is very long
- Define how to treat the footer, consistency across sites is quite important for reoccurring elements. How should site specific links be formatted?
FAQ
Could you remove the left margin and use the full width?
See this image for a comparison and note how the top lef corner becomes congested and the whole layout looks less organised.
The version of the debian logo used also looks better with significant white space beneath it. Since the logo forms an integrated part of the breadcrumbs (the text of the logo is the first crumb) its position is rather locked in by quite a few design decisions so that a change would unravel a significant part of the design. The left margin is also quite comfortable when scanning the text. For these reasons, and a few other I would much rather not remove the left margin. If someone has a very compelling argument I am of course willing to be convinced.
Could you make the logo bigger it's to small!
The smaller logo makes the header quite space-efficient and the wider left margin sites the logo on a column of white space that makes it prominent despite the small size. Also see other heavily branded commercial sites that despite commercial pressures keep their logo resonably small. Making debian pushier than say... Microsoft would feel uncomfortable
Architecture
Files
- debian.css
- deb$(subdomain).css
- changes to backend templates
The proposal works by having one global debian.css that should be the same for every subdomain and backend. Site specific tweaks and overrides are then added in a separate css file following the deb$(subdomain).css naming convention. The subdomains link to their css file which in turn includes the debian.css file via a @import line at the top of the css file.
Design
Top Navigation
- Logo
- Navbar
- Breadcrumbs
The above elements are designed to fit together quite tightly. The textual part of the logo forms the first breadcrumb therefore a slash should be the first item in the breadcrumbs before any actual link. This can be achieved with the css content tag if changes to the backend are difficult.
div.breadcrumb:before { content: "/"; }
replace "breadcrumb" above with the tag your backend provides
Typography
Font Size
After much consideration the font size is left at the browser default and uses em's to vary font size around the default body text. This means that font size as set by the user in the browser settings is respected.
Tabular, listed or otherwise heavily structured data should where appropriate use the smaller 0.75em font size. This is particularly useful for information intensive sites such as gitweb or the debian cd vendor page.
Sites in progess moving to kallesdesign
Site / Subdomaian |
Status |
preview |
by |
dsa.debian.org |
done |
zobel |
|
lists.debian.org |
WiP, needs bigger code-rewrite |
zobel |
|
git.debian.org |
WiP |
Rhonda |
|
www.debian.org |
WiP |
Rhonda |