How git works?

The structure of how Git works is shown in the following figure:

How to create a Git repository and adding files?

The following steps were taken to configure Git on my computer:

1. The first thing is to install Git
2. To create a repository on my computer I started by setting up my account using the commands "user.name" and "user.email".

  	$ git config --global user.name "anapilar.valerga"
	$ git config --global user.email "anapilar.valerga@uca.es"
	

3. I generated an SSH key to allow Git to connect to my computer.

	ssh-keygen -t rsa -C "anapilar.valerga@uca.es" 
	

4. I copied and pasted the key into my Git profile.

	pbcopy < ~/.ssh/id_rsa.pub
	

5. Clone the GitLab repository to my computer.
6. You can now work locally.

My start with git

I decided to work with the HMTL we were given and change the style little by little, despite seeing much more colourful and detailed examples (GitLab Pages examples).

This means that to change any formatting style, I look up the instructions on the HTML website (W3 HTML chools).

I looked up the things I didn't know how to do such as resizing images, having 2 columns, including separator lines, etc.

Therefore, the following steps were followed to work:

1. The first thing to do is to place myself in the directory where I am working and make the changes

		$ git cd (directory of the folder where I am working)
		

2. Significant changes were made to the files you want.
3. I used the "git status" command to check the changes.

		$ git status
		

4. I used "git add" to update the changes.

		$ git add . (changes to all documents)
		$ git add "filename" (changes only to that document)
		

5. I used "git commit -m" to commit changes

		$ git commit -m "changes made"
		

6. I used "git push" to push to production or online.

		$ git push
		

My documentation and how I learned

I wrote the content of my documentation in HTML format using a text editor in Visual Studio Code. Always keep in mind the organization of the content and the logical structure to make it easy to read and understand. It is also possible to incorporate CSS styles to improve the visual design of the documentation. In my case, I followed the default format included as a student in Git, since I preferred to understand each step I do even if the documentation is visually less attractive than using a template.

With this, I have learned to insert simple texts, justify them or put them in the area of the document that interests me, incorporate tables, images, videos and audio to complement the content and improve the user experience. It is important to optimize and compress multimedia files so that the web page loads quickly. Also keep in mind the Git upload limit of 10 MB.

It is also important to validate the HTML code before publishing the documentation to avoid errors and not to be continuously re-uploading files (in this first week I did a lot of "gitpush").

Conclusions

This is the first time I work with a VCS like Git. I had no idea what branches or commits were and I'm still in the process of learning. I've never used HTML either, so I'm learning the basics of the basic structure.

However, I think this course has helped me to get a clear understanding of the basics and I have been able to create my GIT repository and develop my website in HTML and CSS in a few days.

Final project idea

---

This week I have been thinking about defining my final project idea and started to getting used to the documentation process.

In this first week, I still don't have a clear idea of what product I want to make. I have doubts about my ability to manufacture or program it. So, I come up with ideas that I see as too complex, or on the contrary, too simple. However, I am going to explain below some of the ideas that have occurred to me.

Toys