Hi sophi,
Well, sorry for not being responsive, that was diner time and had
people home.
No problem.
I don't know what is 'scares', could you explain that ?
Sorry typos, *squares obviously.
you're the first person complaining about the need to have the
wiki mobile compliant. I don't think the documentation is much read
on phones currently.
It was not only related to the ability to read the wiki easily on a
small screen.
But I don't understand the point in trying to transform a Wiki as if
it was a simple website.
* When the new contributor wants to update some piece of information
on the wiki, when using square boxes, he must double check if is does
not break anything. Too much HTML code.
* This adds even more complexity if you want to reuse the wiki in
other projects like exporting the documentation content to the help
files, etc. (I saw some mails about this, I even reported a topic on
this in LOWN).
When I try to compare the MediaWiki to other tools TDF uses, I have
the impression the main website plays a really minor role here. The
wiki seems at the contrary to embrace every others platform.
Even if you are not redesigning the whole wiki, here are some easy
improvement ideas:
* Like on the ArchLinux wiki [1], integrate the website menu on the
wiki (2 simple PHP include instructions).
* Merge the wiki menu top bar template with the website menu: just a
bit more content to add in the "Contribution" tab.
* Why is the language list located at the top in the wiki while you
have the default left margin dedicated to this usage? --> Losing
vertical space for no reason.
* Why are you adding so much ways to access a simple information. So
much Welcome pages. Just use the welcome pages from the wiki, instead
of rewriting exactly the same content in
http://www.libreoffice.org/community/docs-team/ --> Basically most of
the main website pages should link directly to the wiki.
* Each team is using different layouts on the wiki. Keep It Simple Stupid.
* Using dedicated ODT files for all documentation adds too much
complexity to solve a simple issue/typo. I just got bored to log me in
to OdfAuthors, aka "the documentation team abomination".
I'll ask Dennis' help here and will apply the templates he has
done.
Yet another evidence, a contributor nearly needs web development
skills to be able to write wiki content now.
I won't redesign all the wiki, but only keep the look and feel
currently applied by Dennis. But again I'll ask him the best way to
achieve it, he has done a lot of work on the templates and the
pages.
The simplest way to avoid content duplication, and to give the user
the impression he is always travelling on the SAME platform is to have
the same menu everywhere. Again Arch Linux is, I think, an example to
follow.
You still can do it after I've worked on them
On the Arch Linux wiki I do not hesitate to merge pages, etc. Here,
I'm still rather new in active contribution.
Thanks for highlighting the work done by the project!
Great pleasure, LOWN acts as a summary for myself and others, as a
help for the annual report, and as a marketing tool.
Regards,
[1] https://wiki.archlinux.org
[2] https://pad.documentfoundation.org/p/annualreport
- --
William Gathoye
<william@gathoye.be>