1
votes

I have been tasked with documenting how we are going to use Azure DevOps. This is something new to our team.

I am working on a wiki for the vaious How Tos, guides, standards, etc.

I want to force users to read pages in a certain order. But I don't necessarily want them to go directly to a page in the tree.

Here is my structure

enter image description here

So for Repos, if the reader needs to migrate an existing git repo to Azure DevOps, I want to the read

  1. Create a New DevOps Repo
  2. Change Local Repositories to Azure DevOps
  3. Push Existing Git Repository to Azure DevOps

But I don't want those pages visible in the tree. I will have another page with links to these pages.

Is this even possible? My research has yielded little in the way of help.

2

2 Answers

0
votes

In brief I'd say no. You can't do all you've outlined using Azure DevOps Wiki. I believe I heard these needs:

  1. Hide pages from an Azure DevOps Wiki. Yes. We could do this a number of ways, e.g., clone the underlying Git repository and work/edit locally until you are ready to share it. Not really what you are looking for. You could also futz with permissions but, again, not really what you're looking for.
  2. Force users to read pages in a specific order. No. I don't believe this can be done. It's contrary to Wiki.
  3. Dynamically hide and later dynamically show a page(s) in the right-hand menu. No. I don't believe this can be done. It's contrary to Wiki.

Azure DevOps Wiki could be made to meet some of these needs but I know of no way to stitch them together as you've outlined.

It sounds like you want to create a tightly orchestrated computer-based-training course (CBT). Wiki isn't the right tool for that. Wiki is more about open, loosely-structured, collaborative knowledge sharing.