From: Corin Royal Drummond <corin@studiochango.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Is there anything like developer's manual for ConTeXt?
Date: Mon, 16 Mar 2009 20:33:54 -0600 [thread overview]
Message-ID: <49BF0C12.90707@studiochango.com> (raw)
In-Reply-To: <49BF0323.90807@gmail.com>
Wei-Wei Guo wrote:
> Hi everyone,
>
> After fighting with ConTeXt one month, I find it's too difficult. I
> have two years
> experience of LaTeX. I never thought ConTeXt could be so difficult.
> Using ConTeXt
> is like climbing a steep mountain, every step need extensive
> searching, reading,
> and asking.
>
> Sorry for the useless complain. I'm stuck by so many problems. I might
> be lack of
> the basic knowledge of ConTeXt. Could someone tell me where I can find
> manuals or
> papers that describe the logic of ConTeXt design and basics of ConTeXt
> programming.
>
> Thanks in advance.
>
> Best wishes,
> Wei-Wei
Many have voiced the same complaint. I understand that Hans and every
one are occupied with building MKIV (aka LuaTeX), and that documentation
is not their highest priority. There's the wiki, the wonderfully active
mailing list, and what used to be decent docs from 2001/2002 timeframe.
But yes, it's a steep hill to climb, made worth it only by the relative
awesomeness of ConTeXt.
If there is an existing strategy for creating documentation, I'd love to
hear it.
My feeling is it's it's time to pay someone to write some good docs.
Someone who's not on the development team, who has experience writing
technical documentation, and who can shepard list members into crowd
sourcing some real documentation. MKIV is stabilizing into usefulness,
and now is a good time to start. I suspect list members would donate to
such a project, plus we could get some grant money (if that's not all
dried up due to the global economy), and maybe some contribution from
Pragma itself, and other orgs that depend on ConTeXt. A patchwork quilt
of financing, and a project coordinator/writer who sees their work as a
labor of love, and a side job, could make this happen. Even if we could
only afford 10 hours of work a week, that could get a lot done.
In terms of process, I think someone to comb the list archives for
common problems and solutions, and wikify them would get the most bang
for the buck initially. These wiki entries could later be ConTeXtified
into printed (and screen) docs, like Hans' awesome old manuals.
Honestly, we've got smart people wasting time answering the same
questions in different ways on the list, when they could be plugging in
some of that time into writing docs for everyone. And as useful as the
list is, it's no substitute for manuals.
If I understood ConTeXt I'd volunteer, but I'm a noob, so I'm feeling
the same frustration as Wei-Wei. I feel bad having to bug developers
and advanced users every time I have a basic question. It's inefficient
and inelegant, though I much appreciate the access to great minds and
the window into the development process this has given me.
Pile on to this thread, if this is a burning issue for you, or you have
some strategy or expertise to offer.
Cheers,
Corin
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-03-17 2:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 1:55 Wei-Wei Guo
2009-03-17 2:33 ` Corin Royal Drummond [this message]
2009-03-17 8:16 ` Taco Hoekwater
2009-03-17 16:20 ` Rory Molinari
2009-03-18 22:00 ` David Wooten
2009-03-19 13:48 ` Michael Bynum
2009-03-19 13:57 ` Aditya Mahajan
2009-03-19 23:32 ` Curious Learn
2009-03-19 23:57 ` Aditya Mahajan
2009-03-20 9:53 ` Jesse Alama
2009-03-17 8:33 ` Xan
2009-03-17 8:36 ` Taco Hoekwater
2009-03-17 8:47 ` Xan
2009-03-17 8:50 ` Taco Hoekwater
2009-03-17 10:52 ` Wei-Wei Guo
2009-03-19 14:14 ` luigi scarso
2009-03-17 7:57 ` Taco Hoekwater
2009-03-17 9:03 ` Alan Stone
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=49BF0C12.90707@studiochango.com \
--to=corin@studiochango.com \
--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).