From: Rich Brown <richb.hanover@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"Dave Taht" <dave.taht@gmail.com>,
bloat <bloat@lists.bufferbloat.net>
Cc: "Richard E. Brown" <richb.hanover@gmail.com>
Subject: [Bloat] Bufferbloat.net - Organizing, curating, and workflow
Date: Sun, 12 Jun 2016 13:49:00 -0400 [thread overview]
Message-ID: <2BB7767C-F58D-4A91-9EDF-03C9DD31D882@gmail.com> (raw)
In-Reply-To: <87wplvij9r.fsf@toke.dk>
To all the Bufferbloaters out there...
Thanks again to Toke for all this good work. It's terrific to see the pages resurrected, and to have the www.bufferbloat.net site living again.
I've been thinking of the next steps - to make all this work really useful. I see there are three important issues:
Organizing: Thinking about the best way to display the current information:
- Should Cake be listed as a top-level project?
- Is there a way to display newest entries? I'd like to see a sidebar element showing the 5 newest posts
- Can an RSS feed be generated automatically?
Curating: The current site makes it seem as if all pages are equally important. I feel the urge to do the following:
- Categorizing the "List of Wiki Pages" for a project (e.g., http://bufferbloat.net/projects/cerowrt/ )
so there's a sense of their importance
- Discard old/outdated/useless articles
Workflow:
- Rules for making posts: Who can make them? How do they get published?
- Auto-publish - if it's not already happening, could we re-render and publish after a commit?
- I see the 404 handler in place, but it doesn't seem to show a link to archive.org
- Is there a way to do page redirection? It looks as if Toke has done a great job of replicating
URLs in the new site, but if we see frequent broken links, is there a way to redirect a page to its equivalent on the new site?
- Should we add a Google search box on 404 page? On every page?
- Would it make sense to review error logs from time to time?
I'd love to have your thoughts. Thanks.
Rich
next prev parent reply other threads:[~2016-06-12 17:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1225.1465559858.3642.bloat@lists.bufferbloat.net>
2016-06-10 15:27 ` [Bloat] bufferbloat.net is sorely missed Rich Brown
2016-06-10 15:47 ` Dave Taht
2016-06-10 16:19 ` Rich Brown
2016-06-10 17:08 ` Kevin Darbyshire-Bryant
2016-06-10 17:13 ` Outback Dingo
2016-06-10 18:05 ` Dave Taht
2016-06-10 18:17 ` Steinar H. Gunderson
2016-06-10 18:18 ` Rich Brown
2016-06-10 18:23 ` Dave Taht
2016-06-11 12:07 ` Toke Høiland-Jørgensen
2016-06-11 17:58 ` Dave Taht
2016-06-11 18:29 ` Toke Høiland-Jørgensen
2016-06-11 18:32 ` Toke Høiland-Jørgensen
2016-06-11 19:09 ` Dave Taht
2016-06-11 19:24 ` [Bloat] bufferbloat.net is sorely missed/Now it's back! Rich Brown
2016-06-11 20:05 ` Toke Høiland-Jørgensen
2016-06-11 21:31 ` Dave Taht
2016-06-12 17:49 ` Rich Brown [this message]
2016-06-12 18:02 ` [Bloat] Bufferbloat.net - Organizing, curating, and workflow Toke Høiland-Jørgensen
2016-06-12 18:13 ` moeller0
2016-06-12 18:16 ` Toke Høiland-Jørgensen
2016-06-12 18:24 ` moeller0
2016-06-12 18:25 ` Toke Høiland-Jørgensen
2016-06-12 18:27 ` Dave Taht
2016-06-12 18:33 ` Toke Høiland-Jørgensen
2016-06-13 13:25 ` Rich Brown
2016-06-13 14:05 ` Toke Høiland-Jørgensen
2016-06-13 15:13 ` [Bloat] Bufferbloat.net & LinkChecker Rich Brown
2016-06-13 19:18 ` Toke Høiland-Jørgensen
2016-06-13 14:58 ` [Bloat] Bufferbloat.net - Organizing, curating, and workflow Dave Taht
2016-06-13 15:15 ` Toke Høiland-Jørgensen
2016-06-13 15:39 ` Dave Taht
2016-06-13 10:33 ` [Bloat] bufferbloat.net is sorely missed/Now it's back! Kevin Darbyshire-Bryant
2016-06-13 11:10 ` Toke Høiland-Jørgensen
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://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2BB7767C-F58D-4A91-9EDF-03C9DD31D882@gmail.com \
--to=richb.hanover@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=toke@toke.dk \
/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