From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: [RFC] render Manual.md with mdBook
Date: Sun, 21 Aug 2022 20:47:47 +0200 [thread overview]
Message-ID: <20220821184747.CMJoWMqNBXNcBpIQt9xRJcCf6ACXzyYnrr-HJUF3P9Y@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35856@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 762 bytes --]
There's a closed pull request on the void-packages repository
[RFC] render Manual.md with mdBook
https://github.com/void-linux/void-packages/pull/35856
Description:
This idea was mentioned once on IRC, so I thought I might take a stab at it and submit it for discussion.
I set out to create a version of `Manual.md` that is a bit more user/noob-friendly than a giant monolith of a document, while still preserving the workflow surrounding it. Thus, I created a mdBook pre-processor that processes Manual.md and builds the book, without the need for converting Manual.md *into* an mdBook.
A live example of what is currently generated by mdBook is available here: https://book.qrm.cat/
The only thing this needs is a deployment mechanism.
[ci skip]
prev parent reply other threads:[~2022-08-21 18:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 2:49 [PR PATCH] [RFC] Create a version of Manual.md in mdBook classabbyamp
2022-03-06 3:06 ` [PR PATCH] [Updated] " classabbyamp
2022-03-15 19:17 ` classabbyamp
2022-04-01 19:24 ` classabbyamp
2022-04-01 19:26 ` classabbyamp
2022-04-01 19:29 ` classabbyamp
2022-04-01 19:30 ` classabbyamp
2022-04-02 5:07 ` classabbyamp
2022-04-02 17:50 ` classabbyamp
2022-04-02 21:40 ` classabbyamp
2022-04-07 17:40 ` classabbyamp
2022-04-19 15:28 ` classabbyamp
2022-04-23 1:23 ` [PR PATCH] [Updated] [RFC] render Manual.md with mdBook classabbyamp
2022-05-02 2:09 ` classabbyamp
2022-05-05 17:24 ` classabbyamp
2022-05-05 18:41 ` classabbyamp
2022-05-17 17:09 ` classabbyamp
2022-05-28 7:03 ` classabbyamp
2022-05-28 20:05 ` classabbyamp
2022-05-29 0:12 ` classabbyamp
2022-06-26 23:49 ` classabbyamp
2022-07-17 18:33 ` [PR REVIEW] " ericonr
2022-07-17 18:34 ` ericonr
2022-07-18 5:13 ` [PR PATCH] [Updated] " classabbyamp
2022-07-18 5:13 ` [PR REVIEW] " classabbyamp
2022-08-21 18:47 ` classabbyamp
2022-08-21 18:47 ` classabbyamp [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=20220821184747.CMJoWMqNBXNcBpIQt9xRJcCf6ACXzyYnrr-HJUF3P9Y@z \
--to=classabbyamp@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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).