From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: [Documentation] New Proxy Wiki
Date: Wed, 04 Jan 2012 15:20:27 +0100 [thread overview]
Message-ID: <1325686827.2167.11.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <2F08F54A-4502-40F0-937A-9EF7B2F5F58E@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2034 bytes --]
Happy New Year 2012 for you all too.
I'm excited to see what those changes are, but here some of my opinions
on it:
* Why is there this non-public area? I normally edit the wiki entries
directly. This has advantages that you don't have to move content
around and you can keep the history of changes.
If you feel that users may be disturbed by the changes, I think that
is okay. If they are bothered they should go and fix it by
themselves. That's what a wiki is about.
* I propose a format like this:
=== General settings ===
== Parent proxy ==
The proxy sends all requests to the parent proxy instead of sending
them directly to the internet.
[[Vorgelagerter Proxy]]
You will get an idea of what there is to find on the sub page but
you don't have to read it completely. So I guess that would make
the proxy page (and generally all other pages as well) more readable
because one may find the interesting stuff faster.
Tell me what you think about it? What pages could be redesigned in this
was? Where are the big problems?
Michael
On Tue, 2012-01-03 at 22:20 +0100, Erik K. wrote:
> Hi all,
> i want to inform you that the new Proxy Wiki in the NON Public Wiki
> section
> --> http://wiki.ipfire.org/nonpublic/de/configuration/network/proxy are developed (still be in early stages) new structure and content. I will try it pretty much to arrange in the way like i did it with the OpenVPN wiki --> http://wiki.ipfire.org/de/configuration/services/openvpn .
> Ideas and enhancements in knowledge, design and structure are highly
> appreciated. This Wiki is not online so it is possible to be mental on
> it ;-) .
>
>
> I want also use this possibility to wish you all a nice and pretty
> cool 2012 .
>
>
> Best regards
>
>
> Erik
>
>
>
>
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation
parent reply other threads:[~2012-01-04 14:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <2F08F54A-4502-40F0-937A-9EF7B2F5F58E@ipfire.org>]
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=1325686827.2167.11.camel@rice-oxley.tremer.info \
--to=michael.tremer@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