From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: New wiki painful to use
Date: Tue, 27 Aug 2019 17:14:22 +0100 [thread overview]
Message-ID: <BC9E49E8-54ED-4CC5-A60D-F7C61D66021E@ipfire.org> (raw)
In-Reply-To: <3AE2F2BF-0E15-4A22-BA59-8AF10A18342D@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2645 bytes --]
Hi,
> On 27 Aug 2019, at 16:54, Jon Murphy <jcmurphy26(a)gmail.com> wrote:
>
>
>>
>> So I wrote something lightweight and easy in less than 200 lines of JS code (could be 50 lines without comments, etc.). It has the following features:
>>
>> * You can highlight text and then mark it as bold, italic, code or make a headline or link out of it
>> * You can use keyboard shortcuts which I find very neat, because you don’t have to move your hands away from your keyboard. Hover over the icons to see the shortcuts.
>>
>> Let me know if I forgot anything.
>>
>> There is also a link to the “files” section now so that you can upload images with a few clicks only.
>>
>> I only tested this in Safari and FF. So there might be problems with other browsers. IE? No idea. Feedback is of course appreciated.
>
> Looks good! I’ll give it a try and report back.
>
> —
>
> Is there a way to search for image names? It can be a console/terminal command or anything that helps. For now it doesn’t need to be an easy button or anything. There are many images I cannot locate.
>
> Missing Images (quick examples):
> - lcd4linux_ipfire-specific-widget.jpg
> - configuration_logs_url-filter_log.png
> - netfilter-packet-flow.svg.png
> - squidclamav-detection.png
> - addons_icecast_using.png
> - etc…
None of these exist in the database.
We do not have any search for images. I am not sure if it would help to search on the filename, because often they are not very useful.
>>>> I am also quite frustrated about seeing loads of HTML .... This is not how this was intended and we have talked about why this is a bad idea.
>>>
>>> What should I correct? The HTML I remember is:
>>>
>>> <color blue> Example </color> to <span style=“color:blue”> Example </span>
>>>
>>> I believe I wrote to you asking for guidance and did not receive a response.
>>
>> Please do not use *any* HTML.
>>
>> Please do not use any colours. They create barriers for people who cannot see them.
>
> Currently all of the links are red and those will be very difficult to see for people that are red/green color blind. May need to change to purple (or some other color that is color blind friendly.
People who are colourblind will be able to see the link.
It is just impossible for some people who cannot distinguish some shades of green or red if their ARM board is supported.
> I’ll begin to remove the color/span code.
Thank you.
Maybe we should have a list at the top with supported boards and then the second half of the page can be the non-supported boards?
-Michael
next prev parent reply other threads:[~2019-08-27 16:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EEBA0832-ADEA-4DEC-A62A-C0165425A75F@gmail.com>
2019-08-13 1:06 ` dnl
2019-08-14 13:58 ` Michael Tremer
2019-08-14 13:56 ` Michael Tremer
2019-08-15 20:51 ` Jon Murphy
2019-08-27 14:41 ` Michael Tremer
2019-08-27 15:54 ` Jon Murphy
2019-08-27 16:14 ` Michael Tremer [this message]
2019-09-03 22:19 ` Jon Murphy
2019-09-05 9:24 ` Michael Tremer
2019-09-05 20:52 ` Jon Murphy
2019-09-05 21:23 ` Tom Rymes
2019-09-06 12:01 ` Michael Tremer
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=BC9E49E8-54ED-4CC5-A60D-F7C61D66021E@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=documentation@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox