Talk:Wiki wish list: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
# I personally (and this is a matter of style, not acceptable vs. unacceptable) favor extreme minimalism as to headers. People come to a page to read the contents, not the header. I'd rather hide the information for other levels inside tooltips than make it visible all the time. | # I personally (and this is a matter of style, not acceptable vs. unacceptable) favor extreme minimalism as to headers. People come to a page to read the contents, not the header. I'd rather hide the information for other levels inside tooltips than make it visible all the time. | ||
# Think about what I've said here. If you're happy with your current example, go ahead and implement it. If I've convinced you of the value of minimalism, let's see if we can simplify it first. | # Think about what I've said here. If you're happy with your current example, go ahead and implement it. If I've convinced you of the value of minimalism, let's see if we can simplify it first. | ||
---- | |||
* I agree that there is a lot that doesn't fit under the current package arrangement. There certainly needs to be a way of tying those things back into the overall navigation scheme. I'm not attached to anything I've presented, I was just aware that change was required, and usually the best way to decide how that change should progress is to get in there and start changing things, or presenting examples of what change might look like. That way we get an idea of what will and wont work, and what other things need to be considering within the changes. | |||
* Where to from this point? | |||
** How can the whole be divided up into segments that will make sense to visitors, and keep the information arranged logically? | |||
** Would it make sense to have two (or more) top level domains, e.g. Philosophy and Practicality, or something along those lines? | |||
** There will be generic information (refer current [[:Category:Materials]] category) that is generically useful across different packages, and currently doesn't seem to placed firmly within a package. I think there are a few like this where they need to be drawn into one of the existing packages (flex industry for materials for e.g.) or consider creating new sections. Most of materials could go under a resource extraction and recycling project/package within flex industry. | |||
** I like the idea of breadcrumb style headers. Are you also thinking we would be better doing away with any forward links? | |||
*** '''Main -> Packages -> Habitat''' | |||
*** rather than: | |||
*** '''Main -> Packages -> Habitat: CEB, Living Machines, Modular Housing, Sawmill''' | |||
** It would make sense to go with the former, as you'd only be seeing that header on the habitat category page anyway, but it will require some method of highlighting the main packages within the category page so they stand out from the crowd. Perhaps every package category page has an introduction that bullet points the primary projects and gives an idea of progress/state for each? | |||
Revision as of 00:03, 21 July 2009
Created a draft of a new site header, along with subheaders for each package. I've implemented them in the energy category page so you can get a feel for them and discuss before refactoring through other packages.
- I figured how do the tooltips and made a few changes to Site Header 2 and ProjectHdr Habitat templates to illustrate.
- Style notes (IMHO)
- Never use CAPS FOR EMPHASIS (= SHOUTING)
- Never use underlines for emphasis (= link)
- No need to repeat the word "package" in every link, just put "Packages:" before the list
Agreed. The particular styles were in place to try and distinguish the packages from the whole array of projects in the original header. By breaking it down into a clean package only header and then subheaders for the projects the styling can be cleaned up and it should be easier to see what's going on.
- I've modified the project header for habitat to include the site header directly, that way people only need to include the project header and the other one is included by default. Also removed the seemingly redundant "Packages" from the beginning of the package only content, as the site header above seems to qualify that enough. Check out Category:Habitat to see if it's headed in an acceptable direction.
- I see where you're going and I think it's a big improvement over what is presently in the wiki.
- We've been talking about "site header" but it really isn't. A page like Evolve to freedom doesn't fit into any of the packages or projects. It really needs a header like: Main -> Vision -> Freedom. We might want a Sawmill category with a header like: Main -> Packages -> Habitat -> Sawmill.
- I think your latest example works well for a 2-level hierarchy, but not so well for 3 or 4 levels.
- I personally (and this is a matter of style, not acceptable vs. unacceptable) favor extreme minimalism as to headers. People come to a page to read the contents, not the header. I'd rather hide the information for other levels inside tooltips than make it visible all the time.
- Think about what I've said here. If you're happy with your current example, go ahead and implement it. If I've convinced you of the value of minimalism, let's see if we can simplify it first.
- I agree that there is a lot that doesn't fit under the current package arrangement. There certainly needs to be a way of tying those things back into the overall navigation scheme. I'm not attached to anything I've presented, I was just aware that change was required, and usually the best way to decide how that change should progress is to get in there and start changing things, or presenting examples of what change might look like. That way we get an idea of what will and wont work, and what other things need to be considering within the changes.
- Where to from this point?
- How can the whole be divided up into segments that will make sense to visitors, and keep the information arranged logically?
- Would it make sense to have two (or more) top level domains, e.g. Philosophy and Practicality, or something along those lines?
- There will be generic information (refer current Category:Materials category) that is generically useful across different packages, and currently doesn't seem to placed firmly within a package. I think there are a few like this where they need to be drawn into one of the existing packages (flex industry for materials for e.g.) or consider creating new sections. Most of materials could go under a resource extraction and recycling project/package within flex industry.
- I like the idea of breadcrumb style headers. Are you also thinking we would be better doing away with any forward links?
- Main -> Packages -> Habitat
- rather than:
- Main -> Packages -> Habitat: CEB, Living Machines, Modular Housing, Sawmill
- It would make sense to go with the former, as you'd only be seeing that header on the habitat category page anyway, but it will require some method of highlighting the main packages within the category page so they stand out from the crowd. Perhaps every package category page has an introduction that bullet points the primary projects and gives an idea of progress/state for each?