Je me permets de vous contacter concernant l’export HTML généré par Capella/Arcadia.
Nous nous interrogeons sur la possibilité de moderniser le rendu visuel de cet export, afin d’obtenir une présentation plus actuelle.
Pouvez-vous me confirmer :
s’il existe des options natives de personnalisation de l’export HTML,
s’il est possible d’utiliser un add‑on (comme l’XHTML Documentation Generation),
ou si une modernisation du template nécessite une intervention spécifique (ex. développement ou configuration avancée) ?
Generally speaking, I believe it is better to post in English on the forum if you want to reach out to a larger crowd.
To answer your question, I don’t think there is an “easy/build-in” way to modernize the result of the HTML export.
I would recommend to contact Obeo. As part of their Publication for Capella commercial add-on, they provide a web publication mechanism, the result being accessible via an authentified conexion through a web browser, with a modern look, and other capabilities.
Hello Stephane,
As you know I am currently working on customizing the HTML export generated by the Capella XHTML DocGen add‑on.
My goal is to modernize the output by modifying the content.css file.
Issue encountered:
Even after modifying the content.css file inside the generated export, Capella never takes my changes into account during the next generation. I am forced to run a PowerShell script right after the HTML export generation so that my content.css modifications are applied.
My question:
I would like Capella to automatically use my customized CSS version, without any intermediate step (no post‑generation script, no manual copying).
What is the correct and supported method to modify the contents of the DocGen .jar files (or recompile the plug‑in) in order to permanently integrate my own content.css?
ok so I am probably not the right technical person to answer this, and I am going to give you a “quick and dirty” solution.
You may: change the name of the jar file to zip, open it, replace the css file in it, and change back the zip extension to jar.
Please note that this is not the “correct” way to modify the DocGen jar files. Indeed, the correct way would be to recompile it. What I am suggesting is more a hack. But this should work.
Please also note that this add-on is under the Eclipse Public License, so if you are modifying some code (css included) and then redistributing these changes outside of your organization, then the modified code should be made available to the public under the EPL. This is what the EPL is telling you to do.
Technical context