<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>UX/UI Demo Documentation – Welcome to UX/UI Demo</title>
    <link>/en/docs/</link>
    <description>Recent content in Welcome to UX/UI Demo on UX/UI Demo Documentation</description>
    <generator>Hugo -- gohugo.io</generator>
    
	  <atom:link href="/en/docs/index.xml" rel="self" type="application/rss+xml" />
    
    
      
        
      
    
    
    <item>
      <title>Docs: General</title>
      <link>/en/docs/general/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/docs/general/</guid>
      <description>
        
        
        &lt;h2 id=&#34;header&#34;&gt;Header&lt;/h2&gt;
&lt;h3 id=&#34;user-profile---icon&#34;&gt;User profile - Icon&lt;/h3&gt;
&lt;p&gt;The user profile gives the user information about his logged in account und further functionalities.
It shows the picture of the user. If the user did not upload a foto of himself, a place-holder is shown.&lt;/p&gt;
&lt;p&gt;The user profile is placed on the top right corner. When the user klicks on the profile, a small menu pops up where he gets information about his account (name), his role, the functionality to log  out and his settings.
By clicking on his name, he gets to his profile settings page.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;navigation&#34;&gt;Navigation&lt;/h2&gt;
&lt;p&gt;A main navigation must be given, to provide that every user can easily access the whole content of the navigation.&lt;/p&gt;
&lt;h3 id=&#34;main-navigation&#34;&gt;Main Navigation&lt;/h3&gt;
&lt;p&gt;The Main Menu is placed vertically on the left side in the header and is symbolized as a Burger.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Normal State – Closed Menu:&lt;/strong&gt; The Menu shows only icons, which are clickable. There-fore, the user don’t have to click on the burger every time he wants to navigate.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Open Menu:&lt;/strong&gt; By clicking on the Burger, the menu expands to the right side, now Labels are visible. The user needs labelling, in case he does not know what the icons stand for.&lt;/p&gt;
&lt;h3 id=&#34;theming&#34;&gt;Theming&lt;/h3&gt;
&lt;p&gt;For the menu we used an additional colour swatch to style the menu individually.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;footer&#34;&gt;Footer&lt;/h2&gt;
&lt;h3 id=&#34;copyright&#34;&gt;Copyright&lt;/h3&gt;
&lt;p&gt;The Copyright aligns on the left side in the footer of the application.&lt;/p&gt;
&lt;h3 id=&#34;help&#34;&gt;Help&lt;/h3&gt;
&lt;p&gt;The help is available in an external documentation. The user can access it over the info icon, which is placed inside the footer, if help is needed. By clicking the icon, the user gets directly to the page-description he wants help for.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: Activity Arrangement</title>
      <link>/en/docs/technical-demos/arragement/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/docs/technical-demos/arragement/</guid>
      <description>
        
        
        &lt;p&gt;This function it is used, if a user finds that the sequence/order of the activities and courses is important therefore, she/he like to put them in the right sequence, in order to maximize the courses or activities output.&lt;/p&gt;
&lt;p&gt;The user is able to create, edit and delete certain categories and activities and to drag n drop them wherever he likes. The new order/sequence is automatically saved.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: Dashboard</title>
      <link>/en/docs/content/dashboard/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/docs/content/dashboard/</guid>
      <description>
        
        
        &lt;p&gt;On the dashboard, the user can access quick information of different topics through widgets.&lt;/p&gt;
&lt;p&gt;The User is able to change the position of his widgets per drag n drop and increase or decrease the height and width according to a grid which has per default three columns and infinite rows.
He can hide the widgets, if he does not need certain information or add new ones of a select-field.&lt;/p&gt;
&lt;p&gt;The user has to enable to edit-mode first, then he can personalize his dashboard.
The content of the widgets is strongly depending on role and purpose of an application.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: Navigation</title>
      <link>/en/docs/mobile/navigation/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/docs/mobile/navigation/</guid>
      <description>
        
        
        &lt;h3 id=&#34;main-navigation&#34;&gt;Main Navigation&lt;/h3&gt;
&lt;p&gt;The Main Navigation is shown as &lt;em&gt;bottom navigation&lt;/em&gt; with a maximum of 4-5 entries. If more than five entries are needed, the fifth entry-label changes to &lt;em&gt;More&lt;/em&gt;, additional entries are displayed in this overlay/pop up.
Active entries are coloured in the accent colour.&lt;/p&gt;
&lt;p&gt;This concept of navigation is only suitable for a normal (end-)user. For administration purposes another navigation concept is needed.&lt;/p&gt;
&lt;h3 id=&#34;drawer-menu-burger-menu--profile-icon&#34;&gt;Drawer Menu: Burger Menu / Profile Icon&lt;/h3&gt;
&lt;p&gt;If there is only the profile function and a logout, these functions are accessible over a profile icon in the header.&lt;/p&gt;
&lt;p&gt;If there are more entries, that are either technical or off-topic (not relevant for the main content of the application, example: support-page) the profile picture is displayed in the open drawer menu, and the icon gets replaced with a burger.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: Forms &amp; Fields</title>
      <link>/en/docs/technical-demos/form-elements/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/docs/technical-demos/form-elements/</guid>
      <description>
        
        
        &lt;p&gt;As a user I am offered a complex form. In this form I have to fill in various input fields. My entries are constantly validated and the save button remains without function until all entries have been made correctly. All data is clearly arranged and provided with a label.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Certain rules a form has to follow:&lt;/strong&gt;&lt;/p&gt;
&lt;h4 id=&#34;validation&#34;&gt;Validation&lt;/h4&gt;
&lt;p&gt;Relevant fields have to be validated immediately.&lt;/p&gt;
&lt;h4 id=&#34;field-length&#34;&gt;Field-length&lt;/h4&gt;
&lt;p&gt;The length of a field depends on the input&lt;/p&gt;
&lt;h4 id=&#34;position&#34;&gt;Position&lt;/h4&gt;
&lt;p&gt;All fields are aligned underneath each other in one column&lt;/p&gt;
&lt;h4 id=&#34;labels&#34;&gt;Labels&lt;/h4&gt;
&lt;p&gt;A label should be displayed above its field&lt;/p&gt;
&lt;h4 id=&#34;letters--numbers&#34;&gt;Letters &amp;amp; Numbers&lt;/h4&gt;
&lt;p&gt;Certain fields should only allow letters and numbers if needed. (for ex-ample, phone number)&lt;/p&gt;
&lt;h4 id=&#34;related-information-should-be-grouped-together&#34;&gt;Related Information should be grouped together&lt;/h4&gt;
&lt;p&gt;If a formular gets too long, it should be separated into more pages with steps.&lt;/p&gt;
&lt;h4 id=&#34;required-fields&#34;&gt;Required Fields&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Required Fields are marked with *&lt;/li&gt;
&lt;li&gt;If all fields are required, the * should not be visible&lt;/li&gt;
&lt;li&gt;If there are more required fields than optional fields, the optional fields should be required instead with the (optional) tag&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: Profile Page</title>
      <link>/en/docs/content/profile-page/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/docs/content/profile-page/</guid>
      <description>
        
        
        &lt;p&gt;On the profile Page, the user can make changes about his account.
The content of the profile settings page should always be grouped into related data fields and options.&lt;br&gt;
Therefore, in this demo the content is structured into three groups/sections:&lt;/p&gt;
&lt;h3 id=&#34;personal-details&#34;&gt;Personal Details&lt;/h3&gt;
&lt;p&gt;In this section, the user is able to change his first- and last name and his date of birth.&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th style=&#34;text-align:left&#34;&gt;Field name&lt;/th&gt;
&lt;th style=&#34;text-align:left&#34;&gt;Type&lt;/th&gt;
&lt;th style=&#34;text-align:left&#34;&gt;allowed characters&lt;/th&gt;
&lt;th style=&#34;text-align:left&#34;&gt;Limitation&lt;/th&gt;
&lt;th style=&#34;text-align:left&#34;&gt;additional info&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style=&#34;text-align:left&#34;&gt;First name&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;text box&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;alphabetic&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;-&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;-&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&#34;text-align:left&#34;&gt;Last name&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;text box&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;alphabetic&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;-&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;-&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&#34;text-align:left&#34;&gt;Date of birth&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;select box&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;numeric&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;-&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;by clicking on the calendar-icon a calendar pops up and the user is able to select a date&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h4 id=&#34;profile-picture&#34;&gt;Profile Picture&lt;/h4&gt;
&lt;p&gt;The user is able to upload a photo and is able to delete it.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&#34;contact-details&#34;&gt;Contact Details&lt;/h3&gt;
&lt;p&gt;This section gives information about contact details like address and electronic ways of communication.&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th style=&#34;text-align:left&#34;&gt;Field name&lt;/th&gt;
&lt;th style=&#34;text-align:left&#34;&gt;Type&lt;/th&gt;
&lt;th style=&#34;text-align:left&#34;&gt;allowed characters&lt;/th&gt;
&lt;th style=&#34;text-align:left&#34;&gt;Limitation&lt;/th&gt;
&lt;th style=&#34;text-align:left&#34;&gt;additional info&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style=&#34;text-align:left&#34;&gt;Address&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;text box&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;alphanumeric&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;-&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;-&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&#34;text-align:left&#34;&gt;Postal&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;text box&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;alphanumeric&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;-&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;-&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&#34;text-align:left&#34;&gt;City&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;text box&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;numeric&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;-&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;-&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&#34;text-align:left&#34;&gt;Country&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;select box&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;alphabetic&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;-&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;-&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&#34;text-align:left&#34;&gt;E-Mail&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;text box&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;alphanumeric&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;-&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;instant validation&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&#34;text-align:left&#34;&gt;Phone&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;text box&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;numeric&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;-&lt;/td&gt;
&lt;td style=&#34;text-align:left&#34;&gt;prefilled with correct format, related to country&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&#34;advanced-settings&#34;&gt;Advanced Settings&lt;/h3&gt;
&lt;p&gt;In this section, the user is able to make changes which affect the application, for example its appearance.&lt;/p&gt;
&lt;h4 id=&#34;changable-theme&#34;&gt;Changable Theme&lt;/h4&gt;
&lt;p&gt;The user is able to switch the theme for example from light to dark.&lt;/p&gt;
&lt;h4 id=&#34;language-switch&#34;&gt;Language Switch&lt;/h4&gt;
&lt;p&gt;The language-switch is shown as a Drop-Down-Field, all languages available are written in their language and use its own characters.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: User Information</title>
      <link>/en/docs/mobile/user-information/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/docs/mobile/user-information/</guid>
      <description>
        
        
        &lt;p&gt;In the mobile view, the user profile menu is placed on the upper right corner in the header. By tapping on his profile picture, the menu expands over the whole height of the application and shows the same entries as the web version.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: Tables</title>
      <link>/en/docs/content/tables/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/docs/content/tables/</guid>
      <description>
        
        
        &lt;p&gt;The Data grid is an opportunity for administrators to have an overview of all available learning media. Administrators want to be able to sort them in a table (by clicking on the column&amp;rsquo;s header) and additionally, they want to be able to search for specific names and values.&lt;/p&gt;
&lt;p&gt;The table should be adjustable according to users needs. Information about the total amount must be available. Additionally, the user must be able to set the number of records on screen and users must be able to scroll the table page by page.&lt;/p&gt;
&lt;p&gt;The course list here is just one example for tables with large amounts of data. It can be also users, groups etc.&lt;/p&gt;
&lt;h3 id=&#34;actions&#34;&gt;Actions&lt;/h3&gt;
&lt;p&gt;A maximum of three actions are shown. If there are more than three, the actions are hidden inside a menu, it is accessible over three dots.&lt;/p&gt;
&lt;h3 id=&#34;multi-selection&#34;&gt;Multi-selection&lt;/h3&gt;
&lt;p&gt;The user/administrator is able to select multiple entries of a table.&lt;/p&gt;
&lt;p&gt;By selecting one or more entries a small section fades in, which is fixed to the bottom of the display. It shows the amount of selected items and all operations that are possible with multiple records.  The user is able to deselect his selection by clicking on the checked icon.&lt;/p&gt;

      </description>
    </item>
    
  </channel>
</rss>
