On 8 Sep 2015 at 15:50:33, Ecaterina Moraru (Valica)
(valicac@gmail.com(mailto:valicac@gmail.com)) wrote:
Hi,
This vote has not be concluded.
The majority of votants were in favor of the term 'Page', since it's easier
for end users to understand.
Note that in the VOTE results, we should count binding VOTEs (ie from committers)
separately (even though other people’s VOTE should be taken into consideration by
committers when they VOTE themselves).
We should take this conclusion in consideration when
doing changes to the
translations, in order to assure consistency.
I see you’ve gone ahead and replaced Documents by Pages everywhere. Personally this looks
to me. Note that the same will need to be done in the documentation on
xwiki.org(http://xwiki.org) probably. Even though in lots of cases Documents is more
precise than Page, it’s probably simpler for users to read Pages.
Said differently I’m in favor of using Pages when both Pages and Documents would fit, in
order to make it simpler for users.
Since Page = rendered(Document) + Panels + Skin, anything that talks about Document can be
modified to talk about Pages I think (it’s just less precise). I couldn’t find a sentence
where it would be plain wrong to talk about Pages instead of Document. For example, “the
xobjects of this page” works IMO, since a page is more than a Document so it’s a short way
of saying “the xobjects of the document contained by this page”.
I can think of 2 exceptions:
* Dev documentation. For example to explain the $xwiki.getDocument() API it’s probably
better to mention Document instead of Page
* For a Page definition… :) For example: “In XWiki a Page is the rendered version of a
Document’s metadata (content, title, xobjects, etc), including Skin elements and Panels”.
WDYT?
Thanks
-Vincent
Thanks,
Caty
On Thu, Jan 20, 2011 at 12:09 PM, Thibaut Camberlin <
thibaut.camberlin(a)xwiki.com> wrote:
> Hello,
>
> I think that pages should be used for everything that is exposed to end
> users. From an end user perspective, there is no difference between a page
> and a document, so there is no point in using 2 different wordings. Page
> makes more sense IMO.
>
> Document should be used for XWik advanced users.
>
> --
> Thibaut
>
> On Thu, Jan 13, 2011 at 11:34 PM, Sergiu Dumitriu
> wrote:
>
> > On 01/10/2011 12:49 PM, Gregory GUENEAU wrote:
> > > +1 also for page, for the same reasons raised by others
> > >
> > > BUT : could we have it as a variable in the admin ? We could imagine
> > situations where it is important for the user to name it document, and to
> > name a space as "folder", or "application".
> >
> > No, this is going to do more harm than good. What do we write in the
> > documentation? Do we make 2-3 sets of screenshots to show the possible
> > display variants?
> >
> > > More : as we have page type management, could we have generic page
> types
> > (page, document, code, etc.) with specific icon in the UI ? Same with
> spaces
> > (space, project, application, etc.)
> >
> > Valid idea for the future.
> >
> > >
> > >
> > > Le 7 janv. 2011 à 16:53, Ecaterina Moraru (Valica) a écrit :
> > >
> > >> Hi,
> > >>
> > >> We are using mixed naming when referring to a document/page, not only
> on
> > >> different pages, but also in the same context (Rename step for
> example).
> > >> There is also an issue referring to this problem
> > >> XWIKI-5401and we need
> to
> > >> find an answer in order to move forward consistency.
> > >>
> > >> So the question is which version we prefer: "Page" or
"Document" ?
> > >>
> > >> I'm voting +1 for "Page".
> > >>
> > >> "Page" is more used IMO, especially in the
"Space"/"Page" context.
> > >> "Page" is more general than "Document" and better
fitted for a
> platform
> > that
> > >> encapsulates all kind of content (not just documents).
> > >>
> > >> Please cast your vote.
> > >> Thanks,
> > >> Caty