Parse & figure out what to do with tabbed content

Open
#8 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go, markdown
Domain
tooling

Research direction

Start by locating the parser entry point that handles tabbed content and review how the example Azure documentation is represented. Determine how an OS choice should be requested and how test mode should default to Linux; done means Windows and Linux commands no longer run unintentionally together.

Written by the indexing model from the issue text.

Description

We have a lot of content which repeats the same command for a windows and Linux deployment. This will cause unintended behavior as typically a user doesn't want to deploy both Windows and Linux.

Could create a break in the content which asks users which OS they would like to execute and if the test mode is run it defaults to Linux.

Example document - https://learn.microsoft.com/en-us/azure/app-service/quickstart-nodejs?tabs=linux&pivots=development-environment-cli

Dominant language
Go
Stars
40
Forks
27
Avg merge
2d 20h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/InnovationEngine

All issues in Azure/InnovationEngine

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.