Changes in e2ca466: Updated Forking resources in github (markdown)

				Guides/Developers/Forking-resources-in-github.md
			
          @@ -8,4 +8,8 @@ The resources repository is where the HTML, CSS, and Javascript reside within th

           ##How to fork

          -To fork the resources repository, you will need a github account. This can be obtained through your organization or personally and is a straightforward process. Once you have a github account, visit our [[resources repository page|https://github.com/izenda/resources]]. There will be a button at the top of the page that says "Fork". Click this and the repository will be added to your personal repositories. You can now make edits to the resources in your repository without worrying whether you're going to break functionality. Now whenever you update your Izenda.AdHoc.dll to the latest version, instead of copying the Resources from the zipped archive, you will go to your github interface tool (usually a command line, but GUIs are available) and fetch the upstream repository. If there are any conflicts when fetching, you can resolve these using a merge tool. Ideally, there will be no conflicts and your resources will be updated with both your changes and any changes made by us in development. This will allow you to stay current and prevent you from losing any of your own work.

          \ No newline at end of file

          +To fork the resources repository, you will need a github account. This can be obtained through your organization or personally and is a straightforward process. Once you have a github account, visit our [[resources repository page|https://github.com/izenda/resources]]. There will be a button at the top of the page that says "Fork". Click this and the repository will be added to your personal repositories. 

          +

          +![]()

          +

          +You can now make edits to the resources in your repository without worrying whether you're going to break functionality. Now whenever you update your Izenda.AdHoc.dll to the latest version, instead of copying the Resources from the zipped archive, you will go to your github interface tool (usually a command line, but GUIs are available) and fetch the upstream repository. If there are any conflicts when fetching, you can resolve these using a merge tool. Ideally, there will be no conflicts and your resources will be updated with both your changes and any changes made by us in development. This will allow you to stay current and prevent you from losing any of your own work.

          \ No newline at end of file

...	...	@@ -8,4 +8,8 @@ The resources repository is where the HTML, CSS, and Javascript reside within th
8	8
9	9	##How to fork
10	10
11		-To fork the resources repository, you will need a github account. This can be obtained through your organization or personally and is a straightforward process. Once you have a github account, visit our [[resources repository page\|https://github.com/izenda/resources]]. There will be a button at the top of the page that says "Fork". Click this and the repository will be added to your personal repositories. You can now make edits to the resources in your repository without worrying whether you're going to break functionality. Now whenever you update your Izenda.AdHoc.dll to the latest version, instead of copying the Resources from the zipped archive, you will go to your github interface tool (usually a command line, but GUIs are available) and fetch the upstream repository. If there are any conflicts when fetching, you can resolve these using a merge tool. Ideally, there will be no conflicts and your resources will be updated with both your changes and any changes made by us in development. This will allow you to stay current and prevent you from losing any of your own work.
...	...	\ No newline at end of file
	0	+To fork the resources repository, you will need a github account. This can be obtained through your organization or personally and is a straightforward process. Once you have a github account, visit our [[resources repository page\|https://github.com/izenda/resources]]. There will be a button at the top of the page that says "Fork". Click this and the repository will be added to your personal repositories.
	1	+
	2	+![]()
	3	+
	4	+You can now make edits to the resources in your repository without worrying whether you're going to break functionality. Now whenever you update your Izenda.AdHoc.dll to the latest version, instead of copying the Resources from the zipped archive, you will go to your github interface tool (usually a command line, but GUIs are available) and fetch the upstream repository. If there are any conflicts when fetching, you can resolve these using a merge tool. Ideally, there will be no conflicts and your resources will be updated with both your changes and any changes made by us in development. This will allow you to stay current and prevent you from losing any of your own work.
...	...	\ No newline at end of file