|
8 | 8 | </head> |
9 | 9 | <body> |
10 | 10 | <header> |
11 | | - <h1>Wireframe</h1> |
12 | | - <p> |
13 | | - This is the default, provided code and no changes have been made yet. |
| 11 | + <h1>SOFTWARE DEVELOPMENT LIFECYCLE TOOLS(SDLC)</h1> |
| 12 | + <p id="basic"> |
| 13 | + SDLC tools are software applications that help development teams plan, design, build, test, and deploy software systematically. SDLC tools are software applications that help development teams plan, design, build, test, and deploy software systematically. |
14 | 14 | </p> |
15 | 15 | </header> |
16 | 16 | <main> |
17 | 17 | <article> |
18 | | - <img src="placeholder.svg" alt="" /> |
19 | | - <h2>Title</h2> |
| 18 | + <div> |
| 19 | + <img src="image1.png" alt="an image of a readme.md" /> |
| 20 | + </div> |
| 21 | + <h2>README FILE</h2> |
| 22 | + <p> |
| 23 | + Just like the name implies, you should read a README file as it is the foundational documentation for a software, dataset, or coding project. It serves as a project's "front door," designed to help users quickly understand what the project does, how to install and use it, and how to contribute. It also contains |
| 24 | + clear examples or tutorials demonstrating the project's features in action. |
| 25 | + </p> |
| 26 | + <a href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes">Read more</a> |
| 27 | + </article> |
| 28 | + <article> |
| 29 | + <div> |
| 30 | + <img src="wireframe.png" alt="an image of a wireframe template" /> |
| 31 | + </div> |
| 32 | + <h2>WIREFRAMES</h2> |
| 33 | + <p>Wireframes are basic blueprints that help teams align on requirements, keeping UX design conversations focused and constructive.Think of your wireframe as the skeleton of your app, website, or other final product. Your wireframe shows the design team and stakeholders the bare-bones outlines of essential webpages, components, and features, including: |
| 34 | + </p> |
| 35 | + <ul> |
| 36 | + <li>Screen layouts</li> |
| 37 | + <li>Navigation bars</li> |
| 38 | + <li>Components of UX and UI design</li> |
| 39 | + <li>Interactive elements</li> |
| 40 | + </ul> |
| 41 | + <a href="https://www.figma.com/resource-library/what-is-wireframing/">Read more</a> |
| 42 | + </article> |
| 43 | + <article> |
| 44 | + <div> |
| 45 | + <img src="image2.png" alt="an image of a git branch and its operations" /> |
| 46 | + </div> |
| 47 | + <h2>GIT BRANCH</h2> |
20 | 48 | <p> |
21 | | - Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam, |
22 | | - voluptates. Quisquam, voluptates. |
| 49 | + In Git, a branch is like a separate workspace where you can make changes and try new ideas without affecting the main project. Think of it as a "parallel universe" for your code. |
| 50 | + Branches let you work on different parts of a project, like new features or bug fixes, without interfering with the main branch. Branches allow you to work on different parts of a project without impacting the main branch. |
| 51 | + When the work is complete, a branch can be merged with the main project. You can even switch between branches and work on different projects without them interfering with each other. Branching in Git is very lightweight and fast! |
23 | 52 | </p> |
24 | | - <a href="">Read more</a> |
| 53 | + <a href="https://i0.wp.com/digitalvarys.com/wp-content/uploads/2019/06/GIT-Branchand-its-Operations.png?fit=1921%2C1057&ssl=1">Read more</a> |
25 | 54 | </article> |
26 | 55 | </main> |
27 | 56 | <footer> |
|
0 commit comments