Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 4 years ago

First solution submit on FEM. Used HTML, CSS and JS.

rikvandersar•145
@RikvanderSar
A solution to the Officelite coming soon site challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Some tips and suggestions to further style the form elements would be great. I'd also would appreciate feedback on the readability of the code.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Matt Studdert•13,611
    @mattstuddert
    Posted almost 4 years ago

    Hi Rik, first of all, congrats on submitting your first solution! 🎊

    I hope you enjoyed building the project and learned some new things along the way. You've done an excellent job. Here are some thoughts after taking a look at your solution:

    • First up, from a codebase/project architecture perspective, I'd recommend cleaning up your file and folder structure. You've still got a /starter-code folder in there, which doesn't seem to be getting used, and all your assets are at the root level of your project. To clean things up, you could put them in an /assets folder.
    • It's great to read through your README.md file and learn more about your process and the time it took you to complete the project. Journaling your process will be a great help as you progress. Nice to see you mention client-side validation in your "Continued Development" section as well because that's something I was going to point out. Using the built-in HTML5 validations is great, but you'll often need custom client-side validation based on the design. So it's well worth practising early on.
    • You're linking to separate CSS files on your two pages. It's best to keep it to a single CSS file and link to that on both pages. That way, you can reuse styles between pages and not duplicate code unnecessarily.
    • For your HTML, be sure to really think through what element makes the most sense semantically in a given situation. For example, you're currently using paragraphs for the lists of features in the pricing components when an unordered list would make more sense.
    • The homepage's responsiveness isn't quite right at the moment, as the content overlaps between sections.
    • The overall layout of your pages look good, but there are slight differences between your solution and the design. Spending some time working through these visual differences and bringing the solution a bit closer would be time well spent.
    • Your form styling looks fine! Styling things like select boxes isn't overly necessary, especially at this point. You can always come back to that at a future date.

    I hope these pointers help. Let me know if you have any questions! 🙂

    Marked as helpful
  • rikvandersar•145
    @RikvanderSar
    Posted almost 4 years ago

    Hi Matt,

    Thank you for this helpfull feedback, really appreciate it! I'm definitly learning a lot from this project.

    I'll get back at it with your feedback and will post a update soon!

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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