Refresh based on os-component-website template#31
Conversation
- in pixels!
- forgot to add image assets
- better relation between gtk and webkit <> apps
- left some garbage in.
- All the images ave 10x oversampled and look better scaled filtered. Not a universally better approach, but it is here.
- going with filtered images, the 404 needs to be larger
WebKitGTK rather than WebkitGtk
|
@jamiethecat Hi, and sorry for taking so long in replying here. This is IMO definitely an improvement over the current design (which has served us well, but is quite dated), thanks a ton for proposing it 🫶 I have pushed a rebased and slightly updated version of this to the aperezdc/new-design branch, and I think it's ready to merge. I'm currently double-checking with other maintainers to make sure we all agree on going ahead. If yes, I will take care of merging things manually, and making sure that the cron job that handles website updates has its environment updated and that Jekyll works there correctly. |
|
A lot has changed since this PR was made. jekyll isn't a preprocessor I'd recommend using in 2026. The amount of overhead dealing with gem dependencies is just not worth it, especially for a site that really only uses it to have a markdown processor. I've since moved the template the redesign is based on to Zola. I took some time to port this site to zola -- https://github.com/jimmac/WebKitGTK.org/tree/wip/jimmac/zola Preview here -- https://jimmac.github.io/WebKitGTK.org/ |
- show it works, regardless of how it's gonna be deployed
- make footer look good for mobile layout
- keep .container and footer bottomlink in sync for both mobile and desktop layouts
|
It looks excellent. I think a rebased pull request might help speed this along. |
|
It has been 2 years since I opened this MR, so I'm not familiar enough with the codebase anymore to quickly rebase it. I recommend either @jimmac (who also has collaborator permissions to my branch) or someone else to do it. |
4 participants
No description provided.