ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: [NTG-context] Re: ConTeXt-StarterKit: A Ready-to-Use Template for ConTeXt LMTX
Date: Mon, 22 Sep 2025 09:03:37 +0200	[thread overview]
Message-ID: <df287410-8b3a-4bbf-a6bf-d2d766f1b5a0@xs4all.nl> (raw)
In-Reply-To: <175852059749.2544.6007297966156293014@cgl.ntg.nl>

On 9/22/2025 7:56 AM, seyal.zavira@gmail.com wrote:
> Hi Peter,
> 
> Thank you so much for the kind words! I'm really glad to hear that the starter kit looks useful to you.
> 
> That's exactly one of the goals I had in mind—to make it easier to spin up smaller projects without the usual setup overhead.
> 
> Any feedback you might have would be incredibly valuable.

I took a quick look (not much time now) but I'm sure others will reflect 
on details but one thing I noticed is that you use a lot of \input while 
at the same time assuming some project structure. Best look into 
\environment, \component and alike because then one can process units, 
prevent duplicate loading (which at some point will clash with 
overloadprotection), provide cross unit referencing, get level-up file 
lookups for free, etc.

Also, maybe use 'document' instead of 'project' as main variable 
namespace because that one has some other benefits.

Some of the larger manuals are structured this way so they might act as 
example.

When it comes to file lookups: texmf-project and texmf-fonts are also a 
place to put files under (tex/user/<project>) because these are part of 
general the file database lookup; beware of duplicate copied of fonts 
with the same name because of what ends up in the font cache (different 
versions can clash then).

Hans



-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2025-09-22  7:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-20 13:35 [NTG-context] " seyal.zavira
2025-09-22  5:02 ` [NTG-context] " peter.hopcroft--- via ntg-context
2025-09-22  5:56   ` seyal.zavira
2025-09-22  7:03     ` Hans Hagen via ntg-context [this message]
2025-09-22 15:46       ` seyal.zavira
2025-09-22 16:30         ` Hans Hagen via ntg-context
2025-09-22 17:06           ` Pablo Rodriguez via ntg-context
2025-09-23  7:00             ` Hans Hagen via ntg-context
2025-09-23 14:21             ` Bruce Horrocks

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=df287410-8b3a-4bbf-a6bf-d2d766f1b5a0@xs4all.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@xs4all.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).