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

Re: Wiki editing refresher



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Karsten Wade wrote:
> For all who are editing the DUG or Docs/Beats/, a quick reminder
> pointer:
> 
> http://fedoraproject.org/wiki/WikiEditing#Marking_Technical_Terms
> http://fedoraproject.org/wiki/WikiEditing#Quick_Tips
> 
> Thanks - Karsten
> 

I've been working on converting the server guide (slowly) and notice
that the wiki does not have all the functionality/style that I need to
'easily' convert my guide to the LDP wiki - or I'm doing it the wrong
way :-O.

As the guide is server based, most of the configuration is done by
manually editing the files at the command line. I wanted to make the
guide easy to follow, so I'd like to have a separate format/style
differentiating between a typed command, the output of a command, and
the contents of a configuration file - these seemed the most common
choices for manual administration.

To move technical info (config files etc..) into the wiki takes a large
amount of time using wiki markup, and displaying configuration files
inside a table takes a fair bit to format, so it looks similar to what
the user is expecting to see. To make it simpler, html - <PRE> tags work
best, however the CSSs only provide one format/style for <PRE> tags.

I loaded up moin on my own server so I could learn without killing
anything on FDP and also to play with the CSSs/markup to get the results
I think is suitable for the guide.

I've created a few pages and a template located here:
http://www.brennan.id.au/wiki/
http://www.brennan.id.au/wiki/LinuxHomeServerTemplate
(Internet Explorer does not display my theme very well - known fault)

Also, upgrading the guide should be easier when it is superceded by the
next FC release, because the new example commands / output can be copied
straight into the <PRE> tags again.

I just wanted to get your opinions in regards to the formating/style of
the command line interaction and to see if it would break anything
(docbook/CVS/XML conversion etc..).


Regards,
Miles Brennan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (MingW32)

iD8DBQFE8bNvcSPa0xQu/fARAkivAJ40EDGO1974DS0I2ZPlH59k1tx9YwCdHSp2
6PWVKKLpCa5pv4XY6GFWdkg=
=tEPn
-----END PGP SIGNATURE-----


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