šŸŒ… Introducing Horizon, our newest theme

For those with concerns around space, I think it is important to split the conversation into two parts.

WCAG recommends keeping lines at 80 characters or below for non-CJK text. Our designs try to take this into account; Horizon is currently at ~76.

So, there are two conversations here:

  1. I disagree with WCAG and usability experts; I just want lines to be as long as I want and don’t want anyone enforcing the 80-character limit.

  2. I am fine with WCAG – I just think that there is an alternative alignment trick that can be used to make things look better.

For people in (2), can you share a screenshot or two demonstrating a better layout for ultra-wide screens?

For people in (1), I think the approach here is ā€œcustom componentā€.

9 Likes

Any update on this?

The theme looks great!
But why it doesn’t work with the Expanded AI summaries here on Meta?

1 Like

Es geht ja eher darum das man bei einen Widescreen einen riesen weissen Fleck hat, ich habe ein paar User die auch einen Widescreen haben mit Ƥhnlichen Feedback das es eher stƶrt als hilfreich ist. Ich kann ja nicht sagen ā€œja das ist die WCAG Richtlineā€ oder ā€œKauf doch einen ā€œnormalenā€ Bildschirm.

Ich denke der Vorschlag von @SubStrider in Help us test Horizon, our newest theme - #70 by SubStrider ist sehr hilfreich.

Oder eventuell kann man die Navigation mittig stellen.

We haven’t gotten to this yet, but it is on our list to take care of.

Actually, one of my colleagues just took a look and confirmed that the only additional string added by Horizon (the theme description) is available in Crowdin already. So we should be all set on that front.

1 Like

i thought the theme also has 2 settings whose descriptions should be translated. Should they remain in English, should I add them to that file, should they be moved to the en.yml file so that they can be easily translated in Crowdin or do you plan to remove them now that themeable site settings have been added?