- Advanced Topics
- Documentation Effort
- Unified Documentation
- Use Cases
- b2evolution Vision / Main Use Cases
b2evolution Vision / Main Use Cases
''It is assumed that readers have a general knowledge of the World Wide Web.''
These are very '''high level''' use cases. Detailed [[Use_Case|use cases]] are linked underneath (when available).
'''Motivation''': publishing news/information easily and efficiently on a website
'''Candidate reference solution: '''Movable Type, pMachine
The SiteAdmin (who is also a Blogger here) sets up a Blog or Weblog on a website. Whenever some information/thoughts come up, he writes a Post and assigns it a Category as well as an Issue Date. When the Issue Date arrives, the Post is automatically published on the Blog or Weblog.
Typically, when Site Visitor access the Blog, they see the last 10 or 15 posts, displayed by date, last Post first. However, SiteVisitors also have the option to browse daily, weekly or MonthlyArchives. SiteVisitors can also display the posts by Category.
''This is the most basic use case. This is where the original ""Cafelog/b2"" left off. This is also what dozens of other free blogtools do.''
Multilingual blog tool
'''Motivation''': Extension of Blog Tool allowing to publish news/information in multiple languages and have multiple translations of same information linked to each other
'''Candidate reference solution''': None
Multiuser blog engine
'''Candidate reference solution''': ?
Hierarchic Content Management System
'''Motivation''': Display a large amount of information in an organized format. Allow multiple authors to efficiently build a Knowledge Base.
'''Candidate reference solution''': CMS tools, Wiki tools.
''Not implemented yet''
The SiteAdmin sets up a Book on the website.
Each Book contains one or more Chapters. Chapters may contain Sub Chapters.
Authors write Articles which are placed in Chapters.
Articles also have one or more Categories. Chapters are not the same as Categories. A Category describes the Article's nature, while the Chapter determines its placement in the Book. An Article may have multiple Categories, but will only be contained in a single Chapter or Sub Chapter.
A User Account may choose to display Articles in a variety of different ways:
1. A table of contents, displaying links to all of all the Chapters and Sub Chapters and Articles, organized heirarchically.
2. A list of all Articles in the Book or all of the articles in a single Chapter.
3. One Article with links to the next and previous Article.
4. All of the Articles in one or more Categories.
For example, building a knowledge base for a software company, there may be a Book for each product the company creates, with Chapters and Sub Chapters for each feature in the product. Articles could contain step-by-step information for end-users, frequently asked questions about the feature, and/or known problems. There may be a Categories for "How-To", "FAQ", "Technical Info", and "Known Issues".
Tracker / To do list management
'''Motivation''': Ensuring that all bugs/feature-requests are known and get processed at the appropriate time
'''Candidate reference solution''': Bugzilla, Flyspray, Tasks (http://www.alexking.org/index.php?content=software/tasks/content.php&show=1)
The SiteAdmin sets up a Tracker. Whenever a bug is discovered or a feature request comes up, Collection Members create an Item describing it. They classify the Item using a variety of parameters. SiteVisitors have the option to display the Items according to a variety of parameters.
''Not implemented yet''
'''Candidate reference solution''':phpBB
Created by • Last edit by on Sep 28, 2013
Form is loading...