ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan via ntg-context <ntg-context@ntg.nl>
To: Pawel Urbanski via ntg-context <ntg-context@ntg.nl>
Cc: Aditya Mahajan <adityam@umich.edu>
Subject: Re: [NTG-context] Idea for a shared repository.
Date: Tue, 25 Apr 2023 11:13:57 -0400 (EDT)	[thread overview]
Message-ID: <n202qs37-011r-4947-n5n3-3n775p9rr3sp@hzvpu.rqh> (raw)
In-Reply-To: <ee2c56c7-5606-204e-c2b2-0c55fbcaa261@gmail.com>

On Tue, 25 Apr 2023, Pawel Urbanski via ntg-context wrote:

> What about creating a repository called: 'templates' or 'resources' - we can
> figure out the exact name later.

Why not use the wiki for such documents? For fonts, there is already a wiki page collecting typescripts:

https://wiki.contextgarden.net/Typescripts_examples

There are also a collection of templates which are already on the wiki:

https://wiki.contextgarden.net/Category:Sample_documents


> It is not about duplicating the Context garden site but to collect code in a
> place where we could gradually fix possible errors or introduce improvements.

This can be done on the wiki as well.

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

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2023-04-25 15:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-25 10:28 Pawel Urbanski via ntg-context
2023-04-25 15:13 ` Aditya Mahajan via ntg-context [this message]
2023-04-25 15:38   ` Henning Hraban Ramm via ntg-context

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=n202qs37-011r-4947-n5n3-3n775p9rr3sp@hzvpu.rqh \
    --to=ntg-context@ntg.nl \
    --cc=adityam@umich.edu \
    /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).