Migration to the new wiki

3 views
Skip to first unread message

Paul Grinberg

unread,
Mar 30, 2010, 3:40:40 PM3/30/10
to ul-developers, ul-...@googlegroups.com
At some point in the not too recept past, Devnet migrated us from the old DokuWiki based http://wiki.unity-linux.org/ to the new MediaWiki based http://docs.unity-linux.org/. He even transferred some (unformatted) content from the old to the new site. However, much of the information is woefully out of date and is in need of review. I have started the formatting cleanup. You can check out

http://docs.unity-linux.org/Developers_Portal
http://docs.unity-linux.org/Packagers_Portal

Please visit these pages and review them. If you find something wrong/missing, please edit the content. if you don't have an account, create one! As per our earlier email exchanges, everyone really need to have an account and contribute content.

Paul.

P.S. I have installed an improved editor into the new wiki which should make syntax concern irrelevant. As time goes on, I will be adding more features and will advertise those at a later time. However, if you need/want something in the mean time please post your request.

Gianvacca

unread,
Mar 30, 2010, 4:02:43 PM3/30/10
to ul-...@googlegroups.com
Thanks, Paul, for your work.

Much appreciated.

Custom Processing Unlimited

unread,
Mar 30, 2010, 11:03:06 PM3/30/10
to ul-...@googlegroups.com
much appreciated, and looking forward to a fairly well completed set of pages sometime...

--
"Custom" is NOT mass produced... then it's just a product line.
Custom Processing Unlimited

Paul Grinberg

unread,
Mar 31, 2010, 12:53:19 PM3/31/10
to ul-...@googlegroups.com, ul-developers
The migration is proceeding smoothly. I have added several extensions to improve usability. The latest addition which should be of interest to everyone is the support for Multiple Languages on a per-page basis. An example can be seen here - http://docs.unity-linux.org/index.php?title=Unity_Officers&action=purge - The idea is that if any given wiki article is written with translations, then the language selector bar will appear on the top left of the page. When users open the page, they should automatically be taken to the appropriate translation based on their browser choice or wiki user preferences. If that translation is not available, the user will be shown the English text instead.

I highly encourage everyone to follow the format of this page to add translations to other pages. Please let me know if you have any questions or are experiencing issues.

Paul.

dillj

unread,
Apr 1, 2010, 2:22:05 AM4/1/10
to ul-...@googlegroups.com
awesome extension Paul.
Thanks

Would you mind writng a small instructional so all our translators will know how to use it?

Paul Grinberg

unread,
Apr 1, 2010, 8:12:07 AM4/1/10
to ul-...@googlegroups.com
On Thu, Apr 1, 2010 at 1:22 AM, dillj <the....@gmail.com> wrote:

Would you mind writng a small instructional so all our translators will know how to use it?


Absolutely! This, along with other basic Wiki formatting tips will be posted on the wiki itself when I get around to that. In the mean time, I'll just describe the basic syntax here and now. To have a wiki page with multiple languages:
  1. log into the wiki
  2. browse to that article
  3. click on the Edit button on the top of the article
  4. add the following block of code
<language lang=fr>the french stuff goes here</language>
<language lang=en>the english stuff goes here</language>
etc...
<multilang/>

It's as simple as that! Also note that the order in which the translations are defined determines the order in which the "Available Translations" selector will appear in the upper right. If we decide that this is not the preferred behavior, I can always change it to be in a fixed (ASCII sorted by two letter language code) order.

Paul.

Gianvacca

unread,
Apr 1, 2010, 5:26:21 PM4/1/10
to ul-...@googlegroups.com
Thank you, Paul.


devnet

unread,
Apr 2, 2010, 1:28:20 PM4/2/10
to Unity Linux Docs

On Apr 1, 5:26 pm, Gianvacca <gianva...@unity-linux.org> wrote:
> Thank you, Paul.


Paul et al,


I'd like you all to also take a look at issues assigned to me, John,
and rstob in the issue tracker as many of the documentation tasks are
there. In fact, it would behoov us if we used the issue tracker to
track our documentation process...take a look here: http://powerplant.yoper-linux.org
to see how TobiG approaches it. I think a similar approach might be
good...but nonetheless we should be using the issue tracker for docs.

Paul Grinberg

unread,
Apr 3, 2010, 9:53:05 AM4/3/10
to ul-...@googlegroups.com
The wiki has been updated with the translation instructions - http://docs.unity-linux.org/How_to_translate_content

@devnet. I browsed the yopper link, but did not see what you were referring to. Can you please elaborate?

Paul.

Paul Grinberg

unread,
Apr 4, 2010, 9:41:46 AM4/4/10
to ul-...@googlegroups.com
The wiki is migration is slowly progressing If you'd like to help, please feel free to jump in! This is both an open invitation and a somewhat disappointed realization that almost no one has pitched in so far :-(

I have created a new category on the wiki - http://docs.unity-linux.org/Category:Work_To_Do - This would be a good place to start if you are looking for a quick page to modify. Of course, you can also add any other missing content (any "red colored" link), or create your own content from scratch.

Custom Processing Unlimited

unread,
Apr 4, 2010, 1:54:56 PM4/4/10
to ul-...@googlegroups.com
fixed the issue tracker link... once it's up again, the wiki link will lead to the right place now.

devnet

unread,
Apr 5, 2010, 8:20:24 PM4/5/10
to Unity Linux Docs

On Apr 3, 9:53 am, Paul Grinberg <gri6...@gmail.com> wrote:
> On Fri, Apr 2, 2010 at 11:28 AM, devnet <dev...@gmail.com> wrote:
>
> > On Apr 1, 5:26 pm, Gianvacca <gianva...@unity-linux.org> wrote:
> > > Thank you, Paul.
>
> > Paul et al,
>
> > I'd like you all to also take a look at issues assigned to me, John,
> > and rstob in the issue tracker as many of the documentation tasks are
> > there.  In fact, it would behoov us if we used the issue tracker to
> > track our documentation process...take a look here:
> >http://powerplant.yoper-linux.org
> > to see how TobiG approaches it.  I think a similar approach might be
> > good...but nonetheless we should be using the issue tracker for docs.
>

> The wiki has been updated with the translation instructions -http://docs.unity-linux.org/How_to_translate_content


>
> @devnet. I browsed the yopper link, but did not see what you were referring
> to. Can you please elaborate?
>
> Paul.

I was referring to setting up documentation as a separate project :)
That's how TobiG has yoper setup.

Reply all
Reply to author
Forward
0 new messages