From: Austin Traver <austintraver@icloud.com>
To: Oliver Kiddle <opk@zsh.org>
Cc: zsh-workers@zsh.org
Subject: Re: I'd like to help maintain the Zsh Web Page
Date: Sun, 28 Mar 2021 20:39:59 -0700 [thread overview]
Message-ID: <D71BA465-E023-4461-8C64-BCFA6B149A3A@icloud.com> (raw)
In-Reply-To: <84773-1616980819.919111@ybx2.QGzt.Gdnm>
[-- Attachment #1: Type: text/plain, Size: 1634 bytes --]
> The actual documentation is… not written in HTML but in a macro language named yodl
I've worked with groff in the past, so I'm at least acquainted with macro packages such as mdoc. Yodl, I'm still working on learning, but I see this as a chance to learn something new.
> The man pages are possibly the most
> important form for the documentation.
I agree entirely, don't know what I'd do without them!
> I'm not sure whether that can be
> replicated from markdown but it really would need to be. texi2html is
> quite configurable if we just want to tweak the web version of the
> documentation.
I'll make a first attempt using texi2html and let you guys know how it goes.
> I'm not saying it has to be this way forever but take the
> time to understand it first so you don't end up doing a lot of work that
> goes to waste.
In the past, I've learned the hard way what happens when developers build software now and understand requirements later. Not a fun time for anyone. I'll be sure to do this work in the correct order.
> The documentation is in a Doc directory alongside the source code -
> https://git.code.sf.net/p/zsh/code
> There are mirrors on github and gitlab if you prefer.
> Sourceforge website content is https://git.code.sf.net/p/zsh/web
> zsh.org website content is only the one file, so curl or saving from
> firefox is probably easiest.
>
> Oliver
Sounds good! If I reach a checkpoint, I'll post it to https://github.com/austintraver/zsh <https://github.com/austintraver/zsh>
Which remote (and branch) would I make a pull request to, when done?
Best,
Austin
[-- Attachment #2: Type: text/html, Size: 3006 bytes --]
next prev parent reply other threads:[~2021-03-29 3:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 17:07 Austin Traver
2021-03-27 20:57 ` Daniel Shahaf
2021-03-27 20:59 ` Daniel Shahaf
2021-03-29 0:02 ` Oliver Kiddle
2021-03-29 0:39 ` Austin Traver
2021-03-29 1:20 ` Oliver Kiddle
2021-03-29 3:39 ` Austin Traver [this message]
2021-04-07 8:19 ` Austin Traver
2021-03-29 7:24 ` Daniel Shahaf
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=D71BA465-E023-4461-8C64-BCFA6B149A3A@icloud.com \
--to=austintraver@icloud.com \
--cc=opk@zsh.org \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).