The aim is to have Fedwiki running as a pure Javascript application (no custom server required) and served by IPFS to allow a fully decentralised platform.
How we might structure the IPFS "file system" to serve Fedwiki pages and integrate this with standalone JavaScript apps.
We imagine how wiki client code might maintain its permanent state in IPFS. We suggest an integration with the journal as currently implemented.
Status
It now appears that IPFS fully supports CORS. Previously, IPFS would default to disallowing CORS. There is some discussion regarding API_ORIGIN - github 
HTTP/1.1 200 OK Accept-Ranges: bytes Cache-Control: public, max-age=29030400 Content-Length: 443230 Content-Type: image/jpeg Etag: cat.jpg Last-Modified: Thu, 01 Jan 1970 00:00:01 GMT Suborigin: QmW2WQi7j6c7UgJTarActp7tDNikE4B2qXtFCfLPdsgaTQ X-Ipfs-Path: /ipfs/QmW2WQi7j6c7UgJTarActp7tDNikE4B2qXtFCfLPdsgaTQ/cat.jpg Date: Mon, 22 Jun 2015 13:11:39 GMT
Need to check if IPFS issues wilcard CORS headers. This would be needed to be able to mix content from the IPFS Daemon and other nterent content. There is a discussion here - github
Currently sending an http request to the ipfs daemon runnin glocall returns the following headers: