🌅 מציגים את Horizon, הנושא החדש ביותר שלנו

[sam (Sam Saffron)]

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

Optimal Line Length for Readability

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

[Moin]

@lindsey

I’ll follow up soon!

Any update on this?

[tpetrov (Toni Petrov)]

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

[asa]

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.

[lindsey (Lindsey Fogle)]

@Moin

Any update on this?

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.

[Moin]

@lindsey

So we should be all set on that front.

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?

themes/horizon/settings.yml

[Moin]

@Moin

do you plan to remove them now that themeable site settings have been added?

DEV: Use themeable site settings for Horizon

Fortunately, I waited patiently for an update. I thought for a while about whether I should simply create a pull request to move the texts. That would obviously have been a waste of time

[Jagster (Jakke Lehtonen)]

Well, I don’t.

I disabled Horizon on my forum because there was way too often questions about how to start a topic. Mobile users use sidebar very rarely.

But that question is discussed and demand to do extra click to do one of basic functions in forums didn’t considered as an issue

[Jagster (Jakke Lehtonen)]

Well…

Help us test Horizon, our newest theme

DiscourseHub and mobile: [This image shows a screenshot of the Google Assistant interface and Windows settings on a smartphone with a 31% battery level. (Tekoälyn laatima kuvateksti)] Forcing to use the sidebar to start new topic wouldn’t be the smartest move, if the target is not the most skilful users (specially when a mobile is used)

(Someone asked recently in another topic that when users would use full quote. This could be one example, because I’ll flag these two latest posts to be moved to suggested topic, and then full quote would give some context)

[chapoi (Charlie)]

Mini update:

Based on some feedback we received (old & new), we decided to bring the Create topic button back on mobile.

You’ll find it back in its old spot. The new sidebar version will still remain too.