laminas
[RFC]: New design and layout 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
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?
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/
Might be worth adding input field to filter column contents. eg type "router" to show only router packages.
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 https://github.com/laminas/getlaminas.org/pull/226
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.
@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 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
@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?
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.
@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 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 .
Hey everyone, the new design looks good, cleaner and more focused. One thing I'm missing is the Tutorials area, which definitely need not only a new design, but a complete redevelopment. The focus of the tutorial is the MVC using Skeleton, and the "Components Tutorials" using laminas-db which is in maintenance mode since 2022.
I'm back to PHP and Open Source after 11 years abducted by corporate, and Laminas' website is not helping to understand who we are, what we do, and how to get started. The focus on Mezzio is pretty confusing, the multi-repo strategy is time- and energy-consuming, and the tutorials are not only not helping, they are making a chaos to get started.
I would be happy to contribute with a tutorial "Getting Started", but honestly I can't find my way through.
- What do I need to run Laminas Components?
- Is Mezzio the way forward? What's up with the book promotion having more impact than Laminas Components docs?
- Can this new website have a filter to the package's status (discontinued, active, maintenance, security)?
- What's the alternative to
laminas-db? Its repository has no label about the maintenance mode.
Let me know if I can be of any help here, I'd be happy to do so. The "getting started" would be a great way to get started contributing. 😜
Cheers, Henrique
@henriquemattos The current design and layout changes already deal with the first step of the user guidance topic: it removes MVC from the homepage. As we have to completely rework the Mezzio quick start and the documentation overview, I do not see any capacity to rework the "Getting Started" tutorial.
- What do I need to run Laminas Components?
Composer, as described on the installation pages. (Example)
- Is Mezzio the way forward? What's up with the book promotion having more impact than Laminas Components docs?
Correct, Mezzio is the recommended way and how you should start today. The book is intended for Mezzio and represents an important starting point.
- Can this new website have a filter to the package's status (discontinued, active, maintenance, security)?
I think you mean the "Maintenance Overview" and so yes, it is a good idea to add a filter. Please open a new feature request on this repository for this. Thanks! 👍🏻
- What's the alternative to laminas-db? Its repository has no label about the maintenance mode.
There are many good alternatives:
- Doctrine - Database Abstraction Layer
- Doctrine - Object Relational Mapper
- Cycle ORM
- CakePHP - Database Access & ORM
- Nette Datebase
Or this fork: https://github.com/axleus/laminas-db
The pull request for the label on laminas-db was unfortunately overlooked.