From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Cc: Philip Oakley <philipoakley@iee.org>
Subject: [PATCH 0/2] begin online help for each public-inbox
Date: Thu, 18 Aug 2016 09:51:48 +0000 [thread overview]
Message-ID: <20160818095150.17118-1-e@80x24.org> (raw)
I expect this will be tweaked and edited heavily in coming
weeks, but this at least a start.
I'll be keeping everything within the constraints of a
plain-text email, so no cheating with styling or #fragment
tags, and definitely no deceptive hiding of URLs to external
resources.
Fortunately, deploying changes are cheap and relatively
risk-free with zero user-visible downtime
(which also needs to be documented :x)
Thanks to Philip Oakley at the git list for reminding me the
design_www document is actually helpful to users, not just
hackers :)
https://public-inbox.org/git/D5A2E231FFE74D1C891A1653E1C2D797@PhilipOakley/
Eric Wong (2):
www: implement generic help text
searchview: link to internal help text
MANIFEST | 2 +
lib/PublicInbox/Search.pm | 38 ++++++++
lib/PublicInbox/SearchView.pm | 5 +-
lib/PublicInbox/WWW.pm | 14 +++
lib/PublicInbox/WwwStream.pm | 4 +-
lib/PublicInbox/WwwText.pm | 201 ++++++++++++++++++++++++++++++++++++++++++
t/psgi_text.t | 39 ++++++++
7 files changed, 299 insertions(+), 4 deletions(-)
create mode 100644 lib/PublicInbox/WwwText.pm
create mode 100644 t/psgi_text.t
--
EW
next reply other threads:[~2016-08-18 9:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 9:51 Eric Wong [this message]
2016-08-18 9:51 ` [PATCH 1/2] www: implement generic help text Eric Wong
2016-08-18 9:51 ` [PATCH 2/2] searchview: link to internal " Eric Wong
2016-08-18 19:29 ` [PATCH 0/2] begin online help for each public-inbox Philip Oakley
2016-08-18 19:33 ` Eric Wong
2016-08-26 19:30 ` Favicon for (each) public-inbox Philip Oakley
2016-08-28 9:46 ` Eric Wong
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160818095150.17118-1-e@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
--cc=philipoakley@iee.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 read-only IMAP folder(s) and NNTP newsgroup(s).