nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How can I use Confluence layouts in Scroll Viewport?

Craig Melcher

Scroll Viewport is stripping the 'layouts' (eg 2-column or 3-column blocks within a page) that I've added in Confluence.
Confluence:
Edit - Moving image - Shelter-s Digital Framework - Confluence 16-06-2021 08-31-15.png
Scroll Viewport:
Moving image 16-06-2021 08-31-59.png

Is it possible to enable this?
Thanks

Accepted answers

All comments

Matt Reiner _K15t_

Hi @Craig Melcher

I was wondering if you're using the Help Center theme in Scroll Viewport or if you're using the Web Help or a totally custom theme.

This will help me figure out what's happening here.

Craig Melcher

Hi @[deleted]

Yes, we're using the Help Center theme in SV. I'm just using the theme settings in the app, not using any customized CSS etc.

Thanks

Matt Reiner _K15t_

Ah, OK. 👍🏻

Unfortunately, we don’t support Confluence’s page layout option in Scroll Viewport and this limitation is by design: To guarantee a perfect presentation of your content we currently suppress multi column layouts.

Content on columns is instead displayed beneath each other (as you see in your example). We think that readability might suffer as the article template is already divided into two columns, the article navigation and the article content (and even three columns if the Table of contents option is enabled).

So we recommend laying out content so it’s optimized for the width of the article content column.

That’s not to say that we won’t offer multi-column layouts in the future, but we think it might require a rethinking of the current article template altogether (maybe a different article layout option in the theme editor).

Craig Melcher

Thanks @Matt Reiner _K15t_ Makes sense.

Craig

Ondřej Velíšek

Hi there,

From my point of view this is a big limitation. I understand it might be a low priority issue, but if it is design decision to not support layouts (sorry for my honesty) it is non-sense. Why to decide not support such a frequently used functionality?

Several use-cases from top of my head:

Two images beside each other with some explanation.
- Before scenario.
- After scenario.
Back and forth buttons in tutorials flow.
- One on the left side.
- One on the right side.
Set of quick links pointing outside documentation divided into three column sections. E.g.
- Use-cases: case 1, case 2, case 3
- Legal: Terms of use, Privacy notice, Cookies policy
- Community: Stack overflow, Blog, Github

Please reconsider the design decision and priority of the issue. Thank you for your work and kind regards.

Laura Parraga -K15t-

Hi Ondřej,

We've been working on support for Confluence layouts and will release the enhancement in the coming days. You can track the progress using https://k15t.jira.com/browse/VPC-315.