From d726f11716903b5743193f4e2f2c4797f4df85d1 Mon Sep 17 00:00:00 2001 From: Dipa Sarker Date: Thu, 21 May 2026 01:33:18 +0100 Subject: [PATCH] final wireframe submission --- Wireframe/index.html | 82 ++++++++++++++++++++++++++++++++++++++------ Wireframe/style.css | 67 +++++++++++------------------------- 2 files changed, 91 insertions(+), 58 deletions(-) diff --git a/Wireframe/index.html b/Wireframe/index.html index 0e014e535..f7d60f253 100644 --- a/Wireframe/index.html +++ b/Wireframe/index.html @@ -1,4 +1,4 @@ - + @@ -8,26 +8,86 @@
-

Wireframe

+

WIREFRAME

- This is the default, provided code and no changes have been made yet. + A Wireframe is a simple visual layout or blueprint of a website, mobile + app or software interface. It shows the basic structure of a page + without detailed colors, images or final design elements.

- -

Title

+ Readme.md +

What is the purpose of a README file?

+

Summary

- Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam, - voluptates. Quisquam, voluptates. + A README file is a simple text file (usually named README.md) that + explains what your project about and how to use it. When someone opens + a GitHub repo, the README is usually the first thing they see. It + helps them quickly understand:

- Read more +
    +
  • What the project does
    • +
  • How to run it
    • +
  • How to install it (if needed)
    • +
  • Any important instructions or notes
    • +
+ Read more +
+
+ Wireframe +

What is the purpose of a wireframe?

+

Summary

+

+ A wireframe is a simple visual blueprint of a website, app, or digital + product. It shows the structure and layout of a screen or page without + focusing on final colors, graphics, or detailed styling. Think of it + like an architectural sketch for a building: +

+
    +
  • It outlines where things go
    • +
  • It shows how users move through the interface
    • +
  • + It helps teams agree on functionality before design and development + begin +
    • +
+

+ Wireframes are usually made with boxes, lines, placeholders and labels + instead of polished visuals. +

+ Read more +
+
+ Git Branch +

What is a branch in Git?

+

Summary

+

+ A branch in Git is an independent line of development. It lets you + work on changes without affecting the main version of the project. You + can think of a branch like a parallel workspace: +

+
    +
  • The main project stays stable
    • +
  • You make changes safely in another branch
    • +
  • Later, you can merge those changes back into the main project
    • +
+ Read more
diff --git a/Wireframe/style.css b/Wireframe/style.css index be835b6c7..47904462c 100644 --- a/Wireframe/style.css +++ b/Wireframe/style.css @@ -1,21 +1,6 @@ -/* Here are some starter styles -You can edit these or replace them entirely -It's showing you a common way to organise CSS -And includes solutions to common problems -As well as useful links to learn more */ - -/* ====== Design Palette ====== - This is our "design palette". - It sets out the colours, fonts, styles etc to be used in this design - At work, a designer will give these to you based on the corporate brand, but while you are learning - You can design it yourself if you like - Inspect the starter design with Devtools - Click on the colour swatches to see what is happening - I've put some useful CSS you won't have learned yet - For you to explore and play with if you are interested - https://web.dev/articles/min-max-clamp - https://scrimba.com/learn-css-variables-c026 -====== Design Palette ====== */ +header { + text-align: center; +} :root { --paper: oklch(7 0 0); --ink: color-mix(in oklab, var(--color) 5%, black); @@ -24,8 +9,7 @@ As well as useful links to learn more */ --line: 1px solid; --container: 1280px; } -/* ====== Base Elements ====== - General rules for basic HTML elements in any context */ + body { background: var(--paper); color: var(--ink); @@ -36,54 +20,43 @@ a { border: var(--line); max-width: fit-content; } + img, svg { width: 100%; object-fit: cover; } -/* ====== Site Layout ====== -Setting the overall rules for page regions -https://www.w3.org/WAI/tutorials/page-structure/regions/ -*/ + main { max-width: var(--container); margin: 0 auto calc(var(--space) * 4) auto; } footer { - position: fixed; bottom: 0; text-align: center; } -/* ====== Articles Grid Layout ==== -Setting the rules for how articles are placed in the main element. -Inspect this in Devtools and click the "grid" button in the Elements view -Play with the options that come up. -https://developer.chrome.com/docs/devtools/css/grid -https://gridbyexample.com/learn/ -*/ main { display: grid; grid-template-columns: 1fr 1fr; - gap: var(--space); - > *:first-child { - grid-column: span 2; - } + gap: 10px; } -/* ====== Article Layout ====== -Setting the rules for how elements are placed in the article. -Now laying out just the INSIDE of the repeated card/article design. -Keeping things orderly and separate is the key to good, simple CSS. -*/ +main > *:first-child { + grid-column: 1/ -1; +} + article { border: var(--line); padding-bottom: var(--space); text-align: left; display: grid; grid-template-columns: var(--space) 1fr var(--space); - > * { - grid-column: 2/3; - } - > img { - grid-column: span 3; - } +} +article > * { + grid-column: 2/3; +} +article > img { + grid-column: span 3; + height: auto; + width: 100%; + object-fit: cover; }