I've created a publication with responsive HTML articles with the intention that they would work at smartphone sizes as well.
The DPS system navigation layout looks/works fine at Ipad size. At mobile (iPhone size), everything scales down nicely except the text.
Text size remains constant, but at smartphone size only a few characters fit on the card, which makes the title unreadable.
Is there any way to adjust text size (or any other navigation characteristics) based on device size?
Solved! Go to Solution.
We support having separate designs for phones and tablets. To do so you need to create your project with two top-level collections (it's a setting when you make your project). This enables you to build out dual sets of collections with different layouts and card templates so you can design for each class of device.
This is, unfortunately, rather cumbersome if you are using responsive HTML for your content. We're working on a different approach where you'll be able to specify two layouts for a collection: one to use when displayed on tablets, the other on phones. I don't believe that will get done before the end of the year howevere.
Neil
You are talking about the cards?
Views
Replies
Total Likes
At the time the only solution is to find a happy medium and set up cards that use type sizes that will display on both device classes.
Views
Replies
Total Likes
We support having separate designs for phones and tablets. To do so you need to create your project with two top-level collections (it's a setting when you make your project). This enables you to build out dual sets of collections with different layouts and card templates so you can design for each class of device.
This is, unfortunately, rather cumbersome if you are using responsive HTML for your content. We're working on a different approach where you'll be able to specify two layouts for a collection: one to use when displayed on tablets, the other on phones. I don't believe that will get done before the end of the year howevere.
Neil
Thanks! Good to know. I actually a found a pretty good alternate solution.
I created another responsive article - basically a table of contents - put that single page in a collection, and set it to browse page. That seems to do the job nicely.
Well played Gronckle.
Views
Replies
Total Likes
Note: I meant "set to content page", not browse page. Big difference there.
Views
Replies
Total Likes
I figured . Thanks for the update!
Views
Replies
Total Likes