all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Peter Polidoro <peter@polidoro.io>, help-guix@gnu.org
Subject: Re: Project Documentation Workflow
Date: Tue, 05 Sep 2023 19:51:28 +0200	[thread overview]
Message-ID: <86jzt4qzj3.fsf@gmail.com> (raw)
In-Reply-To: <87r0nic5lk.fsf@polidoro.io>

Hi,

On Fri, 01 Sep 2023 at 10:18, Peter Polidoro <peter@polidoro.io> wrote:

> I could solve this using Git tools, such as submodules or subtrees 
> perhaps. I could have a repository that is the documentation 
> skeleton and each project repository would have a reference to 
> that skeleton repository. Then I would probably need to write some 
> script to combine the local project files with the skeleton files 
> to generate the specific project documentation.

Well, from my understanding, you are describing a specific build system
for your documentation. :-)

> I am wondering if a better approach might be to create a Guix 
> package containing the documentation skeleton and each project 
> inherits that package and applies local changes before generating 
> the project documentation. I have not yet used Guix home, but 
> perhaps that can be used for projects as well as home directories 
> for such tasks?

Yeah, maybe having these documentation for each project as Guix
packages, you could share the common build system (script for building
the documentation) and inherit from one package to the other depending
on these projects.

Well, I have never needed to build many documentation. :-)


Cheers,
simon


      reply	other threads:[~2023-09-05 19:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-01 14:18 Project Documentation Workflow Peter Polidoro
2023-09-05 17:51 ` Simon Tournier [this message]

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=86jzt4qzj3.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=peter@polidoro.io \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.