Search: concept

Last modified by Vincent Massol on 2014/10/21

Results 1 - 10 of 75 next page » Page 1 2 3 4 5 6 7 8

XWiki.org Concept (2016)

Located in
Last modified by Vincent Massol on 2024/11/19
Rendered document content
Improve the layout of XWiki's Concept page. Proposal Before After
Title
XWiki.org Concept (2016)
Objects
mails : * [XWiki.org] "XWiki's Concept" page improvements http://markmail.org/message/w3dztiourthzgovo (May 27, 2016)
Raw document content
* Improve the layout of [[XWiki's Concept>>xwiki:Documentation.UserGuide.Features.SecondGenerationWiki.WebHome]] page.

Simple and Advanced administration concept

Located in
Last modified by Vincent Massol on 2024/11/19
Rendered document content
Administration of application is often not seen Feature proposal : Hide options from the UI to simplify it Allow an advanced and a simple mode for the administration The advanced mode will show all of it The simple mode (default mode) would show only the necessary items for a wiki to be configured by an end-user Simple mode : Wiki Informations (all field in the page) Descriptor Pretty name Description Home page Owner Configurations (all fields in the page) Versioning > Enable version summaries Language > Multilingual (Yes/No) Yes > Supported languages Language > Default Language Date / Time > Date format Date / Time > Timezone Office server state (If local users) Email > Obfuscate Email Addresses Email > Email address to send from Content templates (keep the actual) Look & Feel (all fields in the page) Design Design > Wiki logo Design > ColourTheme > Pick a ColourTheme Design > ColourTheme > Manage ColourTheme Page metadata visibility > Show page annotations Page metadata visibility > Show page comments Page metadata visibility > Show page attachments Page metadata visibility > Show page history Page metadata visibility > Show page information Footer > Space Copyright Footer > Version Panel Wizard Users & groups Member (keep the actual without the Configuration section) Groups (keep the actual but rename XWikiAllGroup into MembersGroup) Rights (keep the actual) Extension manager (Keep only the first page "add extensions" and add the update button into it and a filter to see only user installed extensions) Application Annotations Google Analytics™ User Directory Applications Panel ... other installed applications Advanced mode All features that can't be set at the sub-wiki level should be removed Feature benefits : SImpler UI aiming towards end-users Simpler access to applications administration Concept of advanced/simple already well known Nothing removed Feature flows : Still not good enough to present applications An other proposal with only 2 sections would be best (Wiki and Application) Second design :
Title
Simple and Advanced administration concept
Raw document content
* Administration of application is often not seen **Feature proposal :** * Hide options from the UI to simplify it * Allow an advanced and a simple mode for the administration ** The advanced mode will show all of it ** The simple mode (default mode) would show only the necessary items for a wiki to be configured by an end-user * Simple mode : ** Wiki *** Informations (all field in the page) **** Descriptor **** Pretty name **** Description **** Home page **** Owner *** Configurations (all fields in the page) **** Versioning > Enable version summaries **** Language > Multilingual (Yes/No) ***** Yes > Supported languages **** Language > Default Language **** Date / Time > Date format **** Date / Time > Timezone **** Office server state **** (If local users) Email > Obfuscate Email Addresses **** Email > Email address to send from *** Content templates (keep the actual) ** Look & Feel (all fields in the page) *** Design **** Design > Wiki logo **** Design > ColourTheme > Pick a ColourTheme **** Design > ColourTheme > Manage ColourTheme **** Page metadata visibility > Show page annotations **** Page metadata visibility > Show page comments **** Page metadata visibility > Show page attachments **** Page metadata visibility > Show page history **** Page metadata visibility > Show page information **** Footer > Space Copyright **** Footer > Version *** Panel Wizard ** Users & groups *** Member (keep the actual without the Configuration section) *** Groups (keep the actual but rename XWikiAllGroup into MembersGroup) *** Rights (keep the actual) ** Extension manager (Keep only the first page "add extensions" and add the update button into it and a filter to see only user installed extensions) ** Application *** Annotations *** Google Analytics™ *** User Directory *** Applications Panel *** ... other installed applications * Advanced mode ** All features that can't be set at the sub-wiki level should be removed [[image:Simple_administration.png]] **Feature benefits :** * SImpler UI aiming towards end-users * Simpler access to applications administration * Concept of advanced/simple already well known * Nothing removed **Feature flows :** * Still not good enough to present applications ** An other proposal with only 2 sections would be best (Wiki and Application) **Second design :** **[[image:XWiki_Preferences_(XWiki.XWikiPreferences)_-_XWiki_-_2016-02-22_18.08.07.png]]**

Usability Scenario #4 - User#1

Located in
Last modified by Vincent Massol on 2024/11/19
Rendered document content
Successes No problem in editing the Profile information She found interesting the 'Save&Continue' and 'Save&View' buttons and knew how to used them without problems Used 'Search Suggest' to locate the Marketing wiki Points of Confusion 'Wiki'-'Space'-'Page' concept The folder icon used for 'Spaces' It was not very clear the 'wiki-space-page' hierarchy It's not only about the hierarchy, but also difficult to understand the concepts and differences between them When asked to create a page with a certain content, she tried to add the content to the 'Create Wiki' - 'Description' area Did the tasks using only page and wiki concept Looking for 'New' instead of 'Add' Issues Critical issues Difficult to understand that you need to 'Join the wiki' in order to be able to edit If you didn't joined the wiki, the 'Add' options are not available This lead to making the user go to the wiki where he has rights in order to create pages Less-than-critical issues Some minor issues Clicked initially on 'Registered' and then she logged-in.
Raw document content
{{toc start='2'/}} == Successes == * No problem in editing the Profile information * She found interesting the 'Save&Continue' and 'Save&View' buttons and knew how to used them without problems * Used 'Search Suggest' to locate the Marketing wiki == Points of Confusion == * 'Wiki'-'Space'-'Page' concept ** The folder icon used for 'Spaces' ** It was not very clear the 'wiki-space-page' hierarchy ** It's not only about the hierarchy, but also difficult to understand the concepts and differences between them *** When asked to create a page with a certain content, she tried to add the content to the 'Create Wiki' - 'Description' area ** Did the tasks using only page and wiki concept * Looking for 'New' instead of 'Add' == Issues == === Critical issues === * Difficult to understand that you need to 'Join the wiki' in order to be able to edit ** If you didn't joined the wiki, the 'Add' options are not available ** This lead to making the user go to the wiki where he has rights in order to create pages === Less-than-critical issues === === Some minor issues === * Clicked initially on 'Registered' and then she logged-in.

XWiki.Org Improvements (2017)

Located in
Last modified by Vincent Massol on 2024/11/19
Rendered document content
for Menu on mobile for Content Menu items Menu: less items External Links: more them to the appropriate categories Remove Configuration page by creating specific pages for the various configuration elements + link them from the AdminGuide Reference generic image placeholder - no image provided Platform vs. Standard Flavor? Concepts: 1: XWiki Product + several Flavors (+ extensions) 2: Generic Development Platform 3: Extensions 4: Main wiki (User/Admin/Dev guides + Flavors links) + Extensions Deprecate Platform / Enterprise wiki (redirects / read-only) -> moving stuff to the main wiki Move pages under User/Admin/Dev Guides Move / Create Nested page with the topics (Add redirects to preserver bookmarks) Remove mentions of XWiki Enterprise with XWiki or Extension name (ex. "Notification app allows you to ... ") Check Carousel entries Features: Concepts + Bundle Extensions Promote Flavor concept (Generic XWiki + Flavors [there is also the Standard Flavor developed by XWikiDevTeam] ) + mention Standard Flavor in the Guides List features included in the Flavor Base Features (Base Flavor) 2.
Raw document content
Standard Flavor? *** Concepts: **** 1: XWiki Product + several Flavors (+ extensions) **** 2: Generic Development Platform **** 3: Extensions **** 4: Main wiki (User/Admin/Dev guides + Flavors links) + Extensions ***** Deprecate Platform / Enterprise wiki (redirects / read-only) -> moving stuff to the main wiki ****** Move pages under User/Admin/Dev Guides ****** Move / Create Nested page with the topics (Add redirects to preserver bookmarks) ****** Remove mentions of XWiki Enterprise with XWiki or Extension name (ex. "Notification app allows you to ... ") *** Check Carousel entries ** Features: Concepts + Bundle Extensions ** Promote Flavor concept (Generic XWiki + Flavors [there is also the Standard Flavor developed by XWikiDevTeam] ) + mention Standard Flavor in the Guides *** List features included in the Flavor 1.

Folder Template

Located in
Last modified by Vincent Massol on 2024/11/19
Rendered document content
Problems UC1: Users don't always understand the Nested Pages concept. They are lose because they know the concept of Folder and Files and they are used to it, and then we ask them to switch to something new that breaks their habits.
Raw document content
{{toc/}} = Problems = * **UC1**: Users don't always understand the Nested Pages concept. They are lose because they know the concept of Folder 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 needs a page that will be the container of some others (think about the "//Code//" space) 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 == {{gallery}} [[image:CreatePage.png]] [[image:FolderTemplate.png]] {{/gallery}}

Semantic Tags

Located in
Last modified by Vincent Massol on 2024/11/19
Rendered document content
Semantic Tags is a proposal to extend XWiki's default Tags using Zemanta content recommendation tool and Google search engine: tag documents with user-defined tags (default behavior in XWiki for tagging) tag documents with concepts from DBpedia: use Zemanta to recommend some tags for the wiki page content and Google search engine to suggest concepts from Wikipedia.
Raw document content
Semantic Tags is a proposal to extend XWiki's default Tags using [[Zemanta>>http://www.zemanta.com/]] content recommendation tool and Google search engine: * tag documents with user-defined tags (default behavior in XWiki for tagging) * tag documents with concepts from DBpedia: use Zemanta to recommend some tags for the wiki page content and Google search engine to suggest concepts from Wikipedia.

Nested Documents

Located in
Last modified by Vincent Massol on 2024/11/19
Rendered document content
It creates confusion! Idea: Concept of nodes a.k.a Nested Documents To fix these problems, we propose to introduce the notion of "nested documents", i.e. the ability to create documents inside documents.
In JCR[1], there is only one concept: the "node". A node can have a content, and a list of child nodes.
Future (implement the concept in the model) Finally, after these steps are accomplished in 7.2 and polished until the end of the 7.x cycle, we will refactor the XWiki model (something we dream about for years).
Raw document content
It creates confusion! = Idea: Concept of nodes a.k.a Nested Documents = To fix these problems, we propose to introduce the notion of "nested documents", i.e. the ability to create documents inside documents.
In JCR[1], there is only one concept: the "node". A node can have a content, and a list of child nodes.
=== Future (implement the concept in the model) === Finally, after these steps are accomplished in 7.2 and polished until the end of the 7.x cycle, we will refactor the XWiki model (something we dream about for years). == Problems with this idea == * Path enumeration as Unique ID: a lot of things get broken when a space (a document) in the hierarchy is renamed/moved

Usability Scenario #4

Located in
Last modified by Vincent Massol on 2024/11/19
Objects
mails : * [UX] Wiki - Space - Page concepts pitch http://markmail.org/thread/7y62ewmo2ltdeomq (Jul 31, 2014)

Publication Workflow - Extend Workflow Scope To Child Pages

Located in
Last modified by Vincent Massol on 2024/11/19
Rendered document content
Several types of links can exist between pages: Wiki link to a draft page (either in the same workflow or another one), or to a published page or a page that is not controlled by a workflow. concept covered by the concept of backlinks of XWiki platform Macro reference parameters, for instance in diagram or include macros . The referenced page can either be controlled by the same workflow or by a distinct one, or be published, or not under workflow. concept covered by the concept of backlinks of XWiki platform Links in large string properties of objects concept not covered by the concept of backlinks of XWiki platform DBList or Page objects concept not covered by the concept of backlinks of XWiki platform Links in diagrams concept not covered by the concept of backlinks of XWiki platform Wiki links update Implementation: A publish action can be seen as a combination of a copy and a rename.
Raw document content
Several types of links can exist between pages: * Wiki link to a draft page (either in the same workflow or another one), or to a published page or a page that is not controlled by a workflow. ** concept covered by the concept of backlinks of XWiki platform * Macro reference parameters, for instance in //diagram// or //include// macros . The referenced page can either be controlled by the same workflow or by a distinct one, or be published, or not under workflow. ** concept covered by the concept of backlinks of XWiki platform * Links in large string properties of objects ** concept **not** covered by the concept of backlinks of XWiki platform * DBList or Page objects ** concept **not** covered by the concept of backlinks of XWiki platform * Links in diagrams ** concept **not** covered by the concept of backlinks of XWiki platform Wiki links update Implementation: * A publish action can be seen as a combination of a copy and a rename.

Projects Graphics

Located in
Last modified by Vincent Massol on 2024/11/19
Rendered document content
Projects dependencies animation Preview Projects Relation Extensions Concept
Raw document content
{{velocity}} $xwiki.ssx.use("Improvements.WebHome") $xwiki.ssx.use("Standards.WebHome") {{/velocity}} == Projects dependencies animation == (% class="left column50" %) ((( {{html}} <a href="#cube">Animation</a> <div class="products" id="cube"> <div class="product platform"></div> <div class="text platform"></div> <div class="product enterprise"></div> <div class="text enterprise"></div> <div class="product manager"></div> <div class="text manager"></div> </div> {{/html}} ))) (% class="left column50" %) ((( **Preview** [[[[image:cube.png]]>>attach:cube.png]] ))) (% class="clearfloats"%) ((( ))) == Projects Relation == [[[[image:relation.png||width="100%" style='max-width: 1000px']]>>attach:relation.png]] (% class="clearfloats"%) ((( ))) == Extensions Concept == (% class="left column33" %) ((( [[[[image:extensionsNone.png||width="100%" style='max-width: 500px']]>>attach:extensionsNone.png]] ))) (% class="left column33" %) ((( [[[[image:extensionsPartial.png||width="100%" style='max-width: 500px']]>>attach:extensionsPartial.png]] ))) (% class="left column33" %) ((( [[[[image:extensionsFull.png||width="100%" style='max-width: 500px']]>>attach:extensionsFull.png]] ))) (% class="clearfloats"%) ((( )))
next page » Page 1 2 3 4 5 6 7 8
RSS feed for search on [concept]

Get Connected