laminas
New design
| Q | A |
|---|---|
| New Feature | yes |
| RFC | yes |
Description
An initial version of the design proposed in #242, to maybe make it easier to visualize. The changes can (and will) be cleaned up and streamlined once a preferred layout/design is formed.
This initial version is better viewed on large screens - the design on mobile or small screens was not discussed so it's mostly the default behaviour and some changes I added where it was too weird.
Since the maintenance status of the API-Tools packages is still displayed, I haven't removed the link from the footer for now.
Preview here: https://preview-1-hy2vwsq-2ja7ciew2nbkm.us-2.platformsh.site/
Since the maintenance status of the API-Tools packages is still displayed, I haven't removed the link from the footer for now.
Please remove it.
@laminas/technical-steering-committee Let's see if we are close to push it live check preview here https://preview-1-hy2vwsq-2ja7ciew2nbkm.us-2.platformsh.site/
There's a slight style issue somewhere, as the horizontal scroll bar is appearing no matter what resolution I'm in. It only scrolls a few pixels, but something is amiss.
There still are tweaks to do, especially on the responsive design, but i've made the commit to get some more feedback - i'll take a look at this issue as well
I personally miss more space in and between the elements and the clippings of the screenshots no longer work because the idea was different: https://github.com/laminas/getlaminas.org/issues/162 Please also check the logos of Mezzio and Components, they have different sizes.
My original design proposal contains the same borders and border colours (top!) for the Mezzio and Components section as in the documentation. The section for the book was also coloured completely differently to create differentiation/separation.
Reference:
- https://docs.laminas.dev
- https://docs.mezzio.dev
There's probably a lot that can be refactored into a cleaner version as the overall design is agreed upon - i'll work on this as well while implementing the requested changes
Removed the background image (@froschdesign or did i misunderstand and you mean only removing that first instance of it?), added the spacing and some fixes for the failing responsive design
Let me know of any other changes while i go about and replace the custom styling with bootstrap where i can
I've added some minor markup tweaks…
Also, why have the link targets mostly been changed to
_blank- I personally know how to use my back button, or CMD + click for a new tab, and I find this kind of tab spawning a bit obnoxious.
The teory of SEO says that all external links to have _blank, to not loose the original page
The teory of SEO says that all external links to have
_blank, to not loose the original page
I don't agree - which SEO people say this?
This is a UX problem, not an SEO problem, and also one that can be addressed site-wide with a little JS if neccessary.
Not a hill I want to die on, but I hate spurious use of _blank on sites that I visit. IMO, the only thing it helps is an artificial idea of "Bounce Rate" which we really shouldn't care about.
fresh preview https://preview-1-hy2vwsq-2ja7ciew2nbkm.us-2.platformsh.site/
I do not understand the spacing, this needs to be properly aligned.
The extracts of the individual blog posts are cut off, although these are specially defined.
Why are the headlines in the text green, while they are blue on all other pages? It has to be uniform, please keep it blue.
I've got a number of suggestions, but would prefer to submit them via PRs or individual issues.
@settermjd I think, it would be good to collect all problems and suggestions in a new issue report. Sub-issues can be used for that.
In few hours some of the open issues will be fixed. So better open a separate issue
preview updated
https://preview-1-hy2vwsq-2ja7ciew2nbkm.us-2.platformsh.site/
@settermjd @froschdesign Please create sub-issues to this root issue
https://github.com/laminas/getlaminas.org/issues/242
Quick note about the individual blog post extracts: the proposed design uses fixed dimensions for the cards, so the existing extracts are cut off to accommodate that. I'm open to suggestion on how to handle this - scrolling, bigger boxes, a different layout altogether?
the proposed design uses fixed dimensions for the cards, so the existing extracts are cut off to accommodate that.
The layout is okay but the entire extracts must be visible without scrolling. Use grid cards and equal height and everything should work. Example: https://github.blog/latest/
I personally like the following layout: https://blog.vuejs.org
@froschdesign if going with the grid cards i'd say they look ok with smaller extracts, though where large extracts are concerned it starts to stretch the rows too much.
Unless i'm missing something, that would mean the <!--- EXTENDED --> tag should be moved in many of the blogs to accommodate - or go for a different layout altogether?
uploaded an initial version with the grid layout, but i had to move a few blogposts' extended tags further up to avoid the issue described earlier
the new preview https://preview-1-hy2vwsq-2ja7ciew2nbkm.us-2.platformsh.site/blog/
@froschdesign @settermjd
but i had to move a few blogposts'
extendedtags further up to avoid the issue described earlier
The content must follow the design when it should be the other way round.
Have you had a look at this layout: https://blog.vuejs.org
but i had to move a few blogposts'
extendedtags further up to avoid the issue described earlierThe content must follow the design when it should be the other way round.
Have you had a look at this layout: https://blog.vuejs.org
Yes. I considered the vuejs layout, List style. But i consider this one, grid style, is better.
In a future release, we can have both styles
But i consider this one, grid style, is better.
Why is this better when the content has to be changed for this layout?
But i consider this one, grid style, is better.
Why is this better when the content has to be changed for this layout?
More content on the first screen. No need to scroll too much
The whole thing is too inconsistent for me, so I am afraid to go online with it. We take great care with the individual components before anything is released. I miss that care here.
- Why are there different border radii? (homepage, support, commercial vendor program)
- Why the buttons under "Commercial Vendor Program" are red but in the support overview blue, although there are under the same section "Support"?
- The spacing is inconsistent all over the website. (homepage, blog, community, support, …)
- And the original drafts look much better than the current layout. (Example)
Some other problems:
- wrong layout in blog post
- remove MVC from the footer
- sort the entries in the footer by their importance and not by their length: Mezzio, Components, …
- The copyright is given more importance than the reference to the Linux Foundation, this should be changed.
- Add the link to the project discussions to the community page and not in the footer.
Overall, I would appreciate if we didn't make any major changes to the structure of the footer so that it continues to match the documentation. (Example)
I understand that a timely publication is necessary, but the quality should not suffer as a result. And if we have to publish first and then have to rework, then the process seems wrong to me.