In this project we will build a custom website using HTML5 and modern CSS techniques such as CSS Grid, Flexbox, psuedo selectors, animation and more. We will also deploy to Netlify and add form functionality

Code:
https://github.com/bradtraversy/loruki-website

💖 Support The Channel!
http://www.patreon.com/traversymedia

Website & Brad Traversy Udemy Course Links:
https://www.traversymedia.com

Follow Traversy Media:
https://www.twitter.com/traversymedia
https://www.instagram.com/traversymedia
https://www.facebook.com/traversymedia

Timestamps:
0:00 – Intro
2:32 – Base & Navbar HTML
6:05 – Base CSS
9:08 – Navbar, Container, Flex
16:12 – Showcase Area & Grid
27:28 – Card & Form CSS
33:07 – Button Styles
35:45 – Skewed Area
39:42 – Stats Section
44:16 – Utility Classes – Margin & Padding
52:33 – CLI Section & Grid Col & Row Span
57:25 – Cloud Section
1:00:50 – Background & Button Utility Classes
1:04:00 – Text Sizes
1:05:28 – Languages Section
1:09:49 – Footer
1:14:08 – Media Queries & Responsiveness
1:21:34 – Features Page
1:29:57 – Features Grid With Spans
1:32:15 – Docs Page
1:42:44 – Alert, Code Block & Text Color Styles
1:49:02 – Make Inner Pages Responsive
1:52:02 – Animations
1:56:42 – Prepare & Deploy To Netlify

source

47 Comments

  1. Ok, so I'm probably the only one to do this but hey, I do cool stuff that causes things to break… I noticed when Brad added the utilities.css stylesheet he placed it before the regular styles.css. I had already moved on, lol, and had added it after… When it came time to center the .stats-heading, it didn't work. So, I checked, and double checked my entry, and it was fine. Then it hit me, I hadn't re-ordered the style sheets. I flipped them, to what he had, and it worked. So, I'm guessing the cascade failed for me in this case…

  2. Is anyone having trouble with Chrome. It appears to have a white container in front of ther grids, navbar etc. Only happening on Chrome. I ran my code and the original from github on Edge and it worked fine. Any ideas?

  3. Cannot figure out why the padding for selector (utility) .card of 20px and the padding for selector (showcase) .showcase-form of 40px wont play nicely for me the way the demonstration does. Chrome is putting strikethrough on my 40px padding for the .showcase-form, and I had to override it with !important (which worked), which I know is typically taboo, but I cant find the conflict here. Any advice?

  4. I hear till now 20minutes and I found it very basic not using classes names like bem or using relative unit. Moreover, why not using sass processor ?

  5. you can use npm live-server as global in any project you working on : npm i live-server -g and when you open your project just write in your terminal live-server it better than live-server in vs code as it takes a lot of time to load check vs-code extension resources

  6. This is a great guide to building a responsive website. One thing I would love to see is a video outlining the process for determining the elements. Like, your nav bar in this was a nav inside a div inside a div but how did you decide that's how it needed to be done? Things like that are where I struggle the most so any way to improve that would be awesome. Thank you for your content, it's by far the best available on the web.

  7. Good day Brad, thank you so much for this tutorial currently on it but when I used magin: auto; on the stats-heading it didn't center it because of the utilities my-1: 1rem 0; that has been set but anytime I turn it off it centers
    Would there be a reason for this ???
    Also when I open it on chrome dev the margin: auto; has a strike through line over it
    Sorry for the long question
    Thank you once again

  8. Not really much of a "commenter" but wanted to say thanks for this and the other excellent free content. Picked up a couple of your Udemy courses of the back of this, and really appreciate all the hard work you put in, as well as how clearly you explain everything. As someone who has aggressively avoided front-end development for my entire career, this is exactly what I needed! 🙂

  9. Hello, thanks for your tutorial.
    I want to know your vs code font and settings for getting exactly the workflow you have (font, theme, line spacing, height, …)
    Thank you for your comprehensive care.

  10. Ran into a bit of a "gotcha" moment at 51:30 in the video. setting the .stats-heading to margin: auto did not give me equal margins (the h3 test did not center). Turns out the my-1 utility class we had just made was interfering, since it is defined with margin 1.5rem 0; Since both of these have the same CSS specificity (both acting on a single class property), the one that was defined last took precedent. I put my link to the utilities style sheet after the one for style.css, which means the my-1 definition came last.

    Lesson learned: Pay attention to your specificity and the order in which you are importing your CSS.

Leave A Reply

Please enter your comment!
Please enter your name here