[OOTB-infra] blog aggregator

[Lanre]

Hi Heiko

In response to your question about the infra chair, I am willing to secede the position to you on your claim of having experience in
this area. I only offered myself as an effort to get things moving. I’m not sure how but I will change the position on github this weekend.

All in favour say aye.

Aye


Lanre 
___________________________________________________________________________
When you do things right, people won’t be sure you've done anything at all.













On 15 Oct 2014, at 20:53, Heiko Robert <heiko.orderofthebee.info at ecm4u.de> wrote:

> Oksana,
> 
> it's not redmine I like it's about to control the data instead of just using their hosted UI.
> It would be very disapointing if we decide to move our content to another server / other platform and then to realize that it's not possible. So same argument against blogger.com like against github for non repo content. Wordpress allows to export content from the hosted version:http://en.support.wordpress.com/export/ but since it's very easy to install I would vote for an own install to access or extend APIs install plugins as designed. For just writing a blog hosted on a subdomain I think it's very hard to compete against wordpress and we should go for that. (btw: alfresco does the same: http://blogs.alfresco.com/wp/) 
> Your second requirement was to create an archive for existing content to be copied or referenced. That would be hard to build in a     blog system if you want more than just tags to structure. I would prefer a wiki like system for that but would like avoid yet another component.
> The redmine aproach was meant by example to avoid multiple solutions and control data: Use an easy to use editorial system to create, link articles, documents, includes but which has flexible APIs to alternativly read/consume the content from other systems like the website using REST/xml or REST/json instead of html output. This would allow us to create the cool design on the website but load the dynamic content using AJAX from the editorial system and to use the easy user interface to manage the content. This technique is easy to implement and only requires JavaScript/json knowledge but all components need to be accessed from the same domain.
> Same approach could be achived with wordpress: http://www.makeuseof.com/tag/wordpress-got-json-api/
> 
> I agree, we should only use as few platforms and/or networks as possible.
> 
> Regards
> Heiko
> 
> Am 15.10.2014 um 19:24 schrieb Oksana Kurysheva:
>> Heiko, why do you like Redmine so much? :) It will be again our internal application. But we need a nice design/interface for external users (not members of the Order). I like JSON on the website because it doesn't require additional tools. But this time I agree, that we need more than JSON.
>> 
> _______________________________________________
> OOTB-infra mailing list
> OOTB-infra at xtreamlab.net
> http://www.xtreamlab.net/mailman/listinfo/ootb-infra

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.xtreamlab.net/pipermail/ootb-infra/attachments/20141015/82e5fa8f/attachment.html>