[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Structure of hurd.gnu.org
From: |
Ognyan Kulev |
Subject: |
Structure of hurd.gnu.org |
Date: |
Thu, 28 Jun 2001 18:18:46 +0300 |
User-agent: |
Mutt/1.3.15i |
Hi,
I'm reading a book about web design (Jakob Nielsen's "Design Web Usability:
The Practice of Simplicity", see http://useit.com/) and i'll try to make one
based on XHTML, i.e. all content is XHTML and it is used to generated static
HTML.
Page layout:
-----------------------------------------------------------
GNU Hurd Logo > Install /* navigation */
About INSTALL
Features /*it's stable...*/ See also:
Design /*Toward...*/ * status
unlimited Sections:
Translators * download
4th bit * compile
authentication (many ids)
subhurd
Installing content here....
Download /*Mach&Hurd*/
Compile /*Mach&Hurd*/
FAQ
Documentation
Utilities /*rpctrace, etc*/
Servers /*ext2fs, etc*/
HOWTOs
What Is
Status
Tasks
Links /*here?*/
Development /*here?*/
Microkernels
GNU Mach
...
L4
This site
Contribute
Site Map
Print
Copyrights, last modify, written by
--------------------------------------------------------------
The second level must not be shown. It is recomended pages to have see also
and sections lists.
The starting page have to be a bit different. What about <pre>d structure
of a GNU system? This way people will know visually where is the exact
place of Hurd in a GNU system. Something like
Application programs ,--app1 app2 app3
| \ / |
GNU C Library | glibc <--------'
| |
v v-------+------v
Hurd Servers proc auth ext2fs ...
| v |
Microkernel `-----> GNU Mach <-'
v
Hardware PC
And now the star of the night: all this XHTML can be translated to TeXinfo
and converted to PostScript. This way someone can just print the site and
will have better look over all.
What do you think about that?
Regards
--
Ognyan Kulev <address@hidden>, "\"Programmer\""
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Structure of hurd.gnu.org,
Ognyan Kulev <=