ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Ideas for improving documentation of ConTeXt
Date: Sun, 9 Oct 2016 22:32:27 -0700 (PDT)	[thread overview]
Message-ID: <alpine.OSX.2.02.1610092229010.8140@nqv-znpobbx> (raw)
In-Reply-To: <eb71b9cd-f4ec-2c6e-af62-e4d65acb9446@tranquille.ch>

On Sun, 9 Oct 2016, Jonas Baggett wrote:

> The basic idea I have is a database of ConTeXt documents, where everyone 
> can add his own documents. We have also to make it easy to find there 
> insightful examples in ConTeXt that will help someone to achieve what he 
> is trying to do. Then users, especially beginners, will less likely be 
> stuck at one point and looking for hours for a solution and less help 
> will be asked on the mailing list too.

Recently, stackexchange started a similar project:
https://blog.stackoverflow.com/2016/07/introducing-stack-overflow-documentation-beta/

You can create a context tag and create example documents. The difficulty 
with such projects, as usual, is to have a critical mass for others to 
browse and contribute. One could start by "porting" existing examples from 
the wiki, mailing list, tex.stackexchange, etc.

Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2016-10-10  5:32 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
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 [this message]
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=alpine.OSX.2.02.1610092229010.8140@nqv-znpobbx \
    --to=adityam@umich.edu \
    --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).