Press page

in code: r5131

now waiting for wiki :)

• http://test.bewelcome.org/press
• http://test.bewelcome.org/mediawiki/press
• http://test.bewelcome.org/about/press

don't work for me.

I set this to "test".

Anyway, wouldn't it make sense to make this part of the "about" application?

Also have a look at the "externalcontent" app - we can reuse the ExternalContentWidget?, which allows to replace hyperlinks (so far only works if the hyperlink is given as absolute link, as in WordPress?). See

• http://test.bewelcome.org/externalcontent (wordpress)
• http://test.bewelcome.org/externalcontent?http:;;www.bevolunteer.org;wiki;Press (mediawiki). Problems here: (i) Replacing relative hyperlinks does not lead to good results. (ii) picking DOM elements by id uses ids that only appear in wordpress. This could be easily adjusted to MediaWiki.

Other funny things could be:

• we make subpages in our mediawiki: "About/Press", "About/Xyz" etc. Then, given a request "about/press" or "about/xyz" in bewelcome, we can automatically display the page "
• Allow groups or members to have their own external content pages. We would have to approve every such inclusion, to make sure we don't run into legal trouble. See #320, "include member content from other sources"
• Create an admin backend to map request urls to external content pages. The mappings would be stored in a database table.

who is working on this? how should it work?