added the additional pics

getting_started.md

 # Creating an account
 Please visit gitlab.iotivity.org and click on the "Register" tab and fillout your information and click on the "Register" green button once done. An e-mail wil lbe sent to you which might end up in the junk mail so please check your junk mail. In the sent e-mail, there will be a link to click taking you back to the log in page where you can enter your username and password and sign in.
-![Registration page]()
+![Registration page](/assets/landing_page.PNG)
 # Setting up SSH access (optional)
 In order to enable SSH access to git lab, an SSH key pair needs to be used. Learn how to create one [here](https://gitlab.openconn.org/help/ssh/README#generating-a-new-ssh-key-pair) or learn how to use an already existing ssh key [here](https://gitlab.openconn.org/help/ssh/README#locating-an-existing-ssh-key-pair).
 Once you obtain an SSH key pair, learn how to add it to your Gitlab account [here](https://gitlab.openconn.org/help/ssh/README#adding-an-ssh-key-to-your-gitlab-account).
@@ -61,19 +61,20 @@ Now that you have a merge request, you can share it with a teammate to get their
 Merge conflicts will be highlighted in the merge request along with the result of the CI testing. More commits and code changes can be made within the merge request. Once the merge conflict is resolved and all the changes are polished, assign it to someone with merge privileges to merge your changes.
 ## Issues
 ### Creating Issues
-To create a new issue, click on the "issues" option in the main menu on the left of the project page and click on the "New issue" green button. 
+To create a new issue, click on the "issues" option in the main menu on the left of the project page and click on the "New issue" green button.
+![New Issue button](/assets/NewIssueButton.png)
 The new issue form will open up, fill it up with the proper title and description and assign it to whomever is responsible. You can also associate your new issue with the proper milestones and labels if that makes sense for your issue along with a due date. The "Submit issue" button will light up green and becomes clickable. Click it to create the issue.
-![Issue Form]()
+![Issue Form](/assets/NewIssueForm.png)
 Once the issue is created, your teammate with the proper permissions will be able to vote it up or down, comment or start a discussion thread about it. Whoever is responsible for fixing the issue can create a new merge request from your issue and the issue will be automatically updated as the merge request matures.
-![Issue Page]()
+![Issue Page](/assets/issuePage.png)
 ### Orgnize Issues
 Issues can be organized into boards of a project and each board can have multiple lists of issues. Each board could be specific to a milestone or to a specific team and the lists within these boards could be a done pile for example or a backlog pile or Work-In_Progress (WIP) pile.
 ## Continuous Integration
 Continuous Integration is one of the main advantages of Gitlab! In fact, it was rated as the best by the [Forrester CI Wave ™](https://about.gitlab.com/resources/forrester-wave-cloudnative-ci/) report. 
 To see the pipelines and the jobs of a project, click on the CI/CD option from the project menu then click on pipelines.You should be able to see all the historical pipelines. 
-![pipelines]()
+![pipelines](/assets/pipelines.png)
 From there, you can click on the jobs themselves and see the logs and the console.
-![Job consol]()
+![Job consol](/assets/job_consol.png)
 ## Recommended Workflow
 Gitlab workflow is highly flexable there are many possible workflows that can suit the needs of many teams. However, with flexability, comes complexity. the Gitlab recommended workflow is the following
 * start an issue