From: ummeegge <ummeegge@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: Wiki update
Date: Mon, 18 Feb 2013 08:55:56 +0100 [thread overview]
Message-ID: <1173AA85-2032-4649-809F-7A1B4C57E88F@ipfire.org> (raw)
In-Reply-To: <1360758616.28061.159.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 1900 bytes --]
Hi all,
i have updated the squid wiki (in german and english), cause mostly formatting commands won´t be used. So i have deleted for example the <color> commands and changed also the boxes commands to <WRAP classes width> </WRAP> . I think there are a lot of work to do if the formatting of every wiki page should be updated, but also a good chance to overlook them again for possible errors, outdates or enhancements.
So a question for the first, should we leave it by the usage of one plugin ? The Dokuwiki have surely some other design possibilities under the bonnet e.g. the syntax-highlightning so one plugin may enough. But if there should/can come more plugins, it might be an idea to find out which ones might be interesting. So we can implement them before the update of the whole wiki will be done.
May there are some ideas ?
Greetings
Erik
Am 13.02.2013 um 13:30 schrieb Michael Tremer:
> Hello,
>
> yesterday, I updated the primary IPFire web server and the wiki software
> as well. I am sure some of you have already noticed, that it looks quite
> different.
>
> I won't reinstall the old theme, because it does not work with the old
> version. And instead of downgrading to the old version of the wiki I
> prefer the one in which all security problems are fixed.
>
> If there is anyone who would like to have a go and port the new layout
> to the wiki, go ahead!
>
> Despite the theme, I did not re-install all plugins. Most of them were
> redundant and so there is mainly the wrap plugin for formatting:
> https://www.dokuwiki.org/plugin:wrap
>
> Maybe some fixes are required, because the long-time obsolete commands
> were still used.
>
> -Michael
>
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation
next prev parent reply other threads:[~2013-02-18 7:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 12:30 Michael Tremer
2013-02-18 7:55 ` ummeegge [this message]
2013-02-18 15:05 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1173AA85-2032-4649-809F-7A1B4C57E88F@ipfire.org \
--to=ummeegge@ipfire.org \
--cc=documentation@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox