From: Tom Rymes <trymes@rymes.com>
To: documentation@lists.ipfire.org
Subject: Re: New wiki painful to use
Date: Thu, 05 Sep 2019 17:23:14 -0400 [thread overview]
Message-ID: <04881e1c-e3e3-a313-7b90-ea2ba0694bc3@rymes.com> (raw)
In-Reply-To: <243BC9D2-62A4-4EC5-8BAC-2D72AD9EB015@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1979 bytes --]
I'm with John on this one, the modified version is inferior. I get that
we need to be conscious of color-blindness, but the new version doesn't
work for anyone. May I suggest:
Green Checkmark: Very well supported.
Empty Yellow Circle: Basic Support.
Red "X": Does not work.
Universal Prohibition Symbol: Does not work and no support planned.
Tom
On 09/05/2019 4:52 PM, Jon Murphy wrote:
> Honestly? I think it is too 'flat' and lacks color. The original table was almost perfect.
>
>
> Suggestions:
>
> Use Harvey balls - https://en.wikipedia.org/wiki/Harvey_balls
> -or-
> Use Okto symbols - https://en.wikipedia.org/wiki/Okta
> -or-
> Something similar to Consumer Reports rating symbols:
> https://www.consumerreports.org/video/view/inside-labs/5131824875001/our-ratings--consumer-reports/
>
>
> And it should include color. <—-- One of those things we disagree on
>
> EDIT - added mailing list.
>
>>
>>
>> Hi,
>>
>> Yes, I think this works. What do you think?
>>
>> -Michael
>>
>>> On 3 Sep 2019, at 23:19, Jon Murphy <jcmurphy26(a)gmail.com> wrote:
>>>
>>> Michael - Is this what you are looking for?
>>>
>>>
>>> https://wiki.ipfire.org/hardware/arm/playground
>>>
>>> It is split into three different Tables:
>>> • Well Supported (was green before)
>>> • Basic support (was yellow before)
>>> • 'Does not work' and 'Does not work and no support planned' (was red and black before)
>>>
>>> Here is the old page with colors:
>>> https://wiki.ipfire.org/hardware/arm
>>>
>>>
>>>>
>>>>> 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?
>>>>
>>>
>>
>
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> https://lists.ipfire.org/mailman/listinfo/documentation
>
next prev parent reply other threads:[~2019-09-05 21:23 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
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 [this message]
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=04881e1c-e3e3-a313-7b90-ea2ba0694bc3@rymes.com \
--to=trymes@rymes.com \
--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