Click here to edit contents of this page.
Click here to toggle editing of individual sections of the page (if possible). Watch headings for an "edit" link when available.
Append content without editing the whole page source.
Check out how this page has evolved in the past.
If you want to discuss contents of this page - this is the easiest way to do it.
View and manage file attachments for this page.
A few useful tools to manage this Site.
See pages that link to and include this page.
Change the name (also URL address, possibly the category) of the page.
View wiki source for this page without editing.
View/set parent page (used for creating breadcrumbs and structured layout).
Notify administrators if there is objectionable content in this page.
Something does not work as expected? Find out what you can do.
General Wikidot.com documentation and help section.
Wikidot.com Terms of Service - what you can, what you should not etc.
Wikidot.com Privacy Policy.
Hey Kenneth, I removed the experimental/concept/ stuff from the module:_admin page. It's better that the documentation is all always stable, and that conceptual stuff happens elsewhere.
Portfolio
Thanks, that looks a lot neater. :-)
Kenneth Tsang (@jxeeno)
This doc gonna a be an English only website as I see how it is designed
I'm not sure, but what's clear is that whatever I write (representing the official voice of Wikidot) in terms of doc will be English, period. So how, when, where do we translate?
Portfolio
The lonely proposal for a multilingual documentation was made on the simple basis: category is used for language. There might be another solution, launch a call for better solutions.
In the meantime, I say: http://doc.wikidot.com is not designed as a multilingual documentation, period.
@Gerdami: my first vision for the doc site was to make an evolution of the current doc category. There is always the danger of "version 2 syndrome" when we try to do too much at once, so I prefer to make changes in small discrete steps.
Mainly a new site is to allow improvements to the current English doc. For example, Kenneth's idea of a wish per documentation page, which I think is great - it captures a certain kind of discussion in a clean way.
A multilingual project needs IMO to work off a fairly stable basis. So I'd see this happening when the doc site has gone through a first complete build.
The Wikipedia solution is to build independent sites (for us, Clone + Translate).
The Google solution is live translation (sidebar widget).
What's the Wikidot solution? We don't have large non-English communities but this could be way to encourage that.
How feasible would it be to add babel capability to the doc site after it's been built?
Portfolio
Hence, do not create a new site. Keep enhancing the present one.
Do not compare with Wikipedia and its thousands of editors
It's not a solution, it's just a gadget which users find annoying at use. Those who rely on Google translate have it in their browser's toolbar.
ListPages parent="en:embed" tags="video,audio"
End of post for the moment
Forget the autonumbering with the babel model !
1st mockup : http://babel-doc.wikidot.com/en:modules
It is really annoying of being unable to add comments to edits.
For those who disagree: please consider that:
I agree 100%. Was going to post that but didn't get around to doing it yet.
~ Leiger - Wikidot Community Admin - Volunteer
Wikidot: Official Documentation | Wikidot Discord server | NEW: Wikiroo, backup tool (in development)
Ooops. I put the latest editor CSS on the various expert sites but forgot this one. It's really quite painful to not have cross site includes.
Portfolio
@Kenneth,
Just to say that I really appreciate the work you're doing on the doc site, and I like the ideas, like adding a wish section. Next week I'll find some time to actually start writing content, and we can see how this integrates. I need to redesign the large documentation pages into pieces that can be linked together properly. E.g. we have a 'category selector' in many modules, it should be documented exactly once.
The wishes should be attached to doc pages (parenting) and have some state (_closed means done or canceled). Maybe you already did that.
Uhm, Gerdami, thanks to you to, I see your edits.
Portfolio
Ok. Adding the _closed tags now. Just a question, do i apply the wishes for the category "doc"?
Kenneth Tsang (@jxeeno)
Yes, I think so. Since the parent page can be anywhere, there is no conflict. You are autonumbering wishes, right?
You should take a look at the babel-template.wikidot.com site and see how Gerdami has implemented multilanguage wikis. We need to not build structures that are untranslatable afterwards.
There may be, as Gerdami says, other ways to do multilingual sites. It is something we need to add into Wikidot at some stage anyhow.
Portfolio
@Kenneth, I've pasted the new ListPages doc into the site.
The use of sections makes it kind of difficult. I think we need to reduce this to one section. Examples and wishes can be separate. The first paragraph can always be the summary.
Portfolio
Done. :-)
Kenneth Tsang (@jxeeno)
:-) Nice.
Portfolio