On Fri 20 Apr 2012, Stephen Jolly <steve(a)jollys.org> wrote:
Readily-parsable, stable representations of the node
pages is a big
part of it, and similar representations of the global category and
locale lists would also be useful.
bob has a ticket open for adding the node content to the JSON output
of individual nodes - I will probably implement that at some point,
though I think it actually needs to be done in Wiki::Toolkit rather
JSON output of the global category and locale lists is implemented in svn,
with URLs of the form:
The other obvious and significant missing piece would
be JSON (or
similar) representations of search results -
currently throws a 500, for example, which is arguably a bug all by
I think the OpenGuides search needs to be entirely rewritten from
scratch. I wonder if we should have some form of hackfest to make
this happen? Bob and I could host it (in Croydon).
A standard way to update node contents and metadata
also be needed, although arguably the existing form submission
system could be used.
I do quite a lot of auto-updating/importing on OpenGuides sites - I
use WWW::Mechanize for this.
A JSON representation of the "recent
changes" page would be an
additional convenience, as would be one for the user preferences
Agreed - can you open a couple of tickets for these?
Is that helpful?
It is very helpful, thank you! Do you know when you might be able to
start sharing more details of the things you want to do with all this?
Oh, and a specific useful addition to the JSON
node content would be the image details (where available).
Can you add that to bob's ticket, or open a new one?