From: Tim Cross <theophilusx@gmail.com>
To: Leo Butler <Leo.Butler@umanitoba.ca>
Cc: "alain.cochard@unistra.fr" <alain.cochard@unistra.fr>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: [TASK] Enhance Worg HTML styling
Date: Fri, 06 Jan 2023 12:23:54 +1100 [thread overview]
Message-ID: <86r0w8xwtp.fsf@gmail.com> (raw)
In-Reply-To: <87y1qgu44r.fsf@t14.reltub.ca>
Leo Butler <Leo.Butler@umanitoba.ca> writes:
> On Fri, Jan 06 2023, Tim Cross <theophilusx@gmail.com> wrote:
>
>> Alain.Cochard@unistra.fr writes:
>>
>>> Tim Cross writes on Thu 5 Jan 2023 09:43:
>>>
>>> > As a simple example, try increasing the font size and see what
>>> > happens to the menus. Keep in mind that some users require a very
>>> > large font (for example, I use a 26 or 28 pt font.
>>>
>>> OK, I understand. (Even with default font size, I hate that the table
>>> of contents hides some parts of the text -- I had forgotten about
>>> that.)
>>>
>>> > [...] There have also been numerous other issues (many have already
>>> > been addressed) such as broken links, links to data which doesn't
>>> > exist or has wrong MIME type [...] Perhaps even more unfortunate
>>> > is that sometimes, you can come across some good information in the
>>> > worg site, but finding that same information again at a latter date
>>> > is often extremely challenging.
>>>
>>> But that's not "Org styling", right? Or am I confused about what
>>> "styling" means?
>>>
>>> At any rate, I agree with your other examples, understand why the
>>> styling (as I understand it) should be improved, and am no longer
>>> worried about changes. Thank you very much for your time.
>>
>> It isn't just about the styling - that is just one aspect and the one I
>> planned to start with. However, styling and presentation will also be
>> part of providing better links/navigation, which I think is also
>> necessary to make exploration and discovery easier and more consistent.
>> .
>
> Can you give us an example/model of a site that does these things
> better? I agree with your assessment, but feel that some kind of target
> is needed.
>
> TIA,
> Leo
As Bastien said, small increments is likely the way to go.
So, for an initial target, how about just having set of CSS styles which
support different screen sizes and different font sizes - one where,
unlike the current one, the page content is not obscured by the menus
and navigation buttons.
For an added bonus, a design which provides consistency and convenience
which helps with both general browsing and locating specific information
within the site would be good.
As for an example site, I don't have anything specific in mind and have
ideas taken from various sites. Examples are of little benefit IMO - it
really just comes down to someone having the time to define a new style,
apply it to a development site (likely also on sourcehut) and then get
feedback. We don't need to over think this or get too bogged down in
design - just go for functional and see what falls out the other end.
One question I'm not sure about is whether it would be better to craft
CSS from scratch or better to adopt a CSS framework (which is
appropriately licensed) and use that. I tend to feel the latter would be
better, but others may have different opinions.
next prev parent reply other threads:[~2023-01-06 1:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 21:51 [accessibility] worg obscures text Samuel Wales
2022-06-12 19:35 ` Rudolf Adamkovič
2022-06-13 0:22 ` Tim Cross
2022-06-13 0:34 ` Ihor Radchenko
2022-06-13 2:16 ` Tim Cross
2022-06-13 5:30 ` [BUG] worg-setup.org is outdated (was: [accessibility] worg obscures text) Ihor Radchenko
2022-06-13 5:44 ` Tim Cross
2022-06-13 6:14 ` Timothy
2022-06-13 14:21 ` [BUG] worg-setup.org is outdated Bastien Guerry
2022-06-13 14:21 ` Bastien Guerry
2022-06-13 22:32 ` Tim Cross
2022-06-14 0:57 ` Ihor Radchenko
2022-06-14 1:08 ` Tim Cross
2022-06-14 1:37 ` Ihor Radchenko
2022-06-14 1:51 ` Tim Cross
2022-06-14 2:18 ` Ihor Radchenko
2022-06-14 2:46 ` Tim Cross
2022-06-14 2:59 ` Ihor Radchenko
2023-01-02 10:40 ` Ihor Radchenko
2023-01-02 20:03 ` Tim Cross
2023-01-03 11:01 ` Ihor Radchenko
2023-01-04 10:21 ` [TASK] Enhance Worg HTML styling (was: [BUG] worg-setup.org is outdated) Bastien Guerry
2023-01-04 10:50 ` Alain.Cochard
2023-01-04 22:43 ` Tim Cross
2023-01-05 14:07 ` Alain.Cochard
2023-01-05 15:41 ` Tim Cross
2023-01-05 20:18 ` [TASK] Enhance Worg HTML styling Leo Butler
2023-01-06 1:23 ` Tim Cross [this message]
2022-06-13 5:37 ` [accessibility] worg obscures text Max Nikulin
2022-06-16 3:22 ` Tim Cross
2022-06-16 23:30 ` Samuel Wales
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://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86r0w8xwtp.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=Leo.Butler@umanitoba.ca \
--cc=alain.cochard@unistra.fr \
--cc=emacs-orgmode@gnu.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.savannah.gnu.org/cgit/emacs/org-mode.git
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).