Greetings coreboot community!
One of the items to come out of OSFC and the previous leadership meeting was the need to overhaul coreboot's website to look more "professional" -- like a project which was used by commercial entities large and small, not just something for hobbyists/tinkerers.
The leadership council has decided to move forward with this, and would like to hear from the coreboot community as part of developing requirements. These reqs roughly fall into 3 broad categories: logistical, aesthetic, and content. Some of the ideas been put out so far:
[logistical] * Everything must be owned and run by coreboot - not an outside developer. * Everything must be contained in a git repo (outside of downloadable files like releases). * As much as possible should be generated statically?
[aesthetic] * Use a site-wide top bar for navigation? (similar to https://www.zephyrproject.org)
[content] * Prominent display of companies using coreboot (similar to https://go.dev)
We'd love to hear from anyone else with ideas on how we can improve from the existing site.
regards, Matt
Hi Matt,
since the Zephyr page is more or less unusable without javascript enabled, I'd like to add a requirement that the new website should still be usable with js disabled. The Go language page is still functional without js. I'd say that it's fine if that page looks less nice without js, but it should still be usable without it.
Regards, Felix
On 30/10/2023 18:00, Matt DeVillier wrote:
Greetings coreboot community!
One of the items to come out of OSFC and the previous leadership meeting was the need to overhaul coreboot's website to look more "professional" -- like a project which was used by commercial entities large and small, not just something for hobbyists/tinkerers.
The leadership council has decided to move forward with this, and would like to hear from the coreboot community as part of developing requirements. These reqs roughly fall into 3 broad categories: logistical, aesthetic, and content. Some of the ideas been put out so far:
[logistical] * Everything must be owned and run by coreboot - not an outside developer. * Everything must be contained in a git repo (outside of downloadable files like releases). * As much as possible should be generated statically?
[aesthetic] * Use a site-wide top bar for navigation? (similar to https://www.zephyrproject.org https://www.zephyrproject.org)
[content] * Prominent display of companies using coreboot (similar to https://go.dev https://go.dev)
We'd love to hear from anyone else with ideas on how we can improve from the existing site.
regards, Matt
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
Excellent point, Felix!
On Thu, Nov 2, 2023 at 07:28 Felix Held felix-coreboot@felixheld.de wrote:
Hi Matt,
since the Zephyr page is more or less unusable without javascript enabled, I'd like to add a requirement that the new website should still be usable with js disabled. The Go language page is still functional without js. I'd say that it's fine if that page looks less nice without js, but it should still be usable without it.
Regards, Felix
On 30/10/2023 18:00, Matt DeVillier wrote:
Greetings coreboot community!
One of the items to come out of OSFC and the previous leadership meeting was the need to overhaul coreboot's website to look more "professional" -- like a project which was used by commercial entities large and small, not just something for hobbyists/tinkerers.
The leadership council has decided to move forward with this, and would like to hear from the coreboot community as part of developing requirements. These reqs roughly fall into 3 broad categories: logistical, aesthetic, and content. Some of the ideas been put out so
far:
[logistical]
- Everything must be owned and run by coreboot - not an outside
developer.
- Everything must be contained in a git repo (outside of downloadable
files like releases).
- As much as possible should be generated statically?
[aesthetic]
- Use a site-wide top bar for navigation? (similar to
https://www.zephyrproject.org https://www.zephyrproject.org)
[content]
- Prominent display of companies using coreboot (similar to
https://go.dev https://go.dev)
We'd love to hear from anyone else with ideas on how we can improve from the existing site.
regards, Matt
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
Additionally, the size of zephyrproject.org is ~320k not including the video verses ~6k for coreboot.org
On 11/2/23 10:27, Felix Held wrote:
Hi Matt,
since the Zephyr page is more or less unusable without javascript enabled, I'd like to add a requirement that the new website should still be usable with js disabled. The Go language page is still functional without js. I'd say that it's fine if that page looks less nice without js, but it should still be usable without it.
Regards, Felix
On 30/10/2023 18:00, Matt DeVillier wrote:
Greetings coreboot community!
One of the items to come out of OSFC and the previous leadership meeting was the need to overhaul coreboot's website to look more "professional" -- like a project which was used by commercial entities large and small, not just something for hobbyists/tinkerers.
The leadership council has decided to move forward with this, and would like to hear from the coreboot community as part of developing requirements. These reqs roughly fall into 3 broad categories: logistical, aesthetic, and content. Some of the ideas been put out so far:
[logistical] * Everything must be owned and run by coreboot - not an outside developer. * Everything must be contained in a git repo (outside of downloadable files like releases). * As much as possible should be generated statically?
[aesthetic] * Use a site-wide top bar for navigation? (similar to https://www.zephyrproject.org https://www.zephyrproject.org)
[content] * Prominent display of companies using coreboot (similar to https://go.dev https://go.dev)
We'd love to hear from anyone else with ideas on how we can improve from the existing site.
regards, Matt
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
- could we just use gopher instead? http://gopher.floodgap.com/gopher/gw?a=gopher%3A%2F%2Fcoreboot.org- supports accessibility tools. I don't actually know what this entails though. - no cookies so we don't need an annoying permission pop-up. - no external artifacts that can enable tracking - fonts, scripts, etc. Everything should be hosted at coreboot. - no analytics - no movement that isn't initiated by the viewer. Menus expanding are okay, videos playing in the background are not. (Can you make a professional looking site without video backgrounds?) - no content management systems. - should integrate the coreboot documentation/doc site well. I'd like to eliminate as much duplication between the website and docs as we can. - let's raise some money with ads.
Martin Nov 2, 2023 at 08:28 by felix-coreboot@felixheld.de:
Hi Matt,
since the Zephyr page is more or less unusable without javascript enabled, I'd like to add a requirement that the new website should still be usable with js disabled. The Go language page is still functional without js. I'd say that it's fine if that page looks less nice without js, but it should still be usable without it.
Regards, Felix
On 30/10/2023 18:00, Matt DeVillier wrote:
Greetings coreboot community!
One of the items to come out of OSFC and the previous leadership meeting was the need to overhaul coreboot's website to look more "professional" -- like a project which was used by commercial entities large and small, not just something for hobbyists/tinkerers.
The leadership council has decided to move forward with this, and would like to hear from the coreboot community as part of developing requirements. These reqs roughly fall into 3 broad categories: logistical, aesthetic, and content. Some of the ideas been put out so far:
[logistical] * Everything must be owned and run by coreboot - not an outside developer. * Everything must be contained in a git repo (outside of downloadable files like releases). * As much as possible should be generated statically?
[aesthetic] * Use a site-wide top bar for navigation? (similar to https://www.zephyrproject.org https://www.zephyrproject.org)
[content] * Prominent display of companies using coreboot (similar to https://go.dev https://go.dev)
We'd love to hear from anyone else with ideas on how we can improve from the existing site.
regards, Matt
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
Hi all,
just a short comment:
I'm following the community since many years now, and I always thought that what's awesome about Coreboot is that it allows you to build / implement / install minimalistic firmware. That is, without gigantic animated GUIs and all that. Down to earth, get the job done, make the OS take over.
I tend to think that the website should reflect that as well: slim and efficient. So I think the current design is already better than the huge video of the mainboard equpping machine the site featured a while back.
But I totally acknowledge that I might be out of touch here. Modern (private and corporate) users might very well expect something looking as impressive as they're used to from other places.
P.
Am Montag, dem 30.10.2023 um 12:00 -0500 schrieb Matt DeVillier:
Greetings coreboot community!
One of the items to come out of OSFC and the previous leadership meeting was the need to overhaul coreboot's website to look more "professional" -- like a project which was used by commercial entities large and small, not just something for hobbyists/tinkerers.
The leadership council has decided to move forward with this, and would like to hear from the coreboot community as part of developing requirements. These reqs roughly fall into 3 broad categories: logistical, aesthetic, and content. Some of the ideas been put out so far:
[logistical] * Everything must be owned and run by coreboot - not an outside developer. * Everything must be contained in a git repo (outside of downloadable files like releases). * As much as possible should be generated statically?
[aesthetic] * Use a site-wide top bar for navigation? (similar to https://www.zephyrproject.org)
[content] * Prominent display of companies using coreboot (similar to https://go.dev)
We'd love to hear from anyone else with ideas on how we can improve from the existing site.
regards, Matt _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
Hi Philipp,
On 02.11.23 21:47, Philipp Stanner wrote:
I'm following the community since many years now, and I always thought that what's awesome about Coreboot is that it allows you to build / implement / install minimalistic firmware. That is, without gigantic animated GUIs and all that. Down to earth, get the job done, make the OS take over.
I tend to think that the website should reflect that as well: slim and efficient.
I very much agree with the reasoning. However, it's probably harder to define how to achieve that for a web page. How it is perceived may differ from person to person.
For instance, at a first look, I find the go.dev one tidier than our own. But looking at the layout and presented contents, it's not that. I think it's the unicolored spaces. But is that just me?
Nico
On 30.10.23 18:00, Matt DeVillier wrote:
[logistical]
- Everything must be owned and run by coreboot - not an outside developer.
agreed
- Everything must be contained in a git repo (outside of downloadable
files like releases).
likewise
- As much as possible should be generated statically?
I would even consider to continue the current practice to have as much as possible written in static pages, i.e. no dependency on an additional program to generate pages. It would also avoid the question which program to use :D I know HTML isn't the nicest language, but for smaller edits it shouldn't be a problem (e.g. adding to a list just needs copying boilerplate). And that we never had any bigger discussion about it that I could remember, I take as a sign that it can't be too bad.
[aesthetic]
- Use a site-wide top bar for navigation? (similar to
Yes please, it seems to be too common to ignore. The Zephyr one, however, is one of those that stick when you scroll down. I'm not sure if that is necessary. Personally, I can't remember that this ever felt useful.
I believe for mobile browsers it's common to turn the navigation into a menu.
[content]
- Prominent display of companies using coreboot (similar to https://go.dev)
agreed
Let's add another category:
[function]
* No JavaScript requirement as mentioned by Felix
And I'd like to add * Works 100% in mobile browsers
I wouldn't have thought it necessary to mention but quickly checked our current website. It has some issues in portrait mode.
Cheers, Nico
Hi,
for the statically generated part - I would really consider using a generator like 11ty to build the static website for you. I found it in the end easier to write some markdown files, rather than writing plain HTML. Even though I agree with not putting any JS into the homepage, or at least that it should be usable without JS, the homepage should somewhat be modern.
You can check out the OSFF Homepage: https://github.com/open-source-firmware/homepage - it's a bunch of markdown files, and 11ty builds a static site out of it - and even I can edit it ;)
Best,
Chris
On 11/3/23 13:41, Nico Huber wrote:
On 30.10.23 18:00, Matt DeVillier wrote:
[logistical]
- Everything must be owned and run by coreboot - not an outside developer.
agreed
- Everything must be contained in a git repo (outside of downloadable
files like releases).
likewise
- As much as possible should be generated statically?
I would even consider to continue the current practice to have as much as possible written in static pages, i.e. no dependency on an additional program to generate pages. It would also avoid the question which program to use :D I know HTML isn't the nicest language, but for smaller edits it shouldn't be a problem (e.g. adding to a list just needs copying boilerplate). And that we never had any bigger discussion about it that I could remember, I take as a sign that it can't be too bad.
[aesthetic]
- Use a site-wide top bar for navigation? (similar to
Yes please, it seems to be too common to ignore. The Zephyr one, however, is one of those that stick when you scroll down. I'm not sure if that is necessary. Personally, I can't remember that this ever felt useful.
I believe for mobile browsers it's common to turn the navigation into a menu.
[content]
- Prominent display of companies using coreboot (similar tohttps://go.dev)
agreed
Let's add another category:
[function]
- No JavaScript requirement as mentioned by Felix
And I'd like to add
- Works 100% in mobile browsers
I wouldn't have thought it necessary to mention but quickly checked our current website. It has some issues in portrait mode.
Cheers, Nico
coreboot mailing list --coreboot@coreboot.org To unsubscribe send an email tocoreboot-leave@coreboot.org
-
Christian Walter -
Felix Held -
Martin Roth -
Matt DeVillier -
Nico Huber -
Philipp Stanner -
ron minnich -
Tom Hiller