From: Dworkin Muller <dlm-9fans@weaselfish.com>
To: 9fans@9fans.net, sl@stanleylieber.com
Subject: Re: [9fans] 9front hardware list
Date: Thu, 05 Jun 2025 22:55:22 -0600 (MDT) [thread overview]
Message-ID: <20250605.225522.1218868435901415626.dlm-9fans@weaselfish.com> (raw)
In-Reply-To: <0C575F58D15C7205D4959143C9EC0E28@gaff.inri.net>
On Thu, 05 Jun 2025 22:46:16 -0400, sl@stanleylieber.com wrote:
sl> 2.) the specific url points to a top-level directory containing that
sl> same comprehensive list. look at the menu links on the left side of
sl> the page.
sl>
sl> 3.) i sometimes sell hardware. i put a short list of stuff in that
sl> same top-level directory's index page (plan9 -> stanleylieber ->
sl> hardware; it makes sense if you think about it).
Kinda sorta ;-)
You might want to put a one-liner at the top of the index page (right
after the ``hardware'' label that comes before the ``come and take
it'' image) along the lines of ``please find information about
specific makers/brands/whatever in the menu at left''. For whatever
reason, it wasn't obvious that the brands were subordinate to the
landing page; they looked to be at the same level. This is quite
possibly a rendering quirk of my browser, which shows such menus fully
expanded rather than as a cascade that you pull a mouse through. The
large image and ``FOR SALE'' right under it may have acted to distract
me from rendering niceties on the left, as well.
So, quite possibly purely a user error at my end, but it might not
hurt to be more explicit. Just a suggestion, of course.
Thanks for the explanation.
Dworkin
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tb811a315361892f5-M541cfa641d0d96941a3df6de
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
prev parent reply other threads:[~2025-06-06 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 1:51 Dworkin Muller
[not found] ` <0C575F58D15C7205D4959143C9EC0E28@gaff.inri.net>
2025-06-06 4:55 ` Dworkin Muller [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=20250605.225522.1218868435901415626.dlm-9fans@weaselfish.com \
--to=dlm-9fans@weaselfish.com \
--cc=9fans@9fans.net \
--cc=sl@stanleylieber.com \
/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).