77 < meta name ="description "
88 content ="A beginner-friendly blog about README files, wireframes, and Git branches for learning web development. "/>
99 < title > The Blog | Learning Programming Basics</ title >
10+ < link rel ="preconnect " href ="https://fonts.googleapis.com ">
11+ < link rel ="preconnect " href ="https://fonts.gstatic.com " crossorigin >
12+ < link href ="https://fonts.googleapis.com/css2?family=Bitcount+Grid+Single:wght@100..900&family=Cantarell:ital,wght@0,400;0,700;1,400;1,700&display=swap "
13+ rel ="stylesheet ">
1014 < link rel ="stylesheet " href ="style.css "/>
1115</ head >
1216
@@ -32,7 +36,8 @@ <h1 class="site-title">The Blog</h1>
3236 < div class ="article-feature-text ">
3337 < h2 > What is the purpose of a README file</ h2 >
3438 < p >
35- according to GitHub Docs, a README file serves as the primary source of information about a project and
39+ according to GitHub Docs, a README file serves as the primary source of information about a project
40+ and
3641 helps users understand how to install, use, and contribute to it < em > (GitHub Docs, n.d.).</ em >
3742 </ p >
3843 < p >
@@ -55,7 +60,8 @@ <h2>What is the purpose of a wireframe</h2>
5560 A wireframe is a simple visual representation of a website or application's layout. It acts as a
5661 blueprint.
5762 </ p >
58- < p > Figma describes a wireframe as a low-fidelity representation of a user interface that focuses on layout,
63+ < p > Figma describes a wireframe as a low-fidelity representation of a user interface that focuses on
64+ layout,
5965 structure, and functionality before visual design decisions are made < em > (Figma, n.d.).</ em > </ p >
6066 < a class ="article-read-more " href ="# "
6167 aria-label ="read more about the purpose of a wireframe "> Wireframes</ a >
@@ -64,7 +70,8 @@ <h2>What is the purpose of a wireframe</h2>
6470 < article class ="article-sec ">
6571 < img src ="./images/branch.webp " alt ="illustration of a git tree branching out ">
6672 < h2 > What is a branch in Git?</ h2 >
67- < p > Git documentation explains that branches allow developers to diverge from the main line of development
73+ < p > Git documentation explains that branches allow developers to diverge from the main line of
74+ development
6875 and work independently on features before merging their changes back into the project
6976 < em > (Git SCM, n.d.).</ em > </ p >
7077 < p >
0 commit comments