Long text in the vote cards isn't truncating correctly and will push the controls below it out of bounds.

Add invert option to LayoutColumns, we will need this to reverse the column order for the staking view.

Calls to connects describeScript are slow, we should avoid delaying UI rendering and instead progressively load the descriptions separately inside of our cards and proposal detail page.

Now that we have access to LayoutProvider via aragon/ui 1.7.0 we can set this globally and create our own container/s, this will let us utilise useLayout anywhere without limitations. e.g: In a fullwidth responsive header navigation.

As our pages get longer, this issue becomes more obvious. In the future perhaps some sort of position persistence might be useful, but for MVP lets hop to the top!

They give a 404 if you refresh on a route.

Currently we're doing too much upfront work, that was fine for quickly getting set-up but it's not scalable. There also seems to be quite a bit of added latency with describeScript which needs investigating. At this point I think it's worth switching to lazy loading per route and component.

Small annoyance; usually these headers are clickable :). Not entirely sure where it would lead to you, but probably the proposals route?

I think it would also be ideal if the text was unselectable (this probably applies across the entire navbar and some other headers / etc in the app?)

Very low priority but we should focus trap inside open modals for better accessibility.

The existing <Split/> component provided by the UI kit has a very narrow secondary column, this works against us at the moment as our designs require more space. It should also let us sidestep this issue on the Proposal detail view.

The agreement's text is currently cut-off at the bottom without any effect. On some screen sizes / scroll positions, users could think that what they see is all of the text, rather than just a portion.

AppBadge on vote cards is focusable, it shouldn't be.