Going IPv6-only with what you use the internet for daily will break things.

For time being the recommended approach is a dual-stack setup with NAT64 + DNS64 in the mix.

NAT64 you'll need Jool on Linux and DNS64 you can just easily use Google or Cloudflare's public DNS64 servers or run your own.

In general, yes, this is possible. However, it is more difficult than just disabling IPv4 on all your devices.

First of all, there are still many (more or less relevant) sites that still are IPv4-only. If you want to reach them via your IPv6-only home network, you need to set up or use services that translate your traffic from IPv4 to IPv6 and vice versa. But this can be error-prone and needs work and understanding of the matter from your side.

The easiest is that you just leave IPv4 and IPv6 enabled in parallel. Your operating system will usually prefer IPv6 over IPv4 if it's available.

Unfortunately until website owners starts being aware that IPv6 exists, you can only go IPv6-only if you have NAT64. Look at this:

From this screenshot I can see a couple instances (3 Hetzner IPs, one OVH, one DigitalOcean, one AWS and one from AS211772 (they also do have an IPv6 range announced)) that are IPv4-only. All of them could have IPv6 support but they only add the A record on their DNS records and call it a day. It is very annoying to see that.

The only practical way to go IPv6 only right now is to use NAT64. This allows you to access IPv4 websites using your computers IPv6 address however it's not trivial to configure, you'll need a proper router(or Linux server), not just whatever router your ISP provides, and said router will still need an IPv4 WAN address but your PC, phone, etc can go IPv6 only and still access legacy sites like GitHub etc. For reference my home network is IPv6 only. I use jool for NAT64