Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Fix CI build for release builds

See original GitHub issue

In the configuration.properties the otversion key has the value “2.3+69a962e”
<del>HTML5 contains sass folder</del>
ODT contains src, test and resources folders
RTF contains src folder
docsrc contains temp folder

Issue Analytics

State:
Created 7 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

eerohelecommented, Jun 1, 2016

I agree with @infotexture. I can certainly see myself wanting to extend the default DITA-OT SASS files.

1reaction

infotexturecommented, Jun 1, 2016

Since the sass folder only takes up a few kilobytes, I would be inclined to include them for the benefit of those who would like to extend the defaults with their own mixins, partials, etc.

That would allow web devs who are unfamiliar with DITA-OT to extend styling and simply regenerate the common CSS files using standard Sass practices, rather than requiring customization of the org.dita.html5 plug-in.

To better support that use case, we might decide to ship a Sass build file later and provide an additional args.sass parameter to hook into the CSS pre-processing rather than overriding styles in commonltr.css later with a custom CSS file specified via args.css — but that should be treated as a separate issue.