Should I include a logo and/or favicon?

I think we could use either the default Postgres Logo, or a modified version of it if you can provide such.

Are we using the default colors from VitePress for backgrounds and brand color, or do we have specific ones?

I would like to try an orange-brown text color.
The idea is coming from https://salsita.github.io/node-pg-migrate/#/migrations & https://knexjs.org/guide/
The light or dark mode background could stay for now as is / default.

Currently, I have implemented local search. Are we planning to use Algolia for search functionality?

For the start we should use local search, algolia could be enabled later in a separate PR.

What do you prefer, migration pages as it was here or this new way I've done using alerts, tables..

Your way is MUCH better!!! 😍
I wanted to rework them anyway 👍

Is there any feature list to home page or should I remove it?

We could do e.g. write one box for up-down migration/CLI, one for typescript/programmatic support and one for ... 🤔 I don't know
Maybe "steal" from https://github.com/salsita/node-pg-migrate#explanation--goals 🙂

#913 can be closed

I will do a review tomorrow ❤️

Coverage Report

I had a first look and this is SO MUCH STRAIGHT UP BETTER 🤩
OH MY GOD thx 🙏

I see there is still much todo for some more to-table conversions
Let me know if I should merge something in between or if I should just wait until you mark the PR as ready-for-review

I also made some minor changes in terms of preferred style in docs.yml

I invited you to the repo with granted "write" access, so you can (if you want to) help maintaining the documentation further in the future for inside the repo

ok thx, the migration to vitepress is almost complete, just need to refactor some migration pages to tables, you can merge to avoid conflicts and I'll be updating the migrations until they're all more readable

ok thx, the migration to vitepress is almost complete, just need to refactor some migration pages to tables, you can merge to avoid conflicts and I'll be updating the migrations until they're all more readable

Yeah I will do so 👍

You got an invite to the repo, so if you like, you can then remove your fork, re-clone from origin (salsita/node-pg-migrate) and then do PRs from there. This improves co-working from my side if needed.

"deploy from actions" activated