#218 Information flow- Easier flow- 3 click rule
Opened by advika. Modified
fedora-docs/ advika/docs-fp-o prod  into  master

Download 218.patch

Kindly find the new Information Architecture in the link below
https://miro.com/app/board/o9J_lkoizq8=/?moveToWidget=3458764523605038111&cot=14
This is the new Information Architecture in accordance to the prototype :-
https://www.figma.com/proto/kH4psWpG6uG9Wx4ww8vN20/Untitled?page-id=0%3A1&node-id=7%3A220&viewport=241%2C48%2C0.12&scaling=scale-down&starting-point-node-id=2%3A121

Clicks: Indicates the number of steps required to reach the page. It also includes the clicking the final heading, i.e. , opening of the final page of the respective heading.

The 3-click rule is a persistent, unofficial heuristic that says that no page should take more than 3 clicks (or taps on a touchscreen) to access. A variation pronounces that the most important information should take no more than 3 clicks to get to. This is a rule, taken seriously while designing UIs . Hence, I have tried to create the whole navigation within the 3 click rule , i.e., it means that I have made sure, that the important information is available to the users within 3 clicks. This indicates that the users will take less time to reach the destination they want and it increases usability by making the navigation easier while keeping a structural hierarchy, keeping the front page clean and letting the users absorb the information in steps. While certain terminologies need to be changed and it is a work in progress, for now I feel that this architecture promises easy navigation. I am trying to collects users also, to test this navigation out.

I have also divided the heading into three main components :-
1. Header :- Incudes search bar, and contribute
2. Main page :- Includes introduction ,user documentation and community
3. Footer :- Includes Archives, get involved, and guidelines.

Like I said before, it is a work in progress , and I would like to test this out also, hence feedback is appreciated .

There are some inaccuracies in your information architecture

  • Server and IoT are Editions
  • None of the things you have listed in Editions are actually Editions (although Fedora CoreOS is an "emerging Edition")
  • Get Involved needs to include more than Outreachy and GSoC (maybe you intended that and those are just there as examples)
  • How is Diversity & Inclusion 1 click and Council is 2 clicks? It seems like they should be the same
  • I don't think burying the teams under an additional level of clicks is necessary. What's the reasoning behind that decision?

You may want to review the explanation of some key terms and concepts I posted in Discussion recently.

Metadata