1) you either use one of the public, legacy http gateways and dial <a href="https:&#x2F;&#x2F;ipfs.io&#x2F;ipfs&#x2F;$myContentHash(&#x2F;andDepending&#x2F;maybe&#x2F;SomePath.png)" rel="nofollow">https:&#x2F;&#x2F;ipfs.io&#x2F;ipfs&#x2F;$myContentHash(&#x2F;andDepending&#x2F;maybe&#x2F;Some...</a> or you use the go implementation which is available for download at <a href="https:&#x2F;&#x2F;ipfs.io" rel="nofollow">https:&#x2F;&#x2F;ipfs.io</a> as a compiled binary.<p>You can use it like a unix command line tool to add and get files but you can also run it in daemon mode. It then also opens a HTTP server locally which allows you to use the same URLs as above just with <a href="http:&#x2F;&#x2F;localhost:8080" rel="nofollow">http:&#x2F;&#x2F;localhost:8080</a> as the schema and host.<p>2) You can use the ipfs cli tool to add a directory with your sites html and other static content. The client will then give the the root content hash. Then you open &#x2F;ipfs&#x2F;$rootHash&#x2F;index.html or &#x2F;site2.html and voila! :)<p>Btw, this article is serving from ipfs. Try &#x27;ipfs get QmNhFJjGcMPqpuYfxL62VVB9528NXqDNMFXiqN5bgFYiZ1&#x27; and take a look in that directory on your harddrive. Also: when you now run &#x27;ipfs daemon&#x27; your node will help with requests for this content.<p>3) To update content with a static name, you can use IPNS, it&#x27;s also mentioned in the article. IIRC: To resolve those entries (and get the latest ipfs content hash) the node with the corresponding key for the ipns entry needs to be online. If it isn&#x27;t, you get an error like &#x27;Path Resolve error: could not resolve name.&#x27;. Maybe come to the #ipfs irc channel on freenode for more specific questions.