docs: Add sections for Features, Getting Started, Guidance, and Resources in README#930
Open
Pavan-Microsoft wants to merge 1 commit intodev-v4from
Open
docs: Add sections for Features, Getting Started, Guidance, and Resources in README#930Pavan-Microsoft wants to merge 1 commit intodev-v4from
Pavan-Microsoft wants to merge 1 commit intodev-v4from
Conversation
Pavan-Microsoft
requested review from
Avijit-Microsoft,
Fr4nc3,
Prajwal-Microsoft,
Roopan-Microsoft,
Vinay-Microsoft,
aniaroramsft,
dgp10801,
marktayl1,
nchandhi and
toherman-msft
as code owners
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
This pull request updates the
README.mdto improve its structure and clarity by introducing new sections and reorganizing content. The changes make it easier for users to find information about features, deployment, guidance, and resources.Improvements to documentation structure:
## Featuressection to introduce and highlight the solution's key features, improving the discoverability of capabilities.## Getting Startedsection to provide a clear entry point for users beginning with the solution.## Guidancesection to group prerequisite and cost information, making it more accessible.## Resourcessection with a table summarizing product descriptions and links to pricing, helping users quickly reference relevant Azure services.Does this introduce a breaking change?