Well, one idea was to make a custom skin with "easy to change" elements to
adapt it to each partner (there is currently 3 other sites that want to
embed the wiki in them website).
This would have some implications :
1- Make an adresse with "the look and feel" of the pateneer. (Best would be
, yet we can make easily partner.design-platform.org
2- We know how to make the adress in the partner site redirect to a wiki
page with the patner skin, using &useskin=myskin. Yet we don't know to do so
that when any user from the partner site click on an existing link in the
page, the skin stays the partneers skin.
3- When an user decide to edit a page, we would like that the user come back
to the original wiki, where there is all the community tools such as forum,
liscence specification, etc... Well, this is not exactly mandatory. What we
want is the spirit being "the partner site provide easy access to the wiki
content". With the community still identified under the "design platform"
identity. This mean we could play on graphisms to achieve it in another way
(for example a logo partner + design-platform).
So that I really don't know what is the most simple between the a skin and
extracting the content of a page.
Maybe I could try to make some researches on point 2 wich is the biggest
issue. We can change the mind of the project a bit to adapt to this
Have a nice day.
2009/6/29 Platonides <platonides(a)gmail.com>
Thibaut DEVERAUX wrote:
So, in order to keep you on date with this
adventure... we have
identified two new links where there is more hope :
Generating an XML code.
Generating a render
Next steps are to write code to :
* Change the links so that te user stay on the pateneer website.
* Add an "edit this page" link that come back on the wiki in edit mode.
* Make a page with a css and a menu on the parteneer site that prints
the wiki page.
Step by step, we go further.
PS : If someone know an open source code that already does it it would
save a lot of time ! (evryone is volonteer in the team) Thanks ! ;-)
A custom skin with the look & feel would probably be a better solution.
Mediawiki-api mailing list