Disable list continuation (attributes, conditional processing, and more?) about asciidoc-googledocs-addon

[ggrossetie]

I am trying to set up a workflow where product managers iterate on a release notes draft on Google Docs.

👍

To this effect, I place attributes and conditional directives in the Gdoc but, unless I messed up with Docs formatting, the + sign is added to the end of lines with attributes and if macros.

I'm not sure if we should support it or not.
The idea is really to convert an Google Document written using the formatting tools. AsciiDoc attributes and conditional directives are part of the AsciiDoc syntax and, in my opinion, should not be written in a Google Document.

The workflow should be:

• Product managers iterate/collaborate on Google Document
• Convert the Google Document to AsciiDoc
• Add the AsciiDoc attributes and conditional directives
• Publish to Antora

[fviolette]

The idea is really to convert an Google Document written using the formatting tools. AsciiDoc attributes and conditional directives are part of the AsciiDoc syntax and, in my opinion, should not be written in a Google Document.

Because of the above, I did not think this would work. Now that it almost works (because AsciiDoc is just plain text), I take a chance. It's a little bit much to ask vs. the current features and intent, yes.

I may post the logic I end up going for here for reference purpose.

[ggrossetie]

I think still the list continuation is used too aggressively so we might find a solution but I don't want to introduce too much logic to "understand" plain-text AsciiDoc syntax in a Google Document because I think it's conter-intuitive.
But I'm willing to make some adjustments if it can improve a common workflow.

[fviolette]

Right! If other community members are interested by this use case or just modifying the list continuation behaviour, please chime in.

I see that I can store the metas in yaml, iterate via gulp and inject them in my files before publishing, so I'll dig this path separately.