alain.coch...@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
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
alain.coch...@unistra.fr writes:
> Bastien Guerry writes on Wed 4 Jan 2023 11:21:
>
> > Strong +1 on working on Worg's styling.
> >
> > The task may be daunting, but we can also tackle it incrementally.
> >
> > >From memory, orgmode.org/worg is visited by ~30k persons each month,
> >
Bastien Guerry writes on Wed 4 Jan 2023 11:21:
> Strong +1 on working on Worg's styling.
>
> The task may be daunting, but we can also tackle it incrementally.
>
> >From memory, orgmode.org/worg is visited by ~30k persons each month,
> that 1000 persons per day. A patch enhancing the
Tim Cross writes:
> A significant re-design of the worg styling is required in order to get
> a presentation which both looks good and which works with respect to
> accessibility requirements. I don't believe the current styles are
> workable. Someone with greater CSS fu than me might do better,
Tim Cross writes:
> I would still like to get back to this, but right now, don't know where
> things are likely to be in the short term. There are some job related
> things which will be eitehr completed or stepped up to the next stage by
> mid Feb and I may have a clearer picture by then. For
Ihor Radchenko writes:
> Tim Cross writes:
>
>> First step is to get a working local copy so that I have something to
>> work with. AFter that and a bit of exploring, I should have a better
>> understanding and idea how to go forward.
>
> Hi Tim,
>
> May I know if you got a chance to
Tim Cross writes:
> First step is to get a working local copy so that I have something to
> work with. AFter that and a bit of exploring, I should have a better
> understanding and idea how to go forward.
Hi Tim,
May I know if you got a chance to continue working on this?
Let us know if you
Tim Cross writes:
>> At an occation, FYI another two interesting ideas I noted a while back:
>> https://staticman.net/
>> https://isso-comments.de/docs/
>
> Will certainly have a look. However, I'm a little wary about adding
> comment support. Problem is, once you add comment support, you need
Ihor Radchenko writes:
> Tim Cross writes:
>
>>> Also, you may find https://github.com/oyvindstegard/ox-tagfilter-js
>>> useful.
>>>
>>
>> Thanks, I will check it out.
>
> At an occation, FYI another two interesting ideas I noted a while back:
> https://staticman.net/
>
Tim Cross writes:
>> Also, you may find https://github.com/oyvindstegard/ox-tagfilter-js
>> useful.
>>
>
> Thanks, I will check it out.
At an occation, FYI another two interesting ideas I noted a while back:
https://staticman.net/
https://isso-comments.de/docs/
(that is: comment support for
Ihor Radchenko writes:
>>
>> The thing about a static web site is that it needs good navigation to
>> make it useable and easy to explore (which I think is critical with
>> something like worg). To achieve that, there needs to be some
>> 'knowledge' about the pages and their relationship to
Tim Cross writes:
>> I suspect that the real reason is lack of experience with CSS and JS.
>> Also, we don't really want a high entry barrier for contributors (but
>> then, again, we haven't had many contributors to WORG html side over the
>> years anyway, AFAIK).
>
> I actually think a basic
Ihor Radchenko writes:
> Tim Cross writes:
>
>> Just a couple of questions regarding all of this (really just
>> background and to anyone who may have the knowledge, not just Bastien)
>>
>> Is there any reason we don't use a CSS framework, like bulma or
>> tailwind to manage the CSS? I know
Tim Cross writes:
> Just a couple of questions regarding all of this (really just
> background and to anyone who may have the knowledge, not just Bastien)
>
> Is there any reason we don't use a CSS framework, like bulma or
> tailwind to manage the CSS? I know that using JS can be an issue, but
>
Bastien Guerry writes:
> Hi Ihor,
>
> Ihor Radchenko writes:
>
>> Sorry. worg-setup.org is outdated. Bastien, could you update it?
>
> Done, thanks for the heads up.
Thanks Bastien, that will help!
Just a couple of questions regarding all of this (really just
background and to anyone who
Hi Ihor,
Ihor Radchenko writes:
> Sorry. worg-setup.org is outdated. Bastien, could you update it?
Done, thanks for the heads up.
--
Bastien
Hi Tim,
Tim Cross writes:
> A 'refresh' of the look probably isn't a bad thing. However, getting it
> right and consistent is likely non-trivial. Not sure if my css skills
> are up to it, but willing to have a look at it anyway.
Thanks in advance for looking into this!
--
Bastien
Hi Tim,
Tim Cross writes:
> A ’refresh’ of the look probably isn’t a bad thing. However, getting it
> right and consistent is likely non-trivial. Not sure if my css skills
> are up to it, but willing to have a look at it anyway.
A complete revamp of worg is something I’ve chatted to someone
Ihor Radchenko writes:
> Tim Cross writes:
>
>>> Patches are welcome! We just need someone with knowledge of html/css to
>>> jump in and create a patch for https://git.sr.ht/~bzg/worg (BTW, also
>>> see shiny new https://sr.ht/~bzg/org/).
>>>
>>
>> Sadly, it isn't that simple. You also have
Tim Cross writes:
>> Patches are welcome! We just need someone with knowledge of html/css to
>> jump in and create a patch for https://git.sr.ht/~bzg/worg (BTW, also
>> see shiny new https://sr.ht/~bzg/org/).
>>
>
> Sadly, it isn't that simple. You also have to understand how worg does
> the
21 matches
Mail list logo
