First draft of gitea and ssh guide complete

.gitignore

@@ -49,3 +49,4 @@ flycheck_*.el
 /network-security.data
 
 
+*.html

gitea.md

@@ -27,6 +27,9 @@ Gitea is a GitHub/GitLab clone written in Go.
    - Owner:  Either yourself or an organization you are a member of
    - Repository Name:  something short with US alphabet, numbers, and dashes or underscores.  *Avoid accented and letters outside of the 26 a-z*
    - Visibility:  check this box to keep it private.  In general, make things private unless you are really sure you want search engines, AI LLM scrapers, and random people to look at it.
+   - Description:  Explain what this is about so that people know quickly if it relates to what they need.  This is also the most easily searched.
    - Issue Labels: Default (unless you are working on a project with a complicated management/approval process)
    - License:  Skip this if private.  If not, read the quick overview on licenses at https://choosealicense.com/
-   
+   - README: The default is a nice place to start.  If you haven't already setup a git workspace/repository on your computer, I recommend checking "Initialize Repository (Adds .gitignore, License, and README)" so that the repository starts with some useful files.
+   - Default Branch:  This choice is a bit political in places as explained in a [2020 article at the software freedom conservancy](https://sfconservancy.org/news/2020/jun/23/gitbranchname/).  The default of "main" is less offensive to certain groups.  "master" was the classical name for many years.
+   -Once you are happy, click "Create Repository"

ssh/gitea-ssh-setup.md

@@ -2,16 +2,26 @@
 This guide assumes you have registered and verified your account with an @RU.IS email address.  If you have not setup your account yet, you must do that first.
 The gitea server at RU is on port 2222.  *It does not respond on the usual port 22*
 
-- (Gitea Documentation)[https://docs.gitea.com/]
+- [Gitea Documentation](https://docs.gitea.com/)
 
 # Installing ssh keys into Gitea
 1. If you don't have an ssh key, generate one now following the guide on the (main ssh page)[index.md]
 1. Login to gitea.cs.ru.is
 1. Click on your user Icon on the top right and choose "Settings" in the dropdown
 1. On the Left, click on "SSH / GPG Keys"
+   ![menu of SSH / GPG Keys](Graphics/gitea-ssh-nokeys.png)
 1. copy the contents of `~/.ssh/id_ed25519.pub` into the text box and click "Add Key".  *On windows you can view it in Notepad to cut and paste it*.
-1. It will then want you to verify the key by **TODO**
+   ![SSH key pasted into the text field](Graphics/gitea-ssh-pubkey-paste.png)
-
+1. It will then want you to verify the key by running a `ssh-keygen`.  You will need to tell it where your public key is, typically `~/.ssh/id_ed25519.pub.  **This process must be done quickly as the tokens expire!!!**
+    1. First look at the validation information given.  This guide assumes you are on linux of some sort, but there are directions for Windows also listed
+   ![verification prompt, empty](Graphics/gitea-ssh-signingtoken.png)
+    2. Open a command shell (if you weren't already) and run the ssh-keygen command to sign the token with your key
+   ![shell prompt running sshkeygen](Graphics/gitea-ssh-sshkeygen-sign.png)
+    2. Paste the results into the "Armored SSH signature" area
+   ![verification prompt, full](Graphics/gitea-ssh-signingtoken-filled.png)
+    2. Click "Verify"
+1. If validation is done quickly and with the right key, you will see confirmation
+   ![Successful validation box](Graphics/gitea-ssh-verified.png)
 
 # Testing
 If you have ssh setup properly with gitea, you should be able to test it this way: