[wikka-community] [wikka-devs] Wikka vision
Wed Mar 14 22:47:20 GMT 2007
(I forward your reply to the Community lists too if you don't mind).
I like the idea of connectors, which would nicely complement the idea
of an API for remote calls.
(for an API to allow remote syndication of content, here's a relevant
discussion at wikimatrix: http://www.wikimatrix.org/forum/
On 14 Mar 2007, at 22:09, Brian Koontz wrote:
> On Wed, Mar 14, 2007 at 09:58:17PM +0000, Dario Taraborelli wrote:
>> My proposal, in a sense, is the opposite of what you are suggesting.
>> I think we should aim at making Wikka as easy as possible to *plug*
>> into existing projects in terms of functionality, authentification
>> and look. Some examples:
> Dario, to do this will require some architectural changes to the
> core to
> accomodate "connectors" that will allow this to happen. If we provide
> a complete API for developing connectors, then we leverage the help of
> others who might then go off and write connectors for their particular
> piece of favorite software (blog, CMS, etc.).
> I believe that your goal of continuing to be lightweight is still
> achievable. APIs, properly implemented, should add minimal overhead,
> and certainly should be virtually undetectable (performance-wise) in a
> "stock" Wikka install.
> So maybe our focus, to help achieve Mahefa's goal, is to focus on
> designing an API (or set of APIs) that will allow either us or
> third-party developers to create either plugins or connectors. With a
> complete set of plugins and connectors, Wikka could be configured to
> be whatever kind of CMS the end-user wants it to be.
> Just my USD0.02 worth...
More information about the community