Unreachable page "Managed Plugin System"

[icecrime]

I don't quite understand how to reach this page without typing the URL directly.

From the navigation menu, when I click "Extend Engine" is just collapse/expands the submenu, but doesn't get me to that page.

[mdlinville]

@johndmulhausen I looked in _data/toc.yaml and the engine/extend/ endpoint is not there, though its "children" are. Can we actually give the Extend section a "landing page" or do we just need to add it after line 254?

[johndmulhausen]

@mstanleyjones Just add it after line 254. BTW I noticed and fixed some formatting issues on that page.

[danix800]

Actually the TOC is not well synced with content, not only links, but title text too. Is it written intentionally like that? For example:

• /engine/userguide/networking/get-started-macvlan/ is not in TOC.
• /engine/admin/formatting/, TOC title "Format command and log output", content title "Formatting reference"

[johndmulhausen]

Drift between the TOC and the page titles is okay as long as they're saying
the same thing. Things not showing up in the TOC? That is a bug, unless the
page has publish: false specified in the front-matter

On Tue, Oct 18, 2016 at 7:26 PM, Ding Fei [email protected] wrote:

Actually the TOC is not well synced with content, not only links, but
title text too. Is it written intentionally like that? One example:

• /engine/userguide/networking/get-started-macvlan/ is not in TOC.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#252 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFMAf2GH1jgV-mAiImA7sq_vrXb_VPVcks5q1X_WgaJpZM4KZ_OE
.

---

John Mulhausen
Lead Technical Writer, Docker
[email protected] | GitHub/Docker ID: @johndmulhausen

[mdlinville]

+1 that the TOC title and page title should not be required to be the same, because the TOC is usually in a narrower div and it's standard practice to have an abbreviated title there. I'll do a new PR to add the other page to the TOC.

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked