Add Visual Studio as an alternative to edit DNN Docs articles. Additionally…#793
Conversation
…d a bit more clarity on the repos; names and where they are located: local or remote (on Github). Thus flattening the learning curve.
|  | ||
| For more elaborate instructions on how to create a new branch in Visual Studio see https://learn.microsoft.com/en-us/visualstudio/version-control/git-create-branch?view=visualstudio. | ||
| 5. Make your edits | ||
| 6. & 7. & 8. Preview your work and files locally using the 'Git Changes' tab in Visual Studio. |
There was a problem hiding this comment.
Any reason why 6 & 7 & 8 here? If I understand correctly its is because 1-10 are different if using VisualStudio or not, but then 11 is common. If so maybe it should be broken down as I find that confusiong...
There was a problem hiding this comment.
The Prerequisites Steps and steps 11 and 12 are identical for Git and Visual Studio. The first 10 steps are conceptually the same, but in what to do (in Git versus Visual Studio) different. That apparently is not clear enough. I will split up Git and Visual Studio completely.
I'm quite new to Git. Shall I checkout the same branch the pull request is based on and push to it again?
There was a problem hiding this comment.
Yes you can push additional commits to this branch which will update this Pull Request
There was a problem hiding this comment.
@valadas: I've adjusted the text according to the above. Could you please review and when ok pull the request? Thx.
valadas
left a comment
There was a problem hiding this comment.
Nothing sticks out to me after verifying for the images renames.
…add a bit more clarity on the repos; names and where they are located: local or remote (on Github). Thus flattening the learning curve a bit.