Skip to content

Refresh based on os-component-website template - #31

Draft
jamiethecat wants to merge 22 commits into
WebKitGTK:masterfrom
jamiethecat:main
Draft

Refresh based on os-component-website template#31
jamiethecat wants to merge 22 commits into
WebKitGTK:masterfrom
jamiethecat:main

Conversation

@jamiethecat

Copy link
Copy Markdown

No description provided.

jamiethecat and others added 16 commits November 11, 2024 19:56
- 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
@aperezdc

Copy link
Copy Markdown
Contributor

@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.

@jimmac

jimmac commented Jun 18, 2026

Copy link
Copy Markdown

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/

jimmac added 3 commits June 18, 2026 18:11
- 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
@mcatanzaro

Copy link
Copy Markdown
Contributor

It looks excellent.

I think a rebased pull request might help speed this along.

@jamiethecat

Copy link
Copy Markdown
Author

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.

@mcatanzaro

Copy link
Copy Markdown
Contributor

I just spent an hour rebasing this. Was not fun. Code is here. We should land this ASAP because every news post we publish between now and then needs to be modified to work with Zola rather than Jekyll.

Unfortunately my rebase is broken:

$ zola serve
Building site...
ERROR Failed to serve the site
ERROR error: Found string but expected identifier.
 --> partials/footer.html:6:38
  |
6 |         {% if link.url is containing("http") %}
  |                                      ^^^^^^

@jimmac I don't want to think about this. Any ideas?

To-do:

  • Michael should ensure all scripts (e.g. wsa and webkit-release) are modified for Zola if not already (should be easy)
  • Michael to review other changes to webkitgtk.org in past two years to make sure we haven't lost any changes
  • @aperezdc should ensure the actual webkitgtk.org has zola installed (hopefully easy, since there is a Debian package?)

Minor downside: we'll have to modify the header of the security advisories before copying them to wpewebkit.org. Not a big deal.

@mcatanzaro

Copy link
Copy Markdown
Contributor

Um, I also suggest we modify the new WebKitGTK logo to remove the Safari compass. I suspect Apple will likely not appreciate that.

@mcatanzaro

Copy link
Copy Markdown
Contributor

Maybe we could steal design concept from the Epiphany logo instead? Or... tbh, basically anything other than the compass metaphor?

Or maybe it's fine. We could simply ask Apple and see whether they're OK with it, and not worry about it unless they complain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants