@@ -15,7 +15,7 @@ <h1>Understanding README Files, Wireframes and Git Branches</h1>
1515 < main >
1616 <!--Top article (full-width)-->
1717 < article class ="top-article " id ="readme-article ">
18- < img src ="images/readme.png " alt ="Illustration of a README file " />
18+ < img src ="placeholder.svg " alt ="Illustration of a README file " />
1919 < h2 > What is the purpose of a README file?</ h2 >
2020 < p >
2121 A README file explains what a project is about, how to use it, and any important information someone needs before working with the project code.
@@ -28,7 +28,7 @@ <h2>What is the purpose of a README file?</h2>
2828 < section class ="bottom-articles ">
2929
3030 < article id ="wireframe-article ">
31- < img src ="images/wireframe.png " alt ="Example of a webpage wireframe "/>
31+ < img src ="placeholder.svg " alt ="Example of a webpage wireframe "/>
3232 < h2 > What is the purpose of a wireframe?</ h2 >
3333 < p >
3434 A wireframe is a simple layout plan that shows where content will go on a webpage before you start designing or coding.
@@ -38,7 +38,7 @@ <h2>What is the purpose of a wireframe?</h2>
3838 </ article >
3939
4040 < article id ="branch-article ">
41- < img src ="images/git-branch.png " alt ="Diagram showing Git branches "/>
41+ < img src ="placeholder.svg " alt ="Diagram showing Git branches "/>
4242 < h2 > What is a branch in Git?</ h2 >
4343 < p >
4444 A Git baranch lets developers work on new features without affecting the main project. When finished, the branch can be merged back in.
0 commit comments