RESTful Fedwiki Server

Here we make a start to document the creation of a minimal Fedwiki Server that provides a minimal but fully specified REST API for both existing clients and future mobile clients.

Here we define what the minimum server requirements are for a server to serve Fedwiki contnet to a client. That means assuming a browser or other native client has all it needs to deal with the content, what is required by the server to serve content for read / display purposes only?

The aim is to do this in a nice flexible way moving forwards, so that different server implementations are able to keep in sync. My thought on this is to define, implement and document a simple REST API using DreamFactory to implement and then document the API with - swagger.io .

This generates a standard markup with either:

HTTP/1.1 200 OK X-Powered-By: Express Access-Control-Allow-Origin: * Accept-Ranges: bytes Date: Sun, 28 Jun 2015 11:58:27 GMT Cache-Control: public, max-age=0 Last-Modified: Sun, 28 Jun 2015 11:51:39 GMT ETag: W/"1ed4-1959657124" Content-Type: application/json Content-Length: 7892 Connection: keep-alive

So my starting point is to define the REST API endpoint that everything a client needs to render pages. Later we can add POST, and PUT end points etc.