@@ -19,19 +19,49 @@ <h1>Workflow</h1>
1919 </ header >
2020 < main >
2121 < article >
22- < img src ="placeholder.svg " alt ="" />
23- < h2 > Title </ h2 >
22+ < img src ="Readme.png " alt ="Readme file example " />
23+ < h2 > README files </ h2 >
2424 < p >
25- Lorem ipsum dolor sit amet consectetur adipisicing elit.
26- Quisquam, voluptates. Quisquam, voluptates.
25+ A README file explains a project to other developers and
26+ users. It usually includes the project purpose, installation
27+ steps, usage instructions, features and other important
28+ information so anyone can quickly understand and work with
29+ the project.
2730 </ p >
28- < a href =""> Read more</ a >
31+ < a
32+ href ="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes "
33+ > Read more</ a
34+ >
35+ </ article >
36+ < article >
37+ < img src ="Wireframe.png " alt ="Wireframe example " />
38+ < h2 > Wireframe</ h2 >
39+ < p >
40+ A wireframe isa simple visual layout used to plan the
41+ structure, content, and use experience of a website or
42+ application before development begins.
43+ </ p >
44+ < a
45+ href ="https://www.figma.com/resource-library/what-is-wireframing "
46+ > Read more</ a
47+ >
48+ </ article >
49+ < article >
50+ < img src ="GitBranch.png " alt ="Git branching example " />
51+ < h2 > Git Branching</ h2 >
52+ < p >
53+ Git branching allows developers to work on new features or
54+ fixes separately without affecting the main project code
55+ until the changes are ready to merge
56+ </ p >
57+ < a href ="https://www.atlassian.com/git/tutorials/using-branches "
58+ > Read more</ a
59+ >
2960 </ article >
3061 </ main >
3162 < footer >
3263 < p >
33- This is the default, provided code and no changes have been made
34- yet.
64+ This website was coded by Szidonia Bodo
3565 </ p >
3666 </ footer >
3767 </ body >
0 commit comments