Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Menu behavior in multi-version sites

See original GitHub issue

Using the default template and creating a versioned page, the main TOC links to articles from the standard version

Observed behavior

on any versioned page (/v1.0/index.html) the headers point to the standard version (/articles etc.) instead of the versioned articles (/v1.0/articles/)

Files

partial project.json


    "content": [
      {
        "files": [
          "*.md",
          "toc.yml",
          "docs/**.md",
          "docs/**/toc.yml"
        ],
        "src": "../revisions/head/docs/",
        "dest": ""
      },
      {
        "files": [
          "api/**.yml",
          "api/**.json",
          "api/index.md"
        ],
        "src": "../revisions/head/docs/",
        "dest": ""
      },
      {
        "files": [
          "docs/**.md",
          "docs/**/toc.yml"
        ],
        "src": "../revisions/v1.0/docs/",
        "dest": "v1.0",
        "version":"v1.0"
      },
      {
        "files": [
          "api/**.yml",
          "api/**.json",
          "api/index.md"
        ],
        "src": "../revisions/v1.0/docs/",
        "dest": "v1.0",
        "version":"v1.0"
      }
    ],

partial main toc.yml

- name: Documentation
  href: docs/UserDocs/
- name: Operations
  href: docs/OperationsDocs/
- name: Developers
  href: docs/DevDocs/

Expected result

The TOC in the header should always link to the articles of the active version!

And finally: Thanks to everybody involved (as far as I can tell - @superyyrrzz) for providing multi-version support

Issue Analytics

State:
Created 7 years ago
Comments:11 (5 by maintainers)

Top GitHub Comments

1reaction

superyyrrzzcommented, Dec 5, 2016

I create a test repo. From docfx.json, you can find v2.0 uses its own toc as nav toc, while v2.1 use the default one.

1reaction

superyyrrzzcommented, Nov 7, 2016

Great! Your practical using experience is helpful to us. PR is welcomed.

This still need to be implemented, then you can specify it in docfx.json like:

      {
        "files": [
          "api/**.yml",
          "api/**.json",
          "api/index.md"
        ],
        "src": "../revisions/v1.0/docs/",
        "dest": "v1.0",
        "navRoot": "v1.0",
        "version":"v1.0"
      }

Top Results From Across the Web

Can't remove extra data prior to uninstalling the module

1d PHP/7.3.9. We have multiversion (1.0.0-beta33) installed. Problem/Motivation. To uninstall the module, the extra data related to ...

Does Multiversion module need content migration if enabled on ...

I have Drupal 8 setup with lot of content in it. When I enable Multiversion module all the content gets disappeared. Do I...

Multi version pricing - Iterative Path - WordPress.com

Menu Costs – Maintaining all those SKUs; Customer Costs – Incurred by your customer. This is what it takes for your customers to...

Umitation: Retargeting UI Behavior Examples for Website ...

In this example, these four components corre- spond to a mouse click (trigger), the menu button (trigger object), the dropdown list's fade-in ( ......

Responsive Web Design: 50 Examples and Best Practices

Beautiful example of websites that use responsive web design. Being fully adaptive doesn't mean solely being mobile and tablet friendly.