# Adressing mutable content **URL:** \ **Category:** Ecosystem and Usage\ **Created:** [December 13, 2017, 5:03pm UTC](https://discuss.ipfs.tech/t/adressing-mutable-content/1626 "2017-12-13T17:03:40Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![Apollo22](https://avatars.discourse-cdn.com/v4/letter/a/f475e1/32.png) [@Apollo22](https://discuss.ipfs.tech/u/Apollo22)\ **Post date:** [December 14, 2017, 6:27am UTC](https://discuss.ipfs.tech/t/adressing-mutable-content/1626/5 "2017-12-14T06:27:34Z")
So after your comments the only advantages I see for the system I explained are: - Ability to link a mutable page to any page without needing to update the link should the linked page be changed. [1] - Ability to group pages under one key. [2] - Should the version system be implemented, by able to see every pages / ressources this “page hash” used to point to. (Updated the version system part on the first message) The issue if you host a website is that you need a new folder with files for every page you have that might change. I think it would be nice to have some documentation about IPNS, because I don’t think I fully understand it and what it offers. But from what I understand, it is too much linked to the node to be a system used to point to mutable content. [This link](https://discuss.ipfs.tech/t/ipns-publishing-after-generating-a-key/90/5) helped me understand a bit more about it but I am still not confident with the subject. If you have any links about the way it will eventually work, feel free to send them. [1] Also you could have an IPNS adress for each page, you still need to update the DHT table every 12 hours. [2] With IPNS you have one keypair for each page (not exactly sure about this one). --- _[View the full topic](https://discuss.ipfs.tech/t/adressing-mutable-content/1626)._