I'm hoping that maybe using the :not() pseudo-class in conjunction with setting webhelp.topic.collapsible.elements.initial.state to collapsed might help make all the elements that don't have styling from the .my_collapsible class start in an expanded state. Am I fooling myself or is something like t...

Quick update, this CSS amateur made a little bit of progress. section.my_collapsible > h3 > .wh_expand_btn { display: block !important; padding-right: 0.7em !important; } This bit of CSS brings back the collapsible buttons for the elements I want, so that's a step in the right direction. Two puzzles...

Okay so I'm still struggling with this. Maybe if I write down what I'm trying to do it'll trigger an aha moment for me or for someone generous enough to nudge me toward aha... I want none of my WebHelp output topics (HTML) to have collapsible sections except for a few that get transformed from speci...

Thanks very much, chrispitude. These *.publication.toc.* parameters don't quite give me what I want, at least not how I've been trying to use them. I have a product called MyCoolProduct. It has documentation in the form of a User Guide and a Sysadmin Guide. The User Guide's TOC needs to look somethi...

The first thing I noticed is that when I set the webhelp.topic.collapsible.elements.initial.state parameter to collapsed, almost every section on every output topic page starts in a collapsed state (only headings are displayed). The sections that I want to be collapsible/expandable (starting in a co...

Thanks very much, Radu. It's a good suggestion to go see what people over on the DITA users group might think.

Are they competing architectures? Would someone using DITA be well advised to not add an extra layer of IA complexity by trying to also incorporate iiRDS? Thanks for any insights.

Hi, I searched for this in the forums but couldn't find anything. The ditamap for my WebHelp Responsive transformation references ditamaps from several different but related guides. To keep things simple, I'll call them the User Guide and the Sysadmin Guide. I have the WebHelp output's main page and...

Is there a solution for this? I also would like the Publication TOC and Topic TOC to remain "sticky" on all topic pages (i.e. not scroll at all).

Thanks very much, InspectorSpacetime. I'll try your suggestion, which seems like it will help preserve the responsive aspect of the output.

While I'm hoping that there's a setting or transformation parameter that can help with this, I did manage to get what I want using a CSS hack. Someone please correct me if I did this wrong, but I decreased the width value for both the #content id and .wh_tiles class, as follows: #content, .wh_tiles ...

Thanks very much, InspectorSpacetime. Your suggestion is certainly better than my ongoing cluelessness, so I'll give it a try and report back here.

Hi, My documentation set has four tiles on the main page. Right now the way they render in the output displays three of the tiles on one row and the fourth on a row beneath. I'd like to even up their distribution. Is it possible to configure tiles so there are two on each of two rows? Some kind of t...

+1 to the votes for this integration.

Thanks very much, chrispitude. I'll try the OT plugin that you were generous enough to share. In the meantime and as a stop-gap (and for the possible benefit of those who read this thread in the future), I was able to suppress tiles that I didn't want to show up on the main page by way of a topicmet...

Hi. I searched the forum unsuccessfully, so I'll try to simplify what I'm working with here... For my product documentation, I have a top-level map that references two separate guides: <map> <mapref href="user_guide/user_guide.ditamap" format="ditamap"/> <mapref href="sysadm...

Quick update, I tried setting the webhelp.topic.collapsible.elements.initial.state parameter of my custom transformation to collapsed, but that made everything throughout the document start in a collapsed state (and since I used custom CSS to hide collapse/expand buttons the only way to expand colla...

I'm grateful, InspectorSpacetime. Your suggestion works well for me.

Does anyone know if it's possible to have these collapsible sections of mine default to collapsed instead of expanded? Thanks much.

I'm grateful, chrispitude. I'm also a bit clueless. I was able to get collapsibles to reappear for the section I want by adding this to my custom CSS file: div > section > h3 > .wh_expand_btn { display: inline; } Is there a better way to do that? This way worked for the section I want but also enabl...

Works like a charm, thanks very much! I ended up suppressing the display of all elements that use the wh_expand_btn class. While I was at it, I hid the permalink icon by way of the opacity setting: .permalink { opacity: 0; } Now I just need to figure out how to use collapsibles for the one or two se...

Thanks very much, chrispitude and InspectorSpacetime. I'm going to try your suggestions, and then report back here to help others learn what's possible. And sorry, maglid, for hijacking this thread. Hopefully you've either figured out the CSS hack already or will be interested in trying these latest...

Thanks very much, Costin, for the update.

Yes, thanks Radu. I will try to do just that.

Is there any progress on this? I find WebHelp Responsive to be unusable with so many elements of the output being collapsible.

Hi Radu, thanks for the reply. Here's my story, probably rather typical.

I want some of my coworkers to use Oxygen-based forms for creating their content in a standardized way. They balk at DITA or XML in general, insist upon using Markdown.

I guess I'll have to try another approach. Thanks.

Hi,

Is there a way to use Oxygen's form controls with Markdown content?

Thanks.

Hi all, Thanks to Julien's help, I managed to get all those redundant glossary definitions to coalesce onto one single page. There is still a duplicate glossary in my output (PDF - HTML5/CSS), but at least it now takes up only one extra page. The relevant part of my root <map> now looks something li...

Hi all, Thanks to Costin's help, I managed to remove underlining from links to topics and from links to external URLs. I'm still seeing the underline style applied to links from the <term> elements that I added for glossary references (I'm publishing to PDF - HTML5/CSS) As it stands, this is the rel...

Hi Julien,

Wow, that's great to know. Thanks very much for this information.

I'll try those suggestions, including the CSS debugging tip, and post back here if I have any further problems.

Thanks,

doctissimus

Hi Costin,

Thanks very much for the valuable information, I appreciate your time. I'll add that text decoration to a custom CSS file, as suggested.


doctissimus