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.
The following are also meta data to the page content:
The meta data should be as consistent (in content, naming, and formatting) as possible with the dictionary returned by XML API site.pages() and the 'meta' dictionary returned by page.get():
Using the same names as the API Making the API use the same names is a good idea. I think only the meta data that can be changed in the edit is shown in a page; so we can ignore site, category, and name.
Portfolio
However, the API needs to be made more consistent too. "name" vs. "parent_page".
Portfolio
So you mean parent_name or name_parent ?
~ Leiger - Wikidot Community Admin - Volunteer
Wikidot: Official Documentation | Wikidot Discord server | NEW: Wikiroo, backup tool (in development)
I think the API should use 'parent' unless there is a reason to disambiguate. We should be using the names taken from the ListPages redesign sketch.
Portfolio
This is a fine idea, but I think it should be disabled by default (i.e. if someone adds those lines of code, it works… but in using the NewPage module those lines are by default not shown)
Reason — I want to make editing pages as simple as possible for new wikidot users on my website. If they see metadata at the top they might accidentally change it and cause problems. Experienced users that know how to modify meta data can still do so, just by typing in a few extra lines! :)
Then again, you've mentioned that only administrators and moderators will be able to "view" and "edit" meta data.
If the page source contains [[meta]] … [[/meta]], how will it deal with a regular user clicking 'edit' ? Will it simply show the rest of the source, but hide anything within meta tags ???
Please explain…
~ Leiger - Wikidot Community Admin - Volunteer
Wikidot: Official Documentation | Wikidot Discord server | NEW: Wikiroo, backup tool (in development)
I'm not sure exactly how/when you'd see the meta data on a page. Maybe it's an upfront choice ("See metadata on this site") restricted to admins/mods.
Portfolio
Simpler: users can enable meta data editing and will see it on all pages. They will only see meta data they are allowed to edit.
Portfolio
Just created a wiki article that relates to this design.
http://blog.wikidot.com/wiki:design-forms
~ Leiger - Wikidot Community Admin - Volunteer
Wikidot: Official Documentation | Wikidot Discord server | NEW: Wikiroo, backup tool (in development)