🚧 [docs] Move of documentation to vitepress #2951
Conversation
N0W0RK
force-pushed
the
rewrite/docs
branch
2 times, most recently
from
7d68f17 to
ab43840
Compare
|
Maybe a good point to mention #2933 😁 |
|
Not sure if #2933 fits in the scope of this PR. That should maybe be its own pr |
New documentation resides in . After full transfer, new documentation will be placed in and buildscripts will be adapted.
|
Just FYI vitepress and yarn workspaces do not like each other. If anyone here has an idea on how to get the build script working, feel free to message me. |
Rewrite rules compile the Markdown files into the correct directory structure while leaving them next to the source. Is vitepress syntax and has to be sourrounded by a span. ESLint rules are modifed accordingly. Asset links are cleaned up and somewhat unified. WIP Dynamic links to Issue LSS-Manager#15 and FontAwesome are made static.
Cr4zyc4k3
added
documentation
|
@Cr4zyc4k3 Is there a reason, why the modules |
|
Since the template module is only a template without any real use case I assume nobody noted that until now. The statusCounter module has a register.json. So I assume we can change the |
|
|
|
Yes, it came up, because I havent explicitly excluded it yet. However I still think it would be a good Idea to move everything to JSON. This way everything is unified and the template module can be copied, modified and work just like any other module without any special provisions. |
What kind of update does this PR provide? Please check
What is included in your update?
Additional notes
Still WIP
Vuepress is EOL and will be replaced by Vitepress. Therefore the switch is reasonable and considering the maintainability of the project necessary.
Closes #2884
TODO: