[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Web site design and Slashdot reply .3


My proposal for the new design :

 - move the timestamp *& the instructions to contact Greg* to the
   upper left corner
 - in the "news" and "latest document updates", use little boxes, the
   current huge books are too imposing
 - add RFC and security links (lwn, securityfocus.com and bugtraq?)
 - under the LDP logo, put the following links (make them big :-)
        - HOWTO
        - FAQ
        - GUIDE
        - (DOCBOOK when Jorge will have the new section ready)
        - FTP SITE (metalab.unc.edu/pub/linux/docs/)
 - for the left side boxes, I suggest the following (** means title)
        - *Search* search entry, links, resources
        - *LDP worldwide* non English information, non English
          documentation (metalab mirror), mirrors (of metalab :-)
        - *LDP @home* tar.gz archive of the current docs, printed books
          of the LDP, feedback
        - *Documents* HOWTO, FAQ, GUIDE, FTP SITE
          *Information* volunteers, manifesto, license guide
        - *Author section* sgmltools, HOWTO HOWTOmailing
          list archives
        - *Contribute* todo, contacts, submit a doc (ldp-submit)


Thanks a lot to slashdot readers for the comments they submitted.

Our announcement may have seemed "empty" but you provided us many
feedback regarding the LDP in general, and that will help us improving
our quality.

While reading the comments, I took a paper and wrote down the different
problems people had.

Some will not be solved immediately, some are now solved :

  - web site design : FIXED (http://www.linuxdoc.org)

Each of your comments were precious to help us improve its appearance
and ease of use.

You can try the new version.

  - provide direct access to important links : FIXED (http://www.linuxdoc.org)

We now have big links for each of the major document types (HOWTOs,
FAQs...) in the first page.

Please check "non English" where you should find a link to your local
LDP with translated documents.

  - provide security bulletins & link to RFC archivesa (http://??? links)

I'm sorry but this is not in the current goals of the LDP.
However, we will add links in the links section

  - provide DocBook and PDF documents : FIXED
and ftp://metalab.unc.edu/pub/linux/docs/HOWTO/other-formats/pdf)

I converted each of the LinuxDoc HOWTOs and mini HOWTOs to DocBook and
uploaded them 2 days after the Slashdot article ; they are now available
on ftp://metalab.unc.edu/pub/linux/docs/HOWTO/other-formats/docbook as
another output, just like the html and ps versions.

Since 2 persons also asked a pdf output I'm also working on that.

  - move to DocBook because LinuxDoc sucks
  - stick to LinuxDoc because DocBook sucks

The HOWTOs are now provided in both LinuxDoc and DocBook; however for
the moment we can only accept LinuxDoc source for the HOWTOs.

In the next weeks both DocBook and LinuxDoc sgml source will be
accepted, we are currently testing DocBook output formats.

You can already submit your DocBook only document which will be put in
the DOCBOOK section. (a new major section, like FAQs and HOWTOs)

  - "tables don't scale to window size and resolution and 10 pt font
    size is hardcoded

Our webmasters are working on these problems.

  - How can I submit my work to the LDP? (http://??? HOWTO HOWTO)

4 possibilities : 
a. you can write in LinuxDoc : call your document an HOWTO
b. you can write in DocBook : call your document a DOCBOOK :-)
c. you are a master of TeX/LaTeX, pdf or any specific format : call your
   document a GUIDE
d. you only know ascii and html : call your document a FAQ

Then please choose a license compatible with our requirements (GNU Free
Documentation License is IMHO the best choice but feel free to take any
other license) and mail your document to ldp-submit@lists.linuxdoc.org

If your LinuxDoc or DocBook source contains errors, I'm sorry but we
won't process the document, please test it first

  - You should check the documents : FIXED

We already do!

Since november, a peer reviewer team is trying to proof read each
submitted document.

However, there are far too many docs submitted to ldp-submit for our 2
peer readers.

They can not proof read each document ; if you feel like helping them
please subscribe to ldp-submit (mail ldp-submit-request@lists.linuxdoc.org).

  - XXXX and YYYY HOWTOs are outdated/unmaintained

Please update the document if the license allows modifications.
We will be happy to include your new version (News HOWTO and SCSI HOWTO
are especially old!).

  - I just found ZZZZ HOWTO which is not part of the LDP yet

Then please contact the author and ask him to send his document to

Chances are we will include it, unless it contains errors, has a non
free license, or duplicates an existing document.

  - license problem, GNU/Linux... FIXED (http://??? manifesto license guide)

We have a manifesto and a license guide on the first page ; both are
currently being revised.

We will not impose any license but rather have some criteria and
requirements (free redistribution for ex.)

And if you don't like "LDP", just remember netscape/mozilla : it's
written LDP but it reads GNU Linux Documentation Project.


Writing documentation is not as sexy as writing software
(quoting a slashdotter: "Honestly, how many users want to read
documentation? How many of them see a fat manual and feel happy?")

We do need more authors. Unfortunately, not everyone can be a good
author. It requires a combination of writing skills, technical
knowledge, and the willingness to accept criticism that improves your
final product.  Thank you all for your responses--we hope that you
continue to let us know your opinions on the LDP.

Guylhem P. Aznar                               http://www.linuxdoc.org
guylhem \@/ metalab.unc.edu             http://metalab.unc.edu/guylhem
"They who can give up essential liberty to purchase a little temporary
safety, deserve neither liberty nor safety."  -----  Benjamin Franklin

PGP signature