Hi,
The CentOS website redesign effort is going on and there is already some code to evaluate at:
https://github.com/areguera/centos-jekyll-sites/tree/staging
The redesign uses jekyll static site generator, Montserrat typography and the artistic motif we used in CentOS distributions, to highlight the visual connection among these elements. The navigation header and footer changed to use a dark blue background consistent with CentOS artistic motif. On header the logo and link elements were moved from left to center with respective spaces so the left side of the logo and the left side of the content look aligned on left. On footer, links to CentOS About and CentOS Community were displayed along The CentOS Project description.
The content is based on what we have now in www.centos.org. I tried to replicate it but there are content still missing (on purpose to see how the "404 Not found page" looks like ;). The written information may need some consistency. For example on page titles, sometimes we write "The CentOS ...", others just "CentOS ...", and others no "CentOS" word at all.
The download links are missing on purpose so to bring debate about the way to go here. In the proposed code, we use two cards, one for CentOS Linux and other for CentOS Stream. Each card has tabs inside to organize download information about major releases of each distribution. This organization uses a table to relate architectures, packages, release notes, documentation and end-of-life. These cards are reused both in the home page and the download page, so we only need to change them in a single place (e.g., https://github.com/areguera/centos-jekyll-sites/blob/staging/_includes/cento... ).
What's your impressions so far? You are welcome to share your comments, suggestions, and code/design contributions.
Thanks,
On 09/02/2020 15:56, Alain Reguera Delgado wrote:
Hi,
The CentOS website redesign effort is going on and there is already some code to evaluate at:
https://github.com/areguera/centos-jekyll-sites/tree/staging
The redesign uses jekyll static site generator, Montserrat typography and the artistic motif we used in CentOS distributions, to highlight the visual connection among these elements. The navigation header and footer changed to use a dark blue background consistent with CentOS artistic motif. On header the logo and link elements were moved from left to center with respective spaces so the left side of the logo and the left side of the content look aligned on left. On footer, links to CentOS About and CentOS Community were displayed along The CentOS Project description.
The content is based on what we have now in www.centos.org. I tried to replicate it but there are content still missing (on purpose to see how the "404 Not found page" looks like ;). The written information may need some consistency. For example on page titles, sometimes we write "The CentOS ...", others just "CentOS ...", and others no "CentOS" word at all.
The download links are missing on purpose so to bring debate about the way to go here. In the proposed code, we use two cards, one for CentOS Linux and other for CentOS Stream. Each card has tabs inside to organize download information about major releases of each distribution. This organization uses a table to relate architectures, packages, release notes, documentation and end-of-life. These cards are reused both in the home page and the download page, so we only need to change them in a single place (e.g., https://github.com/areguera/centos-jekyll-sites/blob/staging/_includes/cento... ).
What's your impressions so far? You are welcome to share your comments, suggestions, and code/design contributions.
Thanks,
Hi Alain,
Great work ! I've rebuilt locally proposed design through jekyll (with your instructions in README.md) and I really like it. Some remarks: - I see that you modified /download/mirrors to include the search bar that we discussed in the past, and I really like it. But if you compare with https://www.centos.org/download/mirrors/, you'll see that we decided some time ago to not show the ftp links anymore, and that also increase visibility/readability. Can that be easily modified on the new design ? - All the "social media links" in the footer aren't linked properly , but I guess it's "per design" at this stage - I read that you had some sections not yet ported to Jekyll, to be able to test the 404, but wondering if /sponsors can be worked on, and so curious about how it would look like when included :) (and same for /keys)
Thanks a lot for the refreshed design ! :-)
PS : Have we got news from CentOS board about the new logo/font that you use in this template ?
Hi Fabian,
On Mon, 2020-02-10 at 08:38 +0100, Fabian Arrotin wrote:
I've rebuilt locally proposed design through jekyll (with your instructions in README.md) and I really like it.
Terrific! :)
Some remarks:
- I see that you modified /download/mirrors to include the search bar
that we discussed in the past, and I really like it. But if you compare with https://www.centos.org/download/mirrors/, you'll see that we decided some time ago to not show the ftp links anymore, and that also increase visibility/readability. Can that be easily modified on the new design ?
Yes. That would be certainly an improvement to increase visibility.
- All the "social media links" in the footer aren't linked properly ,
but I guess it's "per design" at this stage
Yes. Something to correct too.
- I read that you had some sections not yet ported to Jekyll, to be
able to test the 404, but wondering if /sponsors can be worked on, and so curious about how it would look like when included :) (and same for /keys)
Yes. I am going to include /sponsors and /keys as well.
Expect these changes near the next Monday.
Thank you for taking the time and provide feedback.
Best regards,
On Mon, 2020-02-10 at 08:38 +0100, Fabian Arrotin wrote:
- I see that you modified /download/mirrors to include the search bar
that we discussed in the past, and I really like it. But if you compare with https://www.centos.org/download/mirrors/, you'll see that we decided some time ago to not show the ftp links anymore, and that also increase visibility/readability. Can that be easily modified on the new design ?
Done.
https://github.com/areguera/centos-jekyll-sites/commit/f819c0073b2701b2ce313...
- All the "social media links" in the footer aren't linked properly ,
but I guess it's "per design" at this stage
- I read that you had some sections not yet ported to Jekyll, to be
able to test the 404, but wondering if /sponsors can be worked on, and so curious about how it would look like when included :) (and same for /keys)
Done.
https://github.com/areguera/centos-jekyll-sites/commit/18e411b8f44711b39af94...
Best regards,
This is really great stuff and I look forward to working with Jekyll rather than what we have.
I wanted to bump the thread to check on status and timelines, as I'm working on a new section of the site (/stream) and don't want to have to do the work twice.
On Sun, Feb 9, 2020, 09:57 Alain Reguera Delgado alain.reguera@gmail.com wrote:
Hi,
The CentOS website redesign effort is going on and there is already some code to evaluate at:
https://github.com/areguera/centos-jekyll-sites/tree/staging
The redesign uses jekyll static site generator, Montserrat typography and the artistic motif we used in CentOS distributions, to highlight the visual connection among these elements. The navigation header and footer changed to use a dark blue background consistent with CentOS artistic motif. On header the logo and link elements were moved from left to center with respective spaces so the left side of the logo and the left side of the content look aligned on left. On footer, links to CentOS About and CentOS Community were displayed along The CentOS Project description.
The content is based on what we have now in www.centos.org. I tried to replicate it but there are content still missing (on purpose to see how the "404 Not found page" looks like ;). The written information may need some consistency. For example on page titles, sometimes we write "The CentOS ...", others just "CentOS ...", and others no "CentOS" word at all.
The download links are missing on purpose so to bring debate about the way to go here. In the proposed code, we use two cards, one for CentOS Linux and other for CentOS Stream. Each card has tabs inside to organize download information about major releases of each distribution. This organization uses a table to relate architectures, packages, release notes, documentation and end-of-life. These cards are reused both in the home page and the download page, so we only need to change them in a single place (e.g.,
https://github.com/areguera/centos-jekyll-sites/blob/staging/_includes/cento... ).
What's your impressions so far? You are welcome to share your comments, suggestions, and code/design contributions.
Thanks,
Alain Reguera Delgado alain.reguera@gmail.com _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Hi Rich,
On Thu, 2020-02-27 at 08:23 -0500, Rich Bowen wrote:
I wanted to bump the thread to check on status and timelines, as I'm working on a new section of the site (/stream) and don't want to have to do the work twice.
Presently, the source of true is www.centos.org. You would not duplicate work (I would do :) until the new site be approved. The new website redesign is in a request-for-comments stage. There is no timeline a.f.a.i.k but a well defined direction of taking what we have in www.centos.org and re-remodel it using Jekyll, implement a more plain design using Bootstrap 4 standards and see what comes up. All this with other CentOS websites in mind (eg., mailing lists, mirrors, etc.)
The website redesign can be tested locally in your workstation. Its code is in Github where pull requests can be considered to introduce changes collaboratively.
To open issues, send comments or any sort of feedback you could provide would be of great motivation to keep going.
Thanks,
On 2/27/20 9:40 AM, Alain Reguera Delgado wrote:
Hi Rich,
On Thu, 2020-02-27 at 08:23 -0500, Rich Bowen wrote:
I wanted to bump the thread to check on status and timelines, as I'm working on a new section of the site (/stream) and don't want to have to do the work twice.
Presently, the source of true is www.centos.org. You would not duplicate work (I would do :) until the new site be approved. The new website redesign is in a request-for-comments stage. There is no timeline a.f.a.i.k but a well defined direction of taking what we have in www.centos.org and re-remodel it using Jekyll, implement a more plain design using Bootstrap 4 standards and see what comes up. All this with other CentOS websites in mind (eg., mailing lists, mirrors, etc.)
Ok, then let me ask the question differently. Is there a chance that we can get this live by April 27th, for Red Hat Summit? What would need to happen for that to happen?
The website redesign can be tested locally in your workstation. Its code is in Github where pull requests can be considered to introduce changes collaboratively.
To open issues, send comments or any sort of feedback you could provide would be of great motivation to keep going.
Thanks,
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Thu, 2020-02-27 at 10:44 -0500, Rich Bowen wrote:
Ok, then let me ask the question differently. Is there a chance that we can get this live by April 27th, for Red Hat Summit? What would need to happen for that to happen?
In the client side:
- The downloads links are a major work still missing. I need help to define this considering the matrix presented in the new design.
- The content it self needs some re-check for consistency and redaction improvements. On titles mainly.
- Do some QA in the code, clean it.
In the server side:
- We need to stage the site in a production-like environment and test using podman or something else to run it. Here we need to consider what git repo the site will be hosted in and implement the update flow to be sure it works on production.
This is what comes on top of my mind. We could reach a basic level of acceptability before April 27th, then iterate through small fixes to introduce improvements, once published, as needed.
-
Alain Reguera Delgado -
Fabian Arrotin -
Rich Bowen