The Downloads page is very unclear, and offers CentOS Linux 7 as the first option.

Agreed. There is an ongoing effort to improve this situation using YAML to define the downloads data and HTML templates to present them. See some documentation and examples.

The Contribute link in the header points to the wiki. Move to www or docs.
The header links to Forums. We need to decide what to do with this long-term.
The header links to the wiki for Mailing Lists and IRC. Maybe put a single Contact page on www?

Similarly, here is also an effort to manage header links using YAML to define the navbar data and HTML templates to present it. See the following documentation links:

• The site navigation bar
• Changing the site navigation bar
• Adding links to site navigation bar
• Adding menus to site navigation bar

While working on the homepage redesign, I realized that I was not sure about the alignment between what I was trying to present and what others expect to have presented. In this respect, I would like to add, to the previous list, the following point:

• Create a collaborative document where we can coordinate the website content structure in hierarchy order. This document would be versioned and it would provide the reference necessary to implement the website components, like navbar. Also, to review the current dependency between pages.

What do you think about having a document with such definitions? Would it help us to be aligned in what we all want to present on the website?

I'd love to get the mission statement up on the site.

• Add a way to put a banner image near the top to promote Connect, major releases, or other big news.

The with_breakingnews configuration variable was added to jekyll-theme-centos and documented to promote Connect and other big news. Note that this component uses texts instead of images to provide more flexible way of presenting these messages. Producing different images for each message may take more time because we need to manage both image files and message configuration. With texts we only manage message configuration. Anyway, I am open to adjust. Here are a couple of screenshots:

with_breakingnews	with_announcements

Ideas about content localization:

• https://gitlab.com/CentOS/artwork/centos-web/pipelines/-/issues/1

@areguera What's your timeline on the new theme stuff? We should really get some changes in by the end of the month when CL7 goes EOL. In particular, we should stop highlighting it in the top fold of the index page. It would be awesome if visual updates could accompany that.

I've been taking notes and sketching some layout stuff on hackmd: https://hackmd.io/qOsVnJRjT4KBaFnalmnitw

I'd love an about/support page that says there is no official support. Perhaps text cribbed from Fedora?

@shaunm Thanks for your sketches and notes, they are very valuable. I am taking them as reference to initiate the website implementation right away based on the current theme implementation. A first version for review should be visible on www.stg.centos.org during the next week.

Preparing changes for staging in the following location:

https://git.centos.org/fork/areguera/centos/centos.org/tree/next

There are some structural changes related to how we organize files and build the site. Don't know if you agree with me here, but the current process to get started involves too many steps. I am wondering what you think about using a pre-baked container image that holds all the theme files and dependencies necessary to build the site? I've updated the README file and added a Makefile with some examples you can try yourself.

I am still accommodating things, here is a first website view built locally:

Theme documentation was also updated in case anyone wants to know how the theme works. There are some features not present in the past like category index that may be worth to consider during the content accommodation process.

Another homepage preview, locally built, with components a bit more aligned:

I've recently updated the staging branch using the gem model instead of the container image model proposed earlier in the next branch. The command we were using to render www.stg.c.o might be failing because of the Gemfile changes. In case it helps, the following command should build the site:

bundler exec jekyll serve

The package version I am using is: rubygem-bundler-2.5.9-9.fc40.noarch.

Though it is not strictly related to www.c.o, I would like share with you a PR to update the blog theme using the same visual presentation proposed in www.stg.c.o. Both blog.stg.c.o and www.stg.c.o should look visually aligned once published.

The website redesign should be driven by a well defined information architecture. I am not sure such thing is available somewhere. So, here is one based on my interpretation of @bex public talks and CentOS board meetings. Does it match reality? Would you change something?

Update previous image to add relationship between RedHat and CentOS Board: