From: Pawel Urbanski via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Pawel Urbanski <urbanski.pawel@gmail.com>
Subject: [NTG-context] Idea for a shared repository.
Date: Tue, 25 Apr 2023 12:28:36 +0200 [thread overview]
Message-ID: <ee2c56c7-5606-204e-c2b2-0c55fbcaa261@gmail.com> (raw)
Dear Everyone,
We currently have the Context Garden site, wiki and htis list for
documentation and resources.
There is a Github contextgarden organization that can host repositories.
What about creating a repository called: 'templates' or 'resources' - we
can figure out the exact name later.
The idea behind it is to collect templates and examples that are
scattered all over the web or in the list threads. The first example
that comes to my mind is the type definition for a Roboto font I needed
and other type scripts that can be useful for the community. Then there
are templates for books, slides or documents. The Repository has a wiki
where we could add some notes about more complex items.
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.
All the best,
Pawel
___________________________________________________________________________________
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
___________________________________________________________________________________
next reply other threads:[~2023-04-25 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 10:28 Pawel Urbanski via ntg-context [this message]
2023-04-25 15:13 ` Aditya Mahajan via ntg-context
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=ee2c56c7-5606-204e-c2b2-0c55fbcaa261@gmail.com \
--to=ntg-context@ntg.nl \
--cc=urbanski.pawel@gmail.com \
/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).