If you're happy with that model for immutable things then we can move on the mutable ones. Whenever you update your blog (e.g. by modifying the home page to have a link to a new blog) you can republish your IPNS record.

In particular you'd do `ipfs name publish --key=myKey /ipfs/QmNewBlogRoot` every time there's a new blog root. You can then resolve `ipfs resolve /ipns/QmMyKey` to get the latest content.

Some things to note:
- If you want multiple different mutable pointers (e.g. one for you car blog and another for your list of favorite books) you will need multiple different keys, these can be generate with `ipfs key gen`. You can also do `ipfs name publish /ipfs/QmNewBlogRoot` without generating a new key and it'll use the same key as your IPFS node does.
- The tooling around letting your friends republish IPNS records for you while you're offline isn't really there yet (i.e. it works at a protocol level, but no one's gotten around to building out the commands for it yet). As a result if the IPNS publisher is offline for a while you could run into some problems, since the IPNS record will only be available as long as the record continues to be in the DHT (at least a few hours, perhaps up to a day).
- IPNS resolution can be pretty slow right now. However, if you run the IPNS over PubSub experiment (i.e. `ipfs daemon --enable-namesys-pubsub`) things will be faster. Additionally, if at least one of your servers is always online then IPNS over PubSub will generally keep the record alive even if the publisher is not online