[wp-trac] [WordPress Trac] #37974: Add multi-panel feature to pages through add_theme_support
WordPress Trac
noreply at wordpress.org
Thu Oct 13 00:47:12 UTC 2016
#37974: Add multi-panel feature to pages through add_theme_support
-----------------------------------------+------------------
Reporter: karmatosed | Owner:
Type: task (blessed) | Status: new
Priority: normal | Milestone: 4.7
Component: Themes | Version:
Severity: normal | Resolution:
Keywords: has-ux-feedback needs-patch | Focuses: ui
-----------------------------------------+------------------
Comment (by folletto):
> My primary concern about this is duplicate content on the site, which
search engines tend to frown upon. Much like we redirect when slugs are
renamed, it seems like the correct behaviour is to redirect to a
"canonical" source.
As far as I know, `rel=canonical` alone is one of the ways to deal with
that as an alternative when the page can't redirect (think of parametrized
pages where query parameters can shuffle for the same results).
I'm not even sure that a page that pulls partial content from other pages
is considered duplication. I'm sure duplication acts when the same page is
replicated (see the examples [https://moz.com/learn/seo/duplicate-content
here]), I'm less sure when a piece of it is present across multiple pages,
otherwise... sidebars and footers wouldn't be duplicated content as well
no?
Keeping the page, would allow theme authors to have simple setups where a
page can show title and excerpt in home, and then link to the same page.
The flexibility WordPress navigation already have take care of other
options (such as not linking a page anywhere if they authors don't want it
linked. WordPress already provides many pages that aren't "linked" often,
like the archive pages, wouldn't be a new thing). And maybe even users
would be surprised the page used in the homepage now disappeared entirely?
How do we clarify that behaviour?
> But if a section of the front page is removed from the front page
(remaining as a standalone page), the link from the menu will
automatically direct to the standalone page, instead of the front page.
This automation seems a bit of an edge case to me: a menu that leads
somewhere else is likely very distinct, both design and code wise, from an
in-page menu.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/37974#comment:129>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list