# 🌅 Introducing Horizon, our newest theme

**URL:** <https://meta.discourse.org/t/introducing-horizon-our-newest-theme/369608>\
**Category:** Announcements\
**Tags:** horizon-theme\
**Created:** [July 1, 2025, 12:32pm UTC](https://meta.discourse.org/t/introducing-horizon-our-newest-theme/369608 "2025-07-01T12:32:45Z")\
**Posts on this page:** 1\
**Showing post:** 34

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [July 7, 2025, 7:25am UTC](https://meta.discourse.org/t/introducing-horizon-our-newest-theme/369608/34 "2025-07-07T07:25:50Z")

</div>

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

> **[Optimal Line Length for Readability: The Complete Guide (2026)](https://www.uxpin.com/studio/blog/optimal-line-length-for-readability/)**
>
> Learn how optimal line length enhances readability, eye movement, and accessibility in digital design, with practical tips for implementation.

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

---

_[View the full topic](https://meta.discourse.org/t/introducing-horizon-our-newest-theme/369608)._