From: Jan Heinen <JaHeinen@gmx.de>
To: ntg-context@ntg.nl
Subject: Re: Integration of all the information around ConTeXt
Date: Fri, 16 Mar 2012 18:19:18 +0100 [thread overview]
Message-ID: <4F637616.3080100@gmx.de> (raw)
In-Reply-To: <4F6330F7.3030803@gmx.de>
At step 5 (see below) please delete
[[category:Commands]]
But only when you write a new category.
And I just got the proof for my book ... it looks great!!!!!
Regards
Jannis
----- Copy -----
Hello,
with the help of ConTeXt and the ConTeXt-Mailinglist I
successfully have generated a book which will be printed
next week :-)
Thankl you - everyone!
And now I would like to give something back to ConTeXt :-)
There is a lot of information around ConTeXt: Material of
Hans Hagen, this very dynamic Mailinglist/Forum, the
command-reference-list of Wolfgang Schuster and the
Contextgarden-Wiki. I think the best what I can do for
ConTeXt is helping to structure, organize and integrating
the huge amount of existing information.
And the wiki ist a very good place to do al this work.
Since several years I am running an own wiki with mediawiki.
After informing Hans, Taco and Mojca Miklavec, I no have
started, to rename all the commands from reference/en/... to
command/... The .htaccess takes care, that all the old names
will be forwarded to the new names. Then I have build a
startting-category: "ConTeXt" and every subcategory is a
branch of it. So we have a tree with all the
wiki-information starting at "ConTeXt". You can find this
startingpoint on http://www.contextgarden.net on the right
side: Categories. I have started to organize the
sub-categories ... but everyone who likes ConTeXt is invited
to improve the wiki.
A very good help would be:
All the commands of context (more than 500) are in one huge
category:commands For the users it would be usefull to build
subcategories for the commands.
1. login (or first register on contextgarden.net)
2. Go to a command, e.g. command/about:
http://wiki.contextgarden.net/Command/about
3. Click on edit (top of page)
4. go to the bottom of the source-code
5. add to
[[category:Commands]]
[[category:xxx]] xxx = new name or existing name
6. save the changes
7. now you can see the category at the bottom of the page.
8. if it is red - click on it
9. then write
[[category:commands]]
to link it to the tree,
I hope lot's of you help at least a little bit ... it's fun
:-) And it's for ConTeXt.
Regards
Jannis
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-03-16 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 12:24 Jan Heinen
2012-03-16 17:19 ` Jan Heinen [this message]
2012-03-16 20:40 ` Kip Warner
2012-03-17 13:46 Jan Heinen
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=4F637616.3080100@gmx.de \
--to=jaheinen@gmx.de \
--cc=ntg-context@ntg.nl \
/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;
as well as URLs for NNTP newsgroup(s).