From @piotr-yuxuan on Fri Oct 28 2016 16:32:20 GMT+0000 (UTC)
First, thank you for IPFS, it seems to be a definitely fun and perhaps promising idea 
Any document is dynamic most of the time: its URL can change and so can its content itself. IPFS hashes solves the first part but how can we retrieve the latest available version of a document?
To the best of my knowledge, tree-based version control system (such as git) makes it trivial to access to parents of a document but further revisions are less easily accessible.
Copied from original issue: https://github.com/ipfs/faq/issues/192
From @Geemili on Sun Oct 30 2016 23:48:53 GMT+0000 (UTC)
The IPNS (InterPlanetary Name Space) solves the issue of accessing the latest document. It is described near the end of the IPFS white paper.
Every user is assigned a namespace at /ipns/<NodeId>. Then a user can put new files at places underneath this, like /ipns/<NodeId>/cat.gif, which would link to a IPFS content address in its metadata.
From @fasiha on Sat Nov 19 2016 21:01:15 GMT+0000 (UTC)
Here’s a tidy summary how people accomplish this: https://ipfs.io/ipfs/QmdPtC3T7Kcu9iJg6hYzLBWR5XCDcYMY7HV685E3kH3EcS/2015/09/15/hosting-a-website-on-ipfs/ 
From @piotr-yuxuan on Fri Jan 13 2017 22:20:19 GMT+0000 (UTC)
Great thank you for your explanations, I can close it.
From @RichardLitt on Wed Jan 18 2017 19:32:05 GMT+0000 (UTC)
Let’s keep this open to make it more easily searchable. Adding the answered label.