Hello developers. I'm here to propose a new template in XWiki to help users
creating container-oriented pages.
= Problem =
UC1: Users don't always understand the Nested Pages concept. They are lost
because they know the concept of Folders and Files and they are used to it,
and then we ask them to switch to something new that breaks their habits.
UC2: Users often need a page that will be the container of some others
(think about the typical "Code" space that we have in all applications) and
they'd like to see quickly all children of that container.
= Proposition =
* Introduce a Folder template the user can chose when she creates a page.
* This folder template displays the children of the page
** It could even be a Dashboard with the children pages on the left, and an
Activity Stream on the right.
== Drawback ==
The workflow of creating a page that is a folder instead of directly create
a folder might be confusing.
== Screenshots ==
Screenshot of my proposition are available there:
http://design.xwiki.org/xwiki/bin/view/Proposal/FolderTemplate#HScreenshots
Please answers your ideas on this mail thread, not on the wiki.
Thanks,
--
Guillaume Delhumeau (guillaume.delhumeau(a)xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
Hi devs,
The story
========
1) We introduced some new translations keys in https://github.com/xwiki/xwiki-platform/commit/5c50e2e88bb7cf592c1ecedcf0f3…
That was done in XWIKI-12431 (Adapt the "rename" action for nested documents), i.e. in 7.2M3
2) We modified the keys in https://github.com/xwiki/xwiki-platform/commit/12ec17d1c486935162581d47bbf1…
That was done in XWIKI-13067 ("Rename: Change the label to make it clear that both links and backlinks are updated or have 2 separate options”), i.e. in XWiki 8.0-rc-1, 7.4.3
3) The consequence is that all translations got broken, resulting in problems such as http://jira.xwiki.org/browse/XINFRA-219. However this issue reports the issue only for French but it’s likely that it broke the translations for other languages.
The learnings
===========
1) We must never change the format of existing translation keys. This is the equivalent of breaking an API. Instead we need to go through deprecation of existing keys and introduction of new keys, even though it’s a pain. http://dev.xwiki.org/xwiki/bin/view/Community/DevelopmentPractices#HTransla… would probably benefit from additional explanations too.
2) We would need a tool in the quality profile of our build/CI that would break the build if someone changes the format of a translation.Easiest would be a tool that compares the English translations on master vs the last released version and breaks if there’s a difference in parameter (i.e. {N} syntax).
3) We need to decide if A) we keep the current change done in XWIKI-13067 or B) revert them and revert/adapt the changes already brought to some translations keys (as it was done for FR). For this we need to evaluate the extent of the damage.
Any volunteer for 3)? :)
Thanks
-Vincent
Hi,
This is a idea proposal for an Administration Overview that:
A. Provides generic/global information about the instance like 'version',
'instance id', etc.
B. Provides a summary of usage listing count of major entities (wikis,
users, pages, extensions, etc.)
C. Lists demo content installed in the wiki
D. Provides a way for administrators to subscribe to the XWiki Community
I'm curios which of the above section sounds interesting to you and would
like to see inside the product. Also maybe you have other ideas of what is
missing or could be represented better.
Thanks,
Caty
Hi devs,
We need to debug our udpate_ow2() which is broken ATM.
It does several curl calls but there’s a “-o /dev/null” that prevents seeing errors.
It would be great if the next RM could remove those and report the error, (and even possibly work to fix the problem with the others).
Thanks
-Vincent