[wp-trac] [WordPress Trac] #30022: Twenty Fifteen: display a default menu when no custom menu was created

[WordPress Trac]

#30022: Twenty Fifteen: display a default menu when no custom menu was created
---------------------------+------------------------------
 Reporter:  jeherve        |       Owner:
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Bundled Theme  |     Version:  trunk
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:
---------------------------+------------------------------

Comment (by iamtakashi):

 Replying to [comment:3 jeherve]:
 > I would argue that a blog often has at least a couple of pages : About,
 and Contact. These 2 pages make sense on a blog imo, and "About" is there
 by default on every new WordPress site.

 We only can speculate whether a blog owner wants to have a page or not,
 but my point is that a theme shouldn't force them to have one when they
 don't want to. Nor leading them to have a hacky solution with empty html
 tags.

 > I like the fallback because it also shows what the theme can do. Without
 it, new bloggers may wonder how they can add a list of pages to their
 sidebar, and may end up using the Pages widget, which doesn't look as good
 as a menu.

 Educating users remains as our challenge but we need to keep doing that so
 that they use the right tools for the purpose the tools are designed for.
 Instead of forcing some users to have something when they don't want to.
 We can totally add a custom menu instruction to readme.txt.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/30022#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform