|
Size: 936
Comment:
|
Size: 1097
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| A resource for documenting, developing and discussing the design proposal. ''My initial text will attempt to explain the structure and thoughts underlying the the design to enable other to contribute and critique.'' | ''Anyone got a better name for this page?'' |
| Line 5: | Line 5: |
| The aim for the design was to create a light robust and elegant site. | A resource for documenting, developing and discussing the design proposal. The aim for the design was to create a light robust and elegant site. |
| Line 22: | Line 22: |
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. |
Debian website redesign proposal
Anyone got a better name for this page?
A resource for documenting, developing and discussing the design proposal. The aim for the design was to create a light robust and elegant site.
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
- 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.
- Table of contents
- Secondary navigation
- Body
- Typography