Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFC]: New design and layout 2025 #242

Open
arhimede opened this issue Feb 3, 2025 · 13 comments
Open

[RFC]: New design and layout 2025 #242

arhimede opened this issue Feb 3, 2025 · 13 comments
Labels

Comments

@arhimede
Copy link
Member

arhimede commented Feb 3, 2025

RFC

Goal

Continuation of the past year RFC related to design and layout, as stated in this RFC 162
Also including the layout of Laminas Ecosystem (temporary name).
It is only a new proposed design , a bit different colors , font, header and footer.
RIght now is missing the proposed design for Sponsors-Vendors-Become A Sponsor section on index page .

Preview

Image

Image

Image

Image

Image

Image

@arhimede arhimede added the RFC label Feb 3, 2025
@settermjd
Copy link

On the package maintenance status page, instead of an endless list, how about some form of scrolling within the four major blocks so that they have a fixed length?

@arhimede
Copy link
Member Author

arhimede commented Feb 3, 2025

On the package maintenance status page, instead of an endless list, how about some form of scrolling within the four major blocks so that they have a fixed length?

In my opinion , this page is supposed to be used with "ctrl-F" and find quickly in page the status of a certain package
Is not supposed to be read or scrolled .
The page is already live for few months now: https://getlaminas.org/packages-maintenance-status/

@Xerkus
Copy link
Member

Xerkus commented Feb 3, 2025

Might be worth adding input field to filter column contents. eg type "router" to show only router packages.

@arhimede
Copy link
Member Author

arhimede commented Feb 3, 2025

Might be worth adding input field to filter column contents. eg type "router" to show only router packages.

There is a separate PR about that "ecosystem" page
#226

@froschdesign
Copy link
Member

Here is a short list of what I have noticed:

  • remove the references on "Blackpoints AG"
  • remove the API tools from the footer
  • sort the entries in the footer by their importance and not by their length: Mezzio, Components, …
  • Where does the star in the background come from? We don't have it anywhere, so why introduce such a boring element? Can we find something better?
  • There are buttons for "Back" and "Next", why not for "Back to blog posts"?
  • Different fonts are used in the footer, but I think that is only due to the draft. Right?
  • The copyright is given more importance than the reference to the Linux Foundation, this should be changed.

@arhimede
Copy link
Member Author

arhimede commented Feb 4, 2025

@froschdesign yes, is only a draft
when we will implement it, we will fix all those content related issues
you are right about the star, we will find something else .
Thanks for feedback 👍🏻

@arhimede
Copy link
Member Author

arhimede commented Feb 7, 2025

Updated design

Homepage , with stripes in background

Image

@froschdesign
Copy link
Member

@arhimede
Is a dark mode planned?

@arhimede
Copy link
Member Author

@arhimede Is a dark mode planned?

Not at this stage.
But if you think that would be usefull, you can the draft item from Redesign project as issue

@froschdesign
Copy link
Member

@arhimede
It was pure interest. For the documentation, I will implement it via Bootstrap.

Another question: The cards on the Commercial Vendor Programme page have shadows, but these shadows are not found anywhere else. This is inconsistent. What is the plan here?

@arhimede
Copy link
Member Author

Another question: The cards on the Commercial Vendor Programme page have shadows, but these shadows are not found anywhere else. This is inconsistent. What is the plan here?

Yes, i noticed that those cards does not fit in the general design layout, but will be redesigned at implementation time.
I am expecting during implementation to see various problems.

@froschdesign
Copy link
Member

@arhimede
Can we get a detailed overview of what the implementation of the redesign includes?
For example, will the build process (JS/CSS) be reworked, which libraries will be used or replaced, or will the redesign be done page by page?

@arhimede
Copy link
Member Author

@arhimede Can we get a detailed overview of what the implementation of the redesign includes? For example, will the build process (JS/CSS) be reworked, which libraries will be used or replaced, or will the redesign be done page by page?

The redesign is planned to be done page by page.
Build process will stay the same, no libraries are planned to be added, maybe will be removed some if is the case .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants