From: Kurt H Maier <khm@sciops.net>
To: 9front@9front.org
Subject: Re: [9front] RFC: add a downloads.md page
Date: Tue, 18 Aug 2020 16:40:33 -0700 [thread overview]
Message-ID: <20200818234033.GE25798@wopr> (raw)
In-Reply-To: <BFC5F2A6-C5D8-4C36-93E5-13839C2576F2@stanleylieber.com>
On Tue, Aug 18, 2020 at 07:34:20PM -0400, Stanley Lieber wrote:
> looked at hiro's downloads.md and reviewed the existing site. i'm not in love with duplicating all these disparate links to individual files that will change with every release. we already put almost all of this stuff into each release announcement. why don't we just replace iso/ with downloads/ and make that load the latest release page, and cause werc to inject a header with the explanatory text? this accomplishes the same thing but only has to be written once. i agree, it should then be linked in the top bar. as far as i'm concerned we can drop the link to the dash1 pdf from the sidebar, reducing clutter alongside other superfluous links like coc/ and n/.
I like this plan, depending on what the explanatory text is explaining.
I don't think it should be a complete education on rendering the media
unto disk; it should be sufficient to mention that the isos are also
bootable usb images and the img files are for sd cards.
> it would also be appropriate to mention the hybrid iso in the corresponding fqa section, and add any other long omitted (four years!) and sorely lacking information, but i sense an underlying urge to segregate frequently questioned answers from the existing collection of frequently questioned answers. "this is natural, but it is done." --malcolm x. maybe someone can submit patches, or at least detail that and other missing info in an article for the new community docs repository. we already link to a mirror of that in the top bar.
This would be a great contribution; for those playing along at home the
fqa source is in https://code.9front.org/hg/fqa.9front.org and you can
send patches to this list.
khm
next prev parent reply other threads:[~2020-08-18 23:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 20:27 hiro
2020-08-18 22:20 ` [9front] " ori
2020-08-18 22:50 ` Stanley Lieber
2020-08-18 23:08 ` Stanley Lieber
2020-08-18 23:34 ` Stanley Lieber
2020-08-18 23:40 ` Kurt H Maier [this message]
2020-08-19 3:52 ` sl
[not found] ` <158A09494BC07582889006A200849F02@ewsd.inri.net>
2020-08-19 12:20 ` hiro
2020-08-19 13:20 ` Stanley Lieber
2020-08-19 13:25 ` hiro
2020-08-19 13:37 ` Stanley Lieber
2020-08-19 13:53 ` hiro
2020-08-19 20:01 ` hiro
2020-08-19 21:59 ` Stanley Lieber
2020-08-20 2:14 ` sl
[not found] ` <54754B562FB01625084E1BA75A9A12C3@ewsd.inri.net>
2020-08-20 2:18 ` hiro
2020-08-20 2:24 ` hiro
2020-08-20 2:30 ` hiro
2020-08-20 2:46 ` ori
2020-08-19 23:12 ` hiro
2020-08-19 23:40 ` Stanley Lieber
2020-08-20 2:14 ` hiro
2020-08-21 17:24 ` Ethan Gardener
2020-08-22 12:59 ` hiro
2020-08-22 15:34 ` Stanley Lieber
2020-08-19 12:15 ` hiro
2020-08-19 12:49 ` telephil9
2020-08-19 13:02 ` hiro
2020-08-19 13:06 ` hiro
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=20200818234033.GE25798@wopr \
--to=khm@sciops.net \
--cc=9front@9front.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).