ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Bruce Horrocks <ntg@scorecrow.com>
To: ntg-context mailing list <ntg-context@ntg.nl>
Subject: [NTG-context] Re: Wiki - test/proposal to further clarify documentation
Date: Sat, 18 May 2024 12:27:02 +0100	[thread overview]
Message-ID: <32166670-3A38-4B32-B550-BC7B127664DC@scorecrow.com> (raw)
In-Reply-To: <171597844497.1997.9206541019414638686@cgl.ntg.nl>

On 17 May 2024, at 21:40, garulfo@azules.eu wrote:
> 
> I have tested on 2 pages :
> - https://wiki.contextgarden.net/Sciences (only mathematics part)
> - https://wiki.contextgarden.net/Fonts
> 
> After these tests, I think this may help users to find their way around the various sources of documentation :
> In one small table he/she has an overview of the documentation for a given topic,  :
> - the few key tutorials
> - link to one "main wiki page" about the topic
> - the few key manuals
> - the reference for commands

The fonts page is a lot better than before[1], IMHO. I would prefer the table were 90% width rather than 50 but that is minor.

So is the plan to go through each of the main headings in the left side-bar and make the same type of change?

> 
> I'm not sure I've selected the few documents that are considered by the community as the key tutorials.
> Thanks for your feedback again.

I don't think that is a problem - the Wiki can be updated by others as long as the layout/structure of the page is clear so people know where to add links.

> PS : in order to benefit from mediawiki page organization features, I moved some pages, for example
> wiki.contextgarden.net/blablabla
> ==> wiki.contextgarden.net/Topic/blablabla


[1] Previous style for reference: <https://web.archive.org/web/20231116125758/https://wiki.contextgarden.net/Fonts>
—
Bruce Horrocks
Hampshire, UK

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2024-05-18 11:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-14 11:21 [NTG-context] " garulfo
2024-04-14 14:14 ` [NTG-context] " Henning Hraban Ramm
2024-04-14 19:45   ` Peter Hopcroft via ntg-context
2024-04-16 19:07     ` Henning Hraban Ramm
2024-04-16 19:56       ` Peter Hopcroft via ntg-context
2024-04-17  6:32         ` Thomas A. Schmitz
2024-04-17  8:36           ` Hans Hagen
2024-04-17  8:47             ` Henning Hraban Ramm
2024-04-17  9:10               ` Joaquín Ataz López
2024-04-17  9:32                 ` jbf
2024-04-17 11:57 ` Bruce Horrocks
2024-04-17 12:17   ` Henning Hraban Ramm
2024-04-18 12:48     ` Bruce Horrocks
2024-04-17 21:25   ` Garulfo
2024-04-18  6:32     ` Henning Hraban Ramm
2024-05-17 20:40 ` garulfo
2024-05-18 11:27   ` Bruce Horrocks [this message]
2024-05-19 12:44     ` garulfo

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=32166670-3A38-4B32-B550-BC7B127664DC@scorecrow.com \
    --to=ntg@scorecrow.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).