Skip to content

PR: review of business project #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 58 commits into
base: main
Choose a base branch
from

Conversation

christina-baldwin
Copy link

No description provided.

Copy link

@JasminHed JasminHed left a comment

Choose a reason for hiding this comment

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

Hello Christina, overall a very insightful review for me, clean and easy to watch in different documents. Missing some comments but I think that is because I personally dont fully understand everything just yet :). I am not asking for changes, rather explanations so no stress on that. Thanks for a well structured code.

script.js Outdated

Choose a reason for hiding this comment

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

Great use javascritp, makes the site very interactive and "in motion". A plus for the comments to make it clear what is happening.

Choose a reason for hiding this comment

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

Clean and clear to look at. Like the use of section and division. So section is for content that has a certain topic? And div is more for layout, general?

Copy link
Author

Choose a reason for hiding this comment

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

Yes that's how I used it! I thought of it as the different parts of my site.

Comment on lines +24 to +38
<nav class="nav">
<ul class="nav-links">
<li><a href="#top" class="nav-link">Top</a></li>
<li><a href="#about" class="nav-link">About</a></li>
<li><a href="#shop" class="nav-link">Shop</a></li>
<li><a href="#events" class="nav-link">Events</a></li>
<li><a href="#membership" class="nav-link">Membership</a></li>
<li>
<a href="#" class="nav-link nav-btn"
><ion-icon name="cart" class="cart-icon"></ion-icon
><span class="cart-text">Cart</span></a
>
</li>
</ul>
</nav>

Choose a reason for hiding this comment

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

Would you say it is always important having ul and li in a navbar? I have seen other options.

Copy link
Author

Choose a reason for hiding this comment

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

I think it's a preference, I find it easier to identify in my code.

Comment on lines +12 to +64
/* UNIVERSAL STYLES */
* {
margin: 0;
padding: 0;
box-sizing: border-box;
}

html {
scroll-behavior: smooth;
}

body {
font-family: "Roboto", sans-serif;
background-color: #fdfaff;
color: #2f184b;
}

p {
line-height: 1.5;
font-size: 1.2rem;
}

/* SECTIONS */
.section {
max-width: 1800px;
margin: 0 auto;
padding: 10rem 1rem 10rem 1rem;
}

.section-text {
display: grid;
grid-template-columns: repeat(1, 1fr);
gap: 2rem;
}

.section-title {
font-size: 3rem;
margin-bottom: 3rem;
}

.section-subtitle {
font-size: 1.6rem;
margin-bottom: 2rem;
}

.section-desc {
margin-bottom: 2rem;
}

.dark-bg-section {
background-color: #eeebf0;
}

Choose a reason for hiding this comment

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

You said this in the demo, that since all sections have the same style it is easier to put them here. I understand that. But, if you then wanted to change one section and keep the rest the same, would you do that in your style.css? Otherwise, really like this way of thinking.

Copy link
Author

Choose a reason for hiding this comment

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

Yep! So if I have any specific changes for certain areas I just do that in the style.css, anything that I use repeatedly across the page I have put in general.css. Again I think its a preference for organising things.

Comment on lines +13 to +14
z-index: 999999;
}

Choose a reason for hiding this comment

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

What does this do? z-index :)

Copy link
Author

Choose a reason for hiding this comment

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

It just puts it above everything else so it's visible :) (I just put a really big number to be certain).

@JasminHed
Copy link

Okay, thanks a lot for your time answering my comments. Enjoyed this.

Copy link
Contributor

@HIPPIEKICK HIPPIEKICK left a comment

Choose a reason for hiding this comment

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

Really good job with this project! Especially like your take on the stretch goals. One thing I need you to fix however is that your labels don’t match (e.g. you have two labels called email and one label called movie, but no matching input with that id). Fix this and you’re good to go 💪

And a reminder for coming projects: Remember to indent attributesif you have two or more of them, it will make the code easier to read.

Changes requested

  • Proper labels

@christina-baldwin
Copy link
Author

Thanks for the feedback! I will work on correcting the labels, I must have just copied and not changed them accordingly, sorry! I have a question about indenting attributes though, I have prettier installed on my vscode so it doesn't allow me to indent things myself really (unless I misunderstood what you meant), if I indent it just reverts them back, it only seems to indent when the number of attributes gets longer than a certain amount, I'd rather not remove prettier, is there another way around this or is this ok?

@HIPPIEKICK
Copy link
Contributor

HIPPIEKICK commented Mar 5, 2025 via email

@christina-baldwin
Copy link
Author

Great! I'll look into it, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants