chore: update docs

README.md

@@ -177,8 +177,7 @@ to find out more about the core framework.
 
 On top of Vue we use [vue-router](http://router.vuejs.org/) for in-app routing,
 [Tailwind CSS](https://tailwindcss.com/) for custom component styling,
-and [Pinia](https://pinia.vuejs.org/) for state management (with the latter most likely
-being subject to change in the future).
+and [Pinia](https://pinia.vuejs.org/) for state management.
 
 We use [Vite](https://vitejs.dev/) as build system and dev server with little
 custom configuration (see `vite.config.js`).
@@ -188,13 +187,10 @@ custom configuration (see `vite.config.js`).
 If you’re in need for components or UX patterns that you’ve seen on other sites
 or seem generic to you, it’s always a good idea to look have a look at
 [VueUse](https://vueuse.org/) which comes with a lot of composables that are
-handy in everyday UI development. Unstyled components are available from
-[headless ui](https://headlessui.com/) if you need a specific UI component but need
-a custom design. For more generic ecosystem information you should visit
+handy in everyday UI development.
+For more generic ecosystem information you should visit
 [awesome-vue](https://github.com/vuejs/awesome-vue) and
-[awesome-vue-3](https://github.com/vuesomedev/awesome-vue-3). If you add any new
-dependencies make sure they don’t rely on any behaviours from Vue 2 as we are in
-the process of migrating to a Vue 3-only setup.
+[awesome-vue-3](https://github.com/vuesomedev/awesome-vue-3).
 
 Run `npm run format` to automatically format your code or run `npm run lint`
 to check it for errors. ESLint emits some warnings for existing code.