[libre-riscv-dev] wiki usability issues

[Luke Kenneth Casson Leighton]

On Mon, Jun 17, 2019 at 10:56 AM Jacob Lifshay <programmerjake at gmail.com> wrote:

> >  if you can track down the CSS that adds it, feel free to let me know
> > the change that's needed.  you should be able to edit it:
> >  https://libre-riscv.org/local.css
> fixed.

 awesome.

> watch out for needing a full refresh, chrome didn't notice the
> changes with just F5.

 yehyeh, static CSS, cached, with nginx setting quite a long timeout.
Ctrl-F5 tends to work.

> >  there's a way to do that using sitemap.  map directive.  found it.
> > added to the index.
> >  https://libre-riscv.org/sitemap/
> yay

 i'm surprised that adding search was easy.

> >  that's done by adding [[toc]] or something to each page, at a
> > location that the author of that page deems suitable.
> isn't there a way to add some html that's added to every page? if
> there is, maybe have each page link to the sitemap or something.

 mumble, grumble, i seem to recall it's necessary to hand-edit the
ikiwiki html templates, creating a custom theme.

> > it sends completely the wrong message to have authoritative resources
> > for libre-riscv managed completely by some other third party's domain.
> > storing data and resource on other peoples' servers says "we're not
> > competent or fit to run the project".
> ok, I was just thinking that gitlab has a pretty nice interface.

 we tried it, remember?  and ruby and gitlab itself consumed nearly
all of the resources of the entire mythic-beasts.com VM (which is only
GBP 8/month).  it would have been necessary to jump to the next
payment level up, which i seem to recall was double that amount.

> > now, i have no problem with the resources looking like they came
> > straight out of the 1990s, on the basis that if people *really* want
> > better, they can *offer their time and resources to improve it*.
> one part that might help that's easy to do is to switch the background
> color to something other than light yellow, maybe to a very light grey
> or white if you like light colors, otherwise, I'd recommend going with
> a dark background and switching the text to white, which will be more
> work.

 white was too harsh, grey was too dull, it looked.. lifeless.
accidentally set it to a sort-of... well, it's #fff8ff and i kinda
like it :)

> > off-site copy of the configuration *and* the data, perform the upgrade
> > on a test site, and then and only then if that goes well, perform the
> > upgrade "live".
> fun.

 for another time :)

l.