From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Launching our new website
Date: Tue, 09 Jan 2024 18:55:53 +0000 [thread overview]
Message-ID: <8439145C-EE38-4E06-844D-5DD3EF092319@ipfire.org> (raw)
In-Reply-To: <178D9B0F-56CA-45B1-A4D3-ADAD38E20EA7@rymes.net>
[-- Attachment #1: Type: text/plain, Size: 1749 bytes --]
> On 9 Jan 2024, at 16:47, Tom Rymes <tom(a)rymes.net> wrote:
>
>
>
>> On Jan 9, 2024, at 3:29 AM, Michael Tremer <michael.tremer(a)ipfire.org> wrote:
>>
>> Hello Tom,
>>
>>> On 8 Jan 2024, at 23:31, Tom Rymes <tom(a)rymes.net> wrote:
>>>
>>> FWIW, I also think the community sections of the site should be as prominent as possible. Users go to the site looking to either download or get support. Everything else is probably a rounding error, IMHO.
>>
>> I agree and it is. It just isn’t part of the main navigation which is used to its maximum:
>>
>> <Screenshot 2024-01-09 at 11.25.57.png>
>>
>> We cannot remove About, Download, Blog and Help because that would bring us back to have different pages with different navigations and it would be hard to switch from one to another.
>>
>> We cannot remove the Donate button because we are funded by those.
>>
>> We could find a different place for the avatar, but that would be confusing as this is a standard location, and if we found another place, we would not get enough space to add a Community link.
>>
>> The only candidate there is is Documentation, but I think Documentation outranks the Community portal. We don’t want people to ask the same questions again. We want them to read the documentation.
>>
>> -Michael
>
>
> Perhaps the “Search Documentation” field could be placed on the documentation page and not in the header?
We tried that and it did not work. We would loose too much space on the actual page and distract from the content.
Rather unsurprisingly, people don’t use the search that much, and so it makes sense to have it in the top navigation where pretty much every website has their search boxes.
> Tom
next prev parent reply other threads:[~2024-01-09 18:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <59C89A89-28FA-46D4-BE36-3EF2669F5049@ipfire.org>
2024-01-09 16:47 ` Tom Rymes
2024-01-09 18:55 ` Michael Tremer [this message]
[not found] <C8B85E1E-318F-463C-ACCB-03CAF1506B70@ipfire.org>
2024-01-10 11:01 ` Michael Tremer
[not found] <D2352E78-D298-4090-AAB6-53C842E92AE3@ipfire.org>
2024-01-09 11:33 ` Michael Tremer
[not found] <92869CA1-474F-4124-8B2E-7F0034E0BDE0@ipfire.org>
2024-01-08 18:33 ` Michael Tremer
[not found] <57E1B76D-8F9D-433F-99AF-1A3449443704@rymes.net>
2024-01-06 14:03 ` Michael Tremer
2024-01-07 1:47 ` Tom Rymes
2024-01-07 14:29 ` Michael Tremer
2024-01-07 23:19 ` Robin Roevens
2024-01-08 17:07 ` Michael Tremer
2024-01-09 15:43 ` Robin Roevens
2024-01-09 18:57 ` Michael Tremer
2024-01-04 16:44 Michael Tremer
2024-01-05 14:43 ` Adolf Belka
2024-01-06 14:08 ` Michael Tremer
2024-01-08 13:17 ` Adolf Belka
2024-01-08 17:11 ` Michael Tremer
2024-01-06 15:29 ` 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=8439145C-EE38-4E06-844D-5DD3EF092319@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@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