On Thu, Mar 29, 2012 at 11:06 PM, David Bovill <da...@architex.tv> wrote:

> On 27 March 2012 17:35, Stephan Beal <sgb...@googlemail.com> wrote:
>
>> The considerations which have come to mind so far:
>>
>> - i would prefer to keep it in wiki form, as opposed to embedded docs,
>> because i often write docs from arbitrary locations.
>>
>
> Yes
>

Hi, David! Thank you for the feedback...


> Personally I'd prefer MediWiki markup - as that's where the content is -
>> but whatever :) Is it possible to include a JavaScript based skin switcher
>> - that way you could have a choice of markups - given someone writing a
>> skin with an embedded parser?
>>
>
Even one step further: a given site can use multiple renderers as long as
it has a way of distinguishing wiki pages by type (e.g. by extension,
naming convention, or some marker tag in the first few bytes). e.g. it
could use MediWiki + Google Code + Markdown, and even link between them, as
long as the site implements the code to handle the intra-page links (it's
not as hard as it sounds - a few lines of jquery normally does the job).
e.g. the GoCo renderer post-processes the parser-generated links with:

http://fossil.wanderinghorse.net/repos/fwiki/index.cgi/artifact/754a19ba9a0dde07e75dec59f1ad454cc2d5f5d7?ln=19-58



> While we could argue forever about the down-side of the non-googlability
>> of client-side-rendered wikis, i think it is important that that the
>> documentation for the JSON API be served via the JSON API, if for no other
>> reason than having it as the canonical demonstration app.
>
>
> Yes - a static dump with links to the live wiki could help?
>

Interestingly, i came to the same conclusion last night. It wouldn't be
much work to dump generated copies. PhantomJS (or similar) could be used to
set up a generator for this purpose.

-- 
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to