davsclaus commented on code in PR #1761:
URL: https://github.com/apache/camel-website/pull/1761#discussion_r4027038622
##########
content/blog/2026/09/new-website-design/index.md:
##########
@@ -0,0 +1,39 @@
+---
+title: "A New Look for the Camel Website"
+date: 2026-09-16
+draft: false
+authors: [ammachado]
+categories: ["Website"]
+keywords: ["apache camel", "website", "redesign", "design"]
+preview: "The Camel website has a new look: self-hosted Archivo and JetBrains
Mono fonts, a new color palette, and reworked home, blog, download, docs, and
trust pages."
+---
+
+The Camel website has a new look. Over the last few weeks we rebuilt the
design foundation and reworked most of the pages on top of it: the home page,
header and footer, blog, downloads, docs listing, community, security
advisories, and the trust page.
+
+## Type and color
+
+The text now renders using the Archivo typeface for headings and body copy,
and JetBrains Mono for code, both self-hosted instead of pulled from a font
CDN. The color palette was rebuilt from the ground up at the CSS variable
level, so the change reaches every page rather than a handful of components
someone remembered to update.
Review Comment:
Body copy is still Open Sans: `antora-ui-camel/src/css/vars.css` keeps
`--body-font-family: 'Open Sans', system-ui, sans-serif` and adds
`--display-font-family: 'Archivo', sans-serif`, which `base.css` applies to
`h1`–`h6` only. The previous fonts (Open Sans, Droid Sans Mono) were also
self-hosted (`typeface-open-sans.css` with local woff2 files), so the "instead
of pulled from a font CDN" contrast isn't right either. What changed is the
choice of fonts: Archivo for headings and JetBrains Mono for code, replacing
Droid Sans Mono.
```suggestion
Headings now render in the Archivo typeface and code in JetBrains Mono,
replacing Droid Sans Mono; body copy stays in Open Sans. Both new families are
self-hosted, like the fonts before them. The color palette was rebuilt from the
ground up at the CSS variable level, so the change reaches every page rather
than a handful of components someone remembered to update.
```
##########
content/blog/2026/09/new-website-design/index.md:
##########
@@ -0,0 +1,39 @@
+---
+title: "A New Look for the Camel Website"
+date: 2026-09-16
+draft: false
+authors: [ammachado]
+categories: ["Website"]
+keywords: ["apache camel", "website", "redesign", "design"]
+preview: "The Camel website has a new look: self-hosted Archivo and JetBrains
Mono fonts, a new color palette, and reworked home, blog, download, docs, and
trust pages."
+---
+
+The Camel website has a new look. Over the last few weeks we rebuilt the
design foundation and reworked most of the pages on top of it: the home page,
header and footer, blog, downloads, docs listing, community, security
advisories, and the trust page.
+
+## Type and color
+
+The text now renders using the Archivo typeface for headings and body copy,
and JetBrains Mono for code, both self-hosted instead of pulled from a font
CDN. The color palette was rebuilt from the ground up at the CSS variable
level, so the change reaches every page rather than a handful of components
someone remembered to update.
+
+Our marketing pages (home, downloads, community) now sit in a 1200px
container. Docs pages kept their wider 1366px container, since a documentation
article needs the room a landing page doesn't.
Review Comment:
This describes the first spec commit in #1740 rather than what shipped. The
squash later replaced the fixed caps ("Replace fixed max-width caps with
clamp(…, 85vw, 1800px) so the doc grid, static pages, and community layout
scale with viewport"). Final code in `antora-ui-camel/src/css/vars.css`:
`--static-max-width--desktop: clamp(1200px, 85vw, 1800px)` and
`--doc-max-width--desktop: none`; before the redesign both were fixed at
1366px. So pages went from a fixed 1366px to scaling with the viewport, and
docs lost their cap.
```suggestion
Pages no longer sit in a fixed 1366px box. Marketing pages (home, downloads,
community) scale with the viewport between 1200px and 1800px, and docs pages
have no cap at all, since a documentation article with a sidebar and a table of
contents needs the room a landing page doesn't.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
