jonathanj / fugue Goto Github PK

• Introduction
• Installation
• Pedestal inspiration
• Problem being solved
• Solution
• Brief (not necessarily complete) examples
• Development (tests, filing bugs)

Prose documentation, specifically.

Fugue is not very useful without this.

Twisted Web and Nevow share a lot of code, it should be fairly straightforward to write a Twisted Web interceptor and adapter that leverages the existing Nevow code.

Logging should probably be a priority early, before too much (more) code is written without it and without tests for it.

Eliot has been a good choice in the past because of it's causal approach, having it output to other logging platforms is fairly easy.

These can probably be easily retrieved from the Hyperlink URL object, but we want them in the context for routing possibilities.

Since there is a runnable Twisted example, probably a Nevow one isn't a bad idea.

There's no coverage for the interceptor itself at all and there should be better coverage for the adapter, specifically around errors.

Setting a scene and how Fugue can solve what are hopefully common issues for developers would be a good documentation start.