Restructured the layout of the current documentation

[Roseline-Bassey]

This PR is an implementation of the proposed docs structure #306 for the Notary Project.

The documentation layout has been restructured in this order :

Project overview
Contributing.md
Notation >

• Quick-start guides.md
• Installation guides
• Tutorials
• How-to-guides
• Concepts ( this only contains the Notation directory structure for system configuration now)
• CLI Reference
• Glossary.md ( some terminologies which I will define in my later PR have been added here)

Troubleshooting

Developer documentation (Securely develop plugins for Notation, Securely deploying Notation, Experimental features, and Notary project specifications and requirements have been moved to developer docs)

FAQ

[netlify]

✅ Deploy Preview for notarydev ready!

Name	Link
🔨 Latest commit	12f160b
🔍 Latest deploy log	https://app.netlify.com/sites/notarydev/deploys/64ff6e831bbd520008770d97
😎 Deploy Preview	https://deploy-preview-312--notarydev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[zr-msft]

@Roseline-Bassey

Thank you for making this PR.

Overall i'm fine with the changes for now, but there a couple changes:

• Create content/en/docs/notation/developer
• Move experimental-features.md, secure-deployment.md, and secure-plugin-development.md under content/en/docs/notation/developer
• Rename content/en/docs/developer-docs -> content/en/docs/developer

There are some other minor things i'm considering if we should change or not, but I can send a follow up PR after this is merged if needed.

[zr-msft]

fixes #306

[Roseline-Bassey]

Hi, @zr-msft, thanks for the comment. I have updated the PR to incorporate your suggestions. Please kindly review.

[zr-msft]

Nice work. LGTM

[Roseline-Bassey]

Thank you, @zr-msft

[FeynmanZhou]

PTAL

[zr-msft]

@Roseline-Bassey you'll need to rebase your branch for this PR and resolve any conflicts before we can merge this

[Roseline-Bassey]

Hi, @zr-msft
I have rebased and force-pushed to my branch. On my local Git, the rebase output shows that it "Successfully rebased and updated refs/heads/refactoring-docs-branch." There was no conflict on my local git after rebasing and before submitting the pull request but on this PR page GitHub says: 'This branch has conflicts that must be resolved" I am wondering if I pushed the PR wrongly and what can I do to resolve the conflict.

[zr-msft]

Hi, @zr-msft I have rebased and force-pushed to my branch. On my local Git, the rebase output shows that it "Successfully rebased and updated refs/heads/refactoring-docs-branch." There was no conflict on my local git after rebasing and before submitting the pull request but on this PR page GitHub says: 'This branch has conflicts that must be resolved" I am wondering if I pushed the PR wrongly and what can I do to resolve the conflict.

did you fetch the latest from upstream?

git fetch upstream
git rebase upstream/main

[Roseline-Bassey]

On the main branch, I executed
git fetch upstream

Then on my branch, I executed:
git rebase main

[zr-msft]

On the main branch, I executed git fetch upstream

Then on my branch, I executed: git rebase main

you need to run git rebase upstream/main on your branch. You ran the equivalent of git rebase origin/main

[FeynmanZhou]

PTAL

[FeynmanZhou]

Hi @Roseline-Bassey , the updated version looks good to me. Thanks for your patience. Could you ps resolve the conflict?

[FeynmanZhou]

@zr-msft @Roseline-Bassey I feel this article could be moved to the chapter "User guides" since only Notation users may take care of this configuration. What's your opinion?

[Roseline-Bassey]

Yes, I agree. The article can be included in the how-to guides under the User Guides. @FeynmanZhou

[FeynmanZhou]

LGTM

[zr-msft]

LGTM