Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 24 days ago

Newsletter Subscription UI with Carousel Slider (Responsive Design)

sass/scss, bem
Nata•170
@kristianusdianata
A solution to the Newsletter sign-up form with success message challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

For this challenge, I experimented with using a carousel to navigate between the subscription form and the confirmation page. Overall, I'm quite pleased with the result!

What specific areas of your project would you like help with?

I'd really appreciate any feedback, especially on the fluid layout part. I found it a bit challenging to wrap my head around and get it just right.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Andrey•4,480
    @dar-ju
    Posted 24 days ago

    Hi, Nata!

    I really like neat works, yours is one of them!

    Your work is great - good responsiveness, BEM without errors, semantics are correct. Carousel is super! The project structure is designed for a medium and large project, this is great for practice.

    I found several points that can be corrected:

    • look at the mobile design, there should be no indents in .carousel, you need to remove 2 lines:
    align-items: center;
    padding: 0.5em;
    
    • there is an error in html:
    <ul class="list mt-6">↩
      <div class="list__container">↩
    

    ul should not contain a div tag

    • do not use defer and module together, leave one or the other, otherwise it is an error <script defer src="./script/index.js" type="module">
    • camelCase is usually used in naming constants, not snake_case in js
    • there is a problem in the carousel: if you use keyboard navigation, then after the button you go to the confirmation window, this needs to be fixed

    Otherwise everything is great, good luck with your development!

    Marked as helpful
  • John Gorman•150
    @Johng117
    Posted 24 days ago

    The carousel works nicely. The focus states are nice too.

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
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub