How we might structure the IPFS "file system" to serve Fedwiki pages and integrate this with standalone JavaScript apps.
http://audioboom.com/boos/3835573-ipfs-architecture-for-fedwiki.mp3
We can use IPNS to serve a Fedwiki Page Slug under a given domain. Domains act as they do now as folders, and all folders can (optionally) reside under a common wiki "directory" root in IPFS. A path may then look like:
So if we take a json file for the Fedwik reference link future.fedwiki.org/ipfs-architecture-for-fedwiki:
http://future.fedwiki.org/ipfs-architecture-for-fedwiki.json
That is to be rendered as wiki-page such as:
http://future.fedwiki.org/ipfs-architecture-for-fedwiki.html
This can be represented by an IPFS uri like:
Animated gif showing the resolving of an IPFS path.
/ipfs/Qmcz.../future.fedwiki.org /ipfs/Qmbx.../future.fedwiki.org/ipns /ipfs/QmatmE9msSfk...
See the attached animated gif to understand how these paths are resolved by ipfs. Now we can use IPNS to pint to the wiki page in a mutable way allowing for changes and versioning.
Finsbury Park, London, United Kingdom - openstreetmap 
This recording was made near Finsbury Park, by fortyfoxes, on Nov 20, 2015 at 1:56 PM - audioboom