Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found

Submitted

Ping Coming Soon Responsive + Mobile First + PWA Supported,Vanilla JS

#accessibility#vanilla-extract#lighthouse
P
AKโ€ข 6,700

@skyv26

Desktop design screenshot for the Ping single column coming soon page coding challenge

This is a solution for...

  • HTML
  • CSS
  • JS
1newbie
View challenge

Design comparison


SolutionDesign

Solution retrospective


I tried my best to complete this project, I made it along with my other work and for the first time I made PWA, a first mile-stone towards learning Progressive Web App. Any suggestion, comment will be appreciated. Please check my PWA by installing it on your devices, doesn't matter what you are using (except smart watches, LOL!). I am happy to share that I have completed my all newbie challenges . Please share your experience.

Community feedback

P
Matt Studdertโ€ข 13,611

@mattstuddert

Posted

Congratulations on completing all newbie challenges, Aakash! That's an amazing milestone! ๐ŸŽ‰

Your project looks great and matches the design really well. I've got a few small suggestions, which I hope will help.

  • When changing the browser size, there are a couple of screen size ranges where the content size changes quite drastically. Around small tablet sizes, the content is very big and around larger tablet to small laptop sizes, the content shrinks quite a bit. It's best to try to gradually scale up content size from mobile all the way through to larger desktop screen sizes.
  • You're using JS events on the li elements for the social media icons and then changing the styles in JS. Instead, I'd recommend adding hover effects in CSS on the anchor tags. The anchor tags are the interactive elements, and it's best to use CSS for hover effects like this.
  • It's great you're adding alt text and aria-label attributes, but try to think about how they'll be read by screen readers and whether they help add context to the content. For example, you've got the alt text of "Ping's illustration main vector image" on the img element. I'd say that doesn't add much context, and I'd also say that image doesn't really need an alt attribute in the first place as it more of a decorative image to give an idea of what the UI might look like. In this instance, I'd leave the alt attribute blank so screen readers ignore it. On a side note, I wouldn't wrap this img element in a figure. Another example is the aria-label text on the input. Instead of writing "subscriber email address", I would talk directly to the person with something like "Enter your email address".

I hope these tips help. Let me know if you have any questions. I'm looking forward to seeing your junior-level projects! ๐Ÿ‘

Marked as helpful

2

P
AKโ€ข 6,700

@skyv26

Posted

@mattstuddert Wow! Thank you so much. You really told me the right use or meaning of attributes in a logical way.

  1. Sometimes while working on design response, some time a question strike to my mind that, am I really adding media queries in right way OR does all developer do/did same just as like me ?

  2. My next question, are there any fixed/global screen-width break-points ? Because when it comes to making a design with mobile first approach then I start from 280px then slowly move on bigger one. My lots of time go waste in deciding the media-queries screen size to make design persistant. I think as a experienced developer you can guide me right way of working on frontend design.

I am in learning phase, and I am really happy that I am learning, enhancing my skills, also understanding the way of working on a design with different angle view. Yes! Soon you will see my next solution (Junior Level).

1
P
Matt Studdertโ€ข 13,611

@mattstuddert

Posted

@skyv26, you're welcome! I'm happy to help. To answer your questions, I'd always add media queries when necessary based on the layout I'm building. I would let the content dictate when breakpoints are required and would gradually scale up the typography as necessary. If you're working mobile-first with min-width media queries you can leave all mobile and general styles outside of any media query. In my opinion, 280px is too small for your first query. Typically, it would be around the 400-500px range if you're using min-width, although as I mentioned before it depends on what you're building.

The way you're doing it with min-width and em units is great and pretty common ๐Ÿ‘

Marked as helpful

1
P
AKโ€ข 6,700

@skyv26

Posted

@mattstuddert Again Thank You for reply me back

1
Dusvy_Mโ€ข 390

@dovelm

Posted

I like this!!!

Marked as helpful

1
Anosha Ahmedโ€ข 9,340

@anoshaahmed

Posted

Awesome!!!

Marked as helpful

1
Rohitโ€ข 330

@Rohitgour03

Posted

Wow, Looks great. Pixel-perfect. ๐Ÿ˜๐Ÿ‘

Marked as helpful

1
Lukaโ€ข 320

@lukakavtarra

Posted

impressed with your work :)) but if it were a real website it would be more comfortable if links open in a new tab so try target="_blank" in your anchor element ๐Ÿ˜๐Ÿ˜๐Ÿ˜๐Ÿ˜

Marked as helpful

1

P
AKโ€ข 6,700

@skyv26

Posted

@lukakavtarra Really Good Luka, I really forgot to add.

1

Please log in to post a comment

Log in with GitHub
Discord logo

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord