peter1000

In my opinion this is already included: - we need a permission file as this is central to subuser so just use a docker file with a single FROM and...

Ah you mean a register subuser repo on docker https://index.docker.io/ with some `official subuser controlled (by you) supported images?`

do we still want to implement `--from-store` or does the upcoming: from saved image is enough. I think an `official subuser repo (controlled by yourself)` might be for some users...

hi, I would be interested if you could share a bit what you have in mind for `Compose.jl-like API for creating static documentation.` Anyway, I will busy for a couple...

I did a small graph to get a feeling how that would/could look like based on a joined **Docile/Lexicon Documentation**. Did not add all Docile modules - just to get...

BTW: I send you some thought about aside-comments to [gitter](https://gitter.im/MichaelHatherly/Docile.jl)

> We don't need SubSection Yes I know just wanted to put the structure out > Anything internal to a Page is part of the page, like Header, and so...

I plan to work next on this issues: which are all inter-related. https://github.com/MichaelHatherly/Lexicon.jl/issues/118

I was wondering about the `docs` node which accepts `Union(AbstractString, Module))` If you look at my [example](http://peter1000.github.io/new_lexicon_example_docs1/api/docile.collector/#external) after appling the filter there where no objects for: **External - Modules, Functions,...

At the moment my own feeling for `docs` would be: - allow only `modules` for docs - remove the `AbstractString` - for an optional header text use a config: e.g....