Difference between revisions of "Basic structure of this wiki"

From ZUGSEIL Wiki
Jump to navigation Jump to search
Line 27: Line 27:


The information should be not from the technical view but rather from the business and user perspective so that a person reading this page understands which value can be generated from our software to his processes.
The information should be not from the technical view but rather from the business and user perspective so that a person reading this page understands which value can be generated from our software to his processes.
Examples for Business Process Pages are:
* Assisted Ordering for a team member
* Laundy Bring-In at a Laundry-Shop


== User Journey Pages ==
== User Journey Pages ==

Revision as of 10:51, 28 May 2022

Basic ZUGSEIL wiki structure

The Start/Main Page presents the user an overview of all content and refers to the product pages. From there the user can navigate to various General Pages (like this one) which provide information on ZUGSEIL or the ZUGSEIL products.

Product Pages

Each product offered by ZUGSEIL has its own Product Page, which is category page of all bop service bundles offered by ZUGSEIL as part of the product described in this page. In the content section of the category page, more information on the product is provided:

  • a description of the product
  • the target audiences of the product
  • a list of all sales features each linking to a sales feature page. “sales” means that only features are listed here worth mentioning to the customer. If a user of the wiki wants to find a full overview on what services are part of the product, he has to browse over the service bundle pages with their contained services.

Feature Pages

Each feature enabled by a product has its own Sales Feature Page. It is a category page of all user journeys enabled by this feature. Each of these sales feature pages contain:

  • a brief general description
  • a business value description for the customer ("What value does it deliver for me?")
  • a list of all business processes enabled by this feature. Each of these are each linking to its own business process page.

Business Process Pages

Each business process enabled by a feature has its own Business Process Page. It contains information on:

  • a reference workflow of this business process. This description should be linked to User Journey Pages to enable the user how the coverage of this business process will look alike when he is using our software.
  • a description of each step of the entire process. This description should be linked to User Help Pages, where individual pages are explained.
  • possible variations of the process

The information should be not from the technical view but rather from the business and user perspective so that a person reading this page understands which value can be generated from our software to his processes.

Examples for Business Process Pages are:

  • Assisted Ordering for a team member
  • Laundy Bring-In at a Laundry-Shop

User Journey Pages

Each task the user wants to complete requires a specific user journey. The name of a User Journey Page typically starts with "How to ...". Each user journey page also is a category page, to which all Service Help Pages are linked which the user needs to visit, operate or use during the described user journey.

A User Journey Page contains these information:

  • Exact description of the task to be demostrated by this user journey
  • Step-by-step explanation of what to do (click through-explanation or even video)

Examples for User Journey Pages are:

  • How to create a new product
  • How to get a quick overview of my orders

Depending on what task user wants to achieve with our software there exists a specific user journey page, which explains the user how to get his task done. Depending on the task of the user, the rederencing user journeys can eventually span over multiple services and multiple business processes.

Service Help Page

Service Bundle Pages


Service Pages

This page has three main sections:

  • A header section, marked by <nowiki bop="basicServiceInfo"/>. It contains generic information like service-type, Service-veservice-description,
  • The first section holds information on what the user can achieve with it. This part is Also it holds the configuration options and an explanation of these
  • The configuration section
  • The release history section
  • The compatibility section, which is autogenerated

Available types are:

  • App - Full window applications
  • Dashboard widget - Apps which can be placed
  • Configration options




User Help Pages