Skip to content

Commit c357368

Browse files
authored
Merge pull request #362 from w3c/MH_Proposal1
Mh proposal1
2 parents a1b34ba + 85ca8b3 commit c357368

File tree

2 files changed

+12
-3
lines changed

2 files changed

+12
-3
lines changed

design-guide/o1p01-clear-purpose.html

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -52,6 +52,11 @@
How it Helps
5252
a video. They can tell by the video title that this video has the
5353
information they need.
5454
p>
55+
<p>
56+
For this pattern to be useful, each page must have a clear purpose. It works best when each page covers
57+
a single unifying topic. (See pattern <a href="#make-the-site-hierarchy-easy-to-understand-and-navigate-pattern">
58+
4.3.2 Make the Site Hierarchy Easy to Understand and Navigate a> for more details.)
59+
p>
5560
section>
5661
<section>
5762
<h5 class="coga-5">More Detailsh5>

design-guide/o2p02-site-structure.html

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -46,15 +46,19 @@
What to do
4646
main menu items under which they fall. It should be easy to know that
4747
sub-menu items are there and how to get to them. Users should guess
4848
correctly, the first time, where to find sub menu items.
49-
li>
50-
ul>
51-
<p>Make it easy to identify:p>
49+
Make it easy to identify:
5250
<ul>
5351
<li>the site organization,li>
5452
<li>the menu and content structure,li>
5553
<li>that there are sub-menus and,li>
5654
<li>if there are sub-menu items, how to reach them.li>
5755
ul>
56+
li>
57+
<li>
58+
Have each page or screen have a single purpose and a limited number of topics.
59+
Ideally a page or screen will have one main unifying topic.
60+
li>
61+
ul>
5862
section>
5963
<section>
6064
<h5 class="coga-5">How it Helpsh5>

0 commit comments

Comments
 (0)