How to create a page to custom display of particular node type and add it to node context menu?

Question

• I created custom node type, let's say "My Node".
• I created custom node display type (at /admin/structure/display-modes/view), let's say "Specialized Display".
• Configured the "Specialized Display" for "My Node" - configured some fields, their order, etc.
• How can I create a page on path "node/*/specialized-display" for "My Node" nodes using "Specialized Display"? (I.e. reject "node/123/specialized-display" if "node/123" is not "My Node", but e.g. "story".)
• How can I make a tab appear in node context menu (the one which contains "View", "Edit", "Delete" tabs)?
• Bonus question: how can I make URL automatic alias(es) "[alias of node/%]/specialized-display"?

What I tried

Created view page, path "node/%/specialized-display", use contextual filter (to reject different node types, use argument for node selection and to alter page title).

Problems:

• Couldn't find out how to add it to the node context menu.
• It creates redundant node title on the page (one for whole page and one for item in view). Couldn't find out how to remove it, but it's not that big problem, I'll remove is using CSS (although accessibility is going to be damaged).

My system: Drupal version: 8.8.3

Answer 1

First question: First you are going to want to set your views path to: node/%node/specialized-display. Then, in the contextual filter, under "WHEN THE FILTER VALUE IS AVAILABLE OR A DEFAULT IS PROVIDED" check off: Specify validation criteria. Finally, select "Content" from the dropdown and select your node type.

Second Question: This guide explains how to add contextual links, all you are going to need a basic custom module with a routing.yml file. You can set the route to the view. Hint, Drupal console's drupal debug:router is a great way to find the route to your view. https://www.drupal.org/docs/8/api/menu-api/providing-module-defined-contextual-links#s-rendering-contextual-links

Third question: I've had my best luck with the sub-pathauto module to make the aliased routes. https://www.drupal.org/project/subpathauto

Thoughts... I am using this setup on two sites so far and this works pretty well. Sub-Pathauto seems to behave fairly well. I do have one tip though, when initially building my views, I disable it, so that I can ensure everything works before I add the extra layer.

Other thoughts... This could be done through traditional custom views processing. If you have a big site, it may be the way to go. I haven't tested Sub-Pathauto at large scale, this is currently something I am experimenting with.