fix(docs): update links after repo move

Signed-off-by: Raimund Schlüßler <[email protected]>

README.md

@@ -1,11 +1,11 @@
 # `@nextcloud/vite-config`
-[![npm last version](https://img.shields.io/npm/v/@nextcloud/vite-config.svg?style=flat-square)](https://www.npmjs.com/package/@nextcloud/vite-config) [![Project documentation](https://img.shields.io/badge/documentation-online-blue?style=flat-square)](https://nextcloud.github.io/nextcloud-vite-config/)
+[![npm last version](https://img.shields.io/npm/v/@nextcloud/vite-config.svg?style=flat-square)](https://www.npmjs.com/package/@nextcloud/vite-config) [![Project documentation](https://img.shields.io/badge/documentation-online-blue?style=flat-square)](https://nextcloud-libraries.github.io/nextcloud-vite-config/)
 
 Shared Vite ⚡ config for Nextcloud apps and libraries, which also can be easily extended.
 
 ## API reference
 
-The full API reference can be found on the [documentation](https://nextcloud.github.io/nextcloud-vite-config/).
+The full API reference can be found on the [documentation](https://nextcloud-libraries.github.io/nextcloud-vite-config/).
 
 ## How to use
 If your app uses an entry point for the main app and one for the settings page, then your default project tree will look like this:
@@ -87,4 +87,4 @@ For apps any styles can be injected in the JS by dynamically inject the styles i
 But this only works in DOM environments, so for libraries this might not work (e.g. while testing in the Node environment).
 
 So for apps the CSS will still be extracted by Vite, but the extracted CSS assets will be imported.
-This way the library user can decide how to handle the imported CSS without relying on a DOM environment.
+This way the library user can decide how to handle the imported CSS without relying on a DOM environment.