ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jean-Pierre Delange <adeimantos@free.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Ideas for improving documentation of ConTeXt
Date: Mon, 10 Oct 2016 19:04:28 +0200 (CEST)	[thread overview]
Message-ID: <837405983.265372955.1476119068519.JavaMail.root@spooler6-g27.priv.proxad.net> (raw)
In-Reply-To: <2d07f89c-ece4-c4a1-00f1-7e0f9a3d5f41@uni-bonn.de>

Dear List,

This discussion (and proposals) is very interesting and I am afraid to say that all the points of view are relevant. But the core idea of Jonas is to get a kind of samples database where access is defined by key-word as "columnset" or "frame", etc. I don't know if making this kind of tool is as simple as it appears to be, but why not ? Surely, the individual (or group) has to be very devoted. Certainly it is possible to get code containing many errors, but Jonas would be inspired to get a further enquiry on this matter. Surely, there is a need to access quickly to the relevant information, but I don't know if it is possible to clear the way much more than the ConTeXt Garden wiki allows to do so.

I order to learn ConTeXt for my own purpose and work, I have begun to start a Wikibook, because a few months ago I simply didn't know the name of ConTeXt, but I was sure that it was a best way for me to use it than LaTeX : my aim was not to build a very well structured database, but to get some code with samples on the same page (as a quick first help), chapter by chapter, from simple to complex (e. g. "simple frame"; "frame in a column" etc.) in order to access quickly to my documentation, and to help beginners like me. I feed this "database" with ConTeXt Garden samples and with test samples from the mailing-list, as long as I can understand them (I am not a mathematician, only someone who needs to print classical texts) : https://fr.wikibooks.org/wiki/ConTeXt 

A simple question : is it usefull to get a very quick access to a documentation where explanation is absent ? That's why the current explanation is very useful : even if you have to read full pages at length, the explanation given in the PDF documentation is an accurate information and oftenly says something which allow to lead to a solve your issue. So, it seems there is a conflict between the desire of a quick access to relevant information and the need of learning ConTeXt with patience !
JP



----- Mail original -----
De: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
À: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Envoyé: Lundi 10 Octobre 2016 09:57:24
Objet: Re: [NTG-context] Ideas for improving documentation of ConTeXt

On 10/10/2016 07:43 AM, Jonas Baggett wrote:
>
> Thanks for your encouragement ! Yes that looks like an interesting
> challenge for me, but it is not something I am wanting to do alone
> because of my lack of experience, at least I would need someone to coach
> me. Actually I don't have really experience with web developpment and I
> would at least need help for the technological choices. Having someone
> that tells me that if I use technology X, there are module Y and Z that
> will be a good fit is a good start.

Just two small remarks:

1. there are not that many modules in ConTeXt because most of the 
functionality is in the core. If you come from the LaTeX world, you may 
expect several hundred packages, each with their own idiosyncracies and 
documentation. That's not the case here.

2. As for your documentation project, let me be honest: unless someone 
very dedicated and very knowledgeable makes a long-term commitment and 
looks after these examples, they are worse than useless. Unless there is 
very tight control, they may contain bad and/or outdated code and lead 
newcomers in the wrong direction. The context way has always been to 
avoid boilerplate templates and let users roll their own styles. Which 
makes sense since in context almost every detail can be changed easily 
via dedicated setup commands. (This is again quite unlike LaTeX and its 
document classes that predefine many details.) I have problems imagining 
a collection of sample documents that will be more than a haphazard 
bunch of fortuitous designs.

Thomas
___________________________________________________________________________________
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
___________________________________________________________________________________
___________________________________________________________________________________
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://context.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2016-10-10 17:04 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-09 11:18 Jonas Baggett
2016-10-09 13:49 ` Yi Qingliang
2016-10-10  5:21   ` Jonas Baggett
2016-10-09 19:31 ` Henri Menke
2016-10-09 22:49   ` Jonas Baggett
2016-10-10  7:35     ` Hans Hagen
2016-10-11 21:36       ` Jonas Baggett
2016-10-09 20:51 ` Wolfgang Schuster
2016-10-10  5:43   ` Jonas Baggett
2016-10-10  7:24     ` Hans Hagen
2016-10-11 21:05       ` Jonas Baggett
2016-10-12 11:30       ` Jonas Baggett
2016-10-12 15:29         ` Yi Qingliang
2016-10-12 15:33           ` Mica Semrick
2016-10-12 17:32             ` Jonas Baggett
2016-10-12 17:45               ` Bomber K.
2016-10-12 17:55           ` Bomber K.
2016-10-10  7:57     ` Thomas A. Schmitz
2016-10-10 17:04       ` Jean-Pierre Delange [this message]
2016-10-10 17:34         ` Hans Hagen
2016-10-10 21:41         ` Henning Hraban Ramm
2016-10-11  5:20           ` Jean-Pierre Delange
2016-10-12 21:18         ` Jonas Baggett
2016-10-12 10:17       ` Jonas Baggett
2016-10-10  5:32 ` Aditya Mahajan
2016-10-10  5:43   ` Aditya Mahajan
2016-10-11 20:26     ` Jonas Baggett
2016-10-11 20:40       ` Henning Hraban Ramm
2016-10-12 21:27         ` Jonas Baggett
2016-10-13  8:15           ` Henning Hraban Ramm
2016-10-13  9:23             ` Aditya Mahajan

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=837405983.265372955.1476119068519.JavaMail.root@spooler6-g27.priv.proxad.net \
    --to=adeimantos@free.fr \
    --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).