Skip to content

Glasgow | 26-ITP-May | Francesco Romano Monda | Sprint 2 | Wireframe to Web Code#1409

Open
fromonda wants to merge 8 commits into
CodeYourFuture:mainfrom
fromonda:feature/wireframe
Open

Glasgow | 26-ITP-May | Francesco Romano Monda | Sprint 2 | Wireframe to Web Code#1409
fromonda wants to merge 8 commits into
CodeYourFuture:mainfrom
fromonda:feature/wireframe

Conversation

@fromonda
Copy link
Copy Markdown

@fromonda fromonda commented Jun 3, 2026

Self checklist

  • I have titled my PR with Region | Cohort | FirstName LastName | Sprint | Assignment Title
  • My changes meet the requirements of the task
  • I have tested my changes
  • My changes follow the style guide

Changelist

  • Implemented semantic HTML structure using header, main, article, and footer elements.
  • Created three articles explaining README files, wireframes, and Git branches.
  • Added unique images, summaries, and links for each article.
  • Styled the webpage using an external CSS file to match the provided wireframe.
  • Applied CSS Grid and spacing adjustments to improve layout and readability.
  • Fixed the footer to the bottom of the viewport.
  • Added descriptive alt text to support accessibility requirements.
  • Validated HTML and reviewed content for formatting, grammar, and accuracy.
  • Used Git for version control with regular commits and pushes to GitHub.

@netlify
Copy link
Copy Markdown

netlify Bot commented Jun 3, 2026

Deploy Preview for cyf-onboarding-module ready!

Name Link
🔨 Latest commit 28ef6ef
🔍 Latest deploy log https://app.netlify.com/projects/cyf-onboarding-module/deploys/6a248a39e2b3420008d9402e
😎 Deploy Preview https://deploy-preview-1409--cyf-onboarding-module.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
2 paths audited
Performance: 100 (no change from production)
Accessibility: 100 (no change from production)
Best Practices: 100 (no change from production)
SEO: 86 (no change from production)
PWA: -
View the detailed breakdown and full score reports
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@fromonda fromonda added the Needs Review Trainee to add when requesting review. PRs without this label will not be reviewed. label Jun 3, 2026
@akeren akeren self-requested a review June 5, 2026 08:47
@akeren akeren added 📅 Sprint 2 Assigned during Sprint 2 of this module Review in progress This review is currently being reviewed. This label will be replaced by "Reviewed" soon. Module-Onboarding The name of the module. and removed Needs Review Trainee to add when requesting review. PRs without this label will not be reviewed. labels Jun 5, 2026
Copy link
Copy Markdown

@akeren akeren left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fromonda, your codebase structure is currently simple and easy to follow, with files kept in the same root directory.

  • As your projects grow, what might happen if you later add more CSS files, JavaScript files, images, or multiple HTML pages?
  • How could you organise your folders so the project stays easy to navigate, scalable and maintainable now and in the future?

Comment thread Wireframe/index.html
Comment on lines 57 to 62
<footer>
<p>
This is the default, provided code and no changes have been made yet.
Built using semantic HTML, CSS layout techniques, and version control
practices.
</p>
</footer>
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fromonda, examine the footer position in the rendered UI. Where should it sit relative to the rest of the page, and what styling might need to change?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The footer was intentionally anchored to the bottom of the viewport using position: fixed. However, based on your comment, I understood that the footer would be better positioned below the page content so that it follows the normal document flow. I have therefore removed the fixed positioning and allowed the footer to sit naturally after the main content.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fromonda, how about the alignment of the footer position?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From my perspective, the footer was not misaligned with the rest of the content. I understand that it may be preferable to centre it, and I have now made that adjustment.

Comment thread Wireframe/index.html
This is the default, provided code and no changes have been made yet.
</p>
<p>Learn about README files, wireframes, and Git branches.</p>
</header>
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fromonda, when you compare the header with the main body, does the UI alignment look intentional? What CSS change might help align them?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The alignment between the header and the main body was not intentional; it was simply the default behaviour. From your comment, I understood that you were suggesting a more consistent alignment, so I applied the same container styling used for the main body to the header as well.

Comment thread Wireframe/index.html Outdated
<title>Wireframe</title>
<link rel="stylesheet" href="style.css" />
</head>

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fromonda, could you explain why you've added this empty line?

Copy link
Copy Markdown
Author

@fromonda fromonda Jun 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The empty line you mentioned, along with the others I added, is intended to make the code more readable by visually separating the different sections. In this case, it helps distinguish the head snippet from the body snippet, while the others separate the individual article snippets, making the structure easier to read.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fromonda, you could use the prettier or eslint extension plugins to help with code formatting. It'll be more consistent and automatic.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I used Prettier since the Form Controls assignment, and the empty lines were added on my own initiative. Since I understand they may be considered unnecessary, I have removed them.

@akeren akeren added Reviewed Volunteer to add when completing a review with trainee action still to take. and removed Review in progress This review is currently being reviewed. This label will be replaced by "Reviewed" soon. labels Jun 5, 2026
@fromonda fromonda added Needs Review Trainee to add when requesting review. PRs without this label will not be reviewed. and removed Reviewed Volunteer to add when completing a review with trainee action still to take. labels Jun 5, 2026
@akeren
Copy link
Copy Markdown

akeren commented Jun 6, 2026

@fromonda, your codebase structure is currently simple and easy to follow, with files kept in the same root directory.

  • As your projects grow, what might happen if you later add more CSS files, JavaScript files, images, or multiple HTML pages?
  • How could you organise your folders so the project stays easy to navigate, scalable and maintainable now and in the future?

@fromonda, what about this comment?

@fromonda
Copy link
Copy Markdown
Author

fromonda commented Jun 6, 2026

@fromonda, your codebase structure is currently simple and easy to follow, with files kept in the same root directory.

  • As your projects grow, what might happen if you later add more CSS files, JavaScript files, images, or multiple HTML pages?
  • How could you organise your folders so the project stays easy to navigate, scalable and maintainable now and in the future?

@fromonda, what about this comment?

If my project grows in terms of elements and styles, I would consider adding additional branches rather than changing the file structure in the current branch. However, I have also grouped the images into a dedicated folder.

@akeren
Copy link
Copy Markdown

akeren commented Jun 6, 2026

@fromonda, your codebase structure is currently simple and easy to follow, with files kept in the same root directory.

  • As your projects grow, what might happen if you later add more CSS files, JavaScript files, images, or multiple HTML pages?
  • How could you organise your folders so the project stays easy to navigate, scalable and maintainable now and in the future?

@fromonda, what about this comment?

If my project grows in terms of elements and styles, I would consider adding additional branches rather than changing the file structure in the current branch. However, I have also grouped the images into a dedicated folder.

Good to know. Similar to images, you'll create subfolders for each distinct content.

Great job.

Comment thread Wireframe/index.html Outdated
Comment on lines +16 to +39
<img
src="readme.png"
alt="Illustration promoting the creation of an effective README file"
/>
<h2>What is a README File?</h2>
<p>
A README file explains what a project does, how to install it, how to
use it, and any important information developers need. It is usually
the first file people read when viewing a project.
</p>
<a href="https://www.makeareadme.com/">Read more</a>
</article>
<article>
<img src="wireframe.png" alt="Wireframe showing a webpage layout" />
<h2>What is a Wireframe?</h2>
<p>
A wireframe is a digital diagram that shows the skeleton of a website.
It strips away visual elements like colors, fonts, and images to focus
entirely on where headers and content blocks live.
</p>
<a href="https://balsamiq.com/blog/what-are-wireframes/">Read more</a>
</article>
<article>
<img src="git-branch.png" alt="Illustration of branching in Git" />
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fromonda, your images aren't displaying on the UI anymore. Could you debug and correct what's wrong?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As required, I updated image source paths to reflect the new folder structure.

@akeren akeren added Reviewed Volunteer to add when completing a review with trainee action still to take. and removed Needs Review Trainee to add when requesting review. PRs without this label will not be reviewed. labels Jun 6, 2026
@fromonda fromonda added Needs Review Trainee to add when requesting review. PRs without this label will not be reviewed. and removed Reviewed Volunteer to add when completing a review with trainee action still to take. labels Jun 6, 2026
@akeren akeren removed the Needs Review Trainee to add when requesting review. PRs without this label will not be reviewed. label Jun 6, 2026
@akeren akeren added the Complete Volunteer to add when work is complete and all review comments have been addressed. label Jun 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Complete Volunteer to add when work is complete and all review comments have been addressed. Module-Onboarding The name of the module. 📅 Sprint 2 Assigned during Sprint 2 of this module

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants