New User Journey

User's Journey[edit | edit source]

The main idea is to have a github structure like, where every user can write on his own page what he wants. When the users has some material that he wants share on the course and department pages, he can ask a wikitolearn's tutor or admin to publish his content. This will help new user not to worry about making mistakes, deleting pages. A newbie will get familiar with the way WikiToLearn (and more generally mediawiki) works.

The work is tracked down on phabricator. You can see the tasks here:

New User's Journey

The keywords in this workflow are Username, Sections and Chapters. The uri will have a hierarchical structure like


I will try to analyze a simple user journey, from the creation of the user to the publishing of his sections. For simplicity I will divide the workflow into separated phases:

New User[edit | edit source]

When a user signs up he will receive a welcome message on his own page. This welcome message should contain some text regarding how he can start writing on his page and where to ask for help.

New section.png

He will have a list of sections which he can modifies. An important aspect is that the user can immediately create a new section without leaving his own page.

New/Edit Section[edit | edit source]

When the user creates a new Section a subpage with name of the section will be created. This means that if my username is Grigoletti and I want to to create a section called Black body radiation the url will be:


In that page, there will be an editor, similar to the one used with the Book creator, where the Grigoletti can add, remove or rename the chapters of the "black body radiation" section. A point ot be discussed is that this kind of section editor may not be necessary if visual editor will be implemented and correctly working.

Also, another important aspect is the role of the publish button. What it does is to to be defined. It can add a category to that page (for example Category: Page to be published), so that WikiToLearn administrators and tutors can check that section and see if everything is fine. Another suggestion could be that before adding a category to the page, the publish button calls the pdf renderer and see if it compiles. Based on the results it will send the page to a different category (if it renders correctly it can go to Category: To be published and if it fails to Broken pdf to be published).

New chapter.png

New/Edit Chapter[edit | edit source]

When the user chose to create or edit a new chapter a subpage of the section will be created. From the above example, if Grigoletti wants to write a chapter about Rayleigh Jeans Law under the Black body radiation he will have a uri:


Here the writing of the content will be as usual, using the templates needed and writing whatever he wants.

Edit chapter.png

Pros/Cons[edit | edit source]

This part has to be carefully evaluated and discussed.


  • User will have everything organized under his own page
  • User can start writing without worrying about making mistakes on the official and public course pages
  • It's easy to check if a page is ready to be published


  • This can lead to a fragmentation. User will start writing on its own page something that perhaps already exists but written in a different way. This will be a problem because user are not encouraged to improve already existing material.
  • A little bit difficult to implement the section editor and a good layout. This is not impossible but will require some time.