-
Sub-task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
None
Generated screenshots must end up in the generated documentation. Ideally, a documentation writer does not have to leave the documentation repository at all. That would imply:
- that the screenshot description (desired application state + screenshot dimensions) is part of the documentation repo (maybe even the .md file?)
- that the generation script has to parse the documentation files to find screenshots that should be generated (or it is called by hugo?)
- that the generated screenshots end up in the compiled documentation pages
This is the controller panel for Smart Panels app
[OPT-2798] Integration Screenshot generation - documentation
Done as part of OPT-2397. We will have a separate script that generates the screenshots with yarn run screenshots
Current idea: Check out the documentation repo parallel to the optimize repo and let the generation replace the images in the documentation repo. This way you could also have non-generated screenshots.