Community
Participate
Working Groups
The refactoring and strategies are still being reviewed and therefore there is not a clear plan for this change yet. This bug is a way to open the discussion about the necessary/future changes to improve the user experience.
To my mind, user and developer doc should be located as closed as possible to the code: so inside the plugin they are dealing with. Then we need a documentation agregator for mediawiki, html and pdf generation. We should use the maven/tycho mecanism to produce the documentation. They are several patches where we have linked the TOC and mediawiki generation to the build process. Moreover it could be good to generate a default user/developer web site for each release of the Papyrus. This is the case for all Papyrus Components. See [1,2,3] [1]: https://www.eclipse.org/papyrus/components/sysml/ [2]: https://www.eclipse.org/papyrus/components/designer/ [3]: https://www.eclipse.org/papyrus/components/components/ [4]: https://www.eclipse.org/papyrus/components/robotml/