Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
11
Comments
13
P

moe

@jellmooUnited States220 points

Hey, I’m Moe! A 23-year-old beginner coder learning front-end development. I love my cat, Marvel, crocheting, and gaming. Always looking to improve my skills and make new friends! Feel free to add me on Discord @jellmo—let’s learn and code together!

Latest solutions

  • Timetracking Dashboard - JS + SASS + JSON

    #sass/scss

    P
    moe•220
    Submitted about 1 month ago

    Anything helps!


    1 comment
  • Newsletter Signup - BEM, Sass, JS


    P
    moe•220
    Submitted about 2 months ago

    2 comments
  • FEM Article Prev. Component


    P
    moe•220
    Submitted about 2 months ago

    1 comment
  • Meet Landing Page w/ Flexbox + Grid

    #sass/scss

    P
    moe•220
    Submitted 3 months ago

    1 comment
  • CSS Grid Testimonials

    #sass/scss

    P
    moe•220
    Submitted 4 months ago

    Any feedback helps!


    1 comment
  • FEM Four Card Feature w/ CSS Grid + BEM Methodology

    #bem#sass/scss

    P
    moe•220
    Submitted 4 months ago

    Any feedback on my BEM methodology, my use of Grid and also Media Queries would be appreciated! Thank you for viewing! <3


    1 comment
View more solutions

Latest comments

  • P
    Kellen James•350
    @Kellenkjames
    Submitted about 2 months ago
    What are you most proud of, and what would you do differently next time?
    • Architecting a full MVC-lite system in vanilla JS that cleanly separates state, rendering, and interaction.

    • Building a fully responsive design system with SCSS tokens, fluid typography, and semantic mixins.

    • Debugging layout overflow edge cases down to sub-300px viewports — and solving them with precision.

    • Writing clean, modular code that mirrors Angular’s architecture — without relying on a framework.

    What challenges did you encounter, and how did you overcome them?
    • Plan a design system audit earlier to prevent hardcoded spacing or typography overrides.

    • Validate external asset paths (data.json, images) for production during initial setup.

    • Set flex-wrap: wrap as a default utility and override only when absolutely needed.

    • Possibly include unit tests or localStorage to introduce persistence and further separation of concerns.

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

    Not seeking additional help at this time but feedback is welcome.

    Responsive dashboard UI built with modular SCSS and state-driven JS

    #bem#sass/scss#accessibility
    1
    P
    moe•220
    @jellmoo
    Posted about 1 month ago

    Looks great!

  • Abimbola•200
    @Abimzz
    Submitted about 2 months ago
    What are you most proud of, and what would you do differently next time?

    I'm happy that i was able to finish the project and i would love to do it in a shorter time next time.

    What challenges did you encounter, and how did you overcome them?

    i had issues with the following:

    • with postioning the li::marker
    • the success msg layout on mobile
    • the js for the email validation
    • with debugging JavaScript

    and i solve all of them with many tutorial videos.

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

    Any suggestions on efficiency or to streamline my code would be appreciated.

    newsletter sign up with success message main

    2
    P
    moe•220
    @jellmoo
    Posted about 2 months ago

    Strengths:

    Well-structured HTML with semantic elements and proper form handling

    Good mobile-first approach with thoughtful breakpoints that work across devices

    Consistent use of custom properties and logical class naming

    Email validation works correctly with appropriate user feedback

    Good UX flow: Smooth transition between signup and success states, with proper form reset

    Areas to Improve:

    Remove commented-out code blocks and unused attributes to improve readability

    Could benefit from visual styling for invalid input states and better accessibility features

    Fix the typo in error message class name and consider removing unused styles

    Minor optimizations like moving regex patterns outside event handlers

    Add ARIA attributes and better screen reader support for error states

    Some hover effects and transitions could be smoother and more consistent

  • EDrick-her•30
    @EDrick-her
    Submitted about 2 months ago
    What are you most proud of, and what would you do differently next time?

    Proud to have completed it and to have worked through each of the challenges I faced as the project progressed. If I had to do it differently, I would aim to complete it faster. I took a long time, and every time I skipped a day of studying, I would forget what I had done previously. So, a key takeaway for me is to stay consistent.

    What challenges did you encounter, and how did you overcome them?

    There were two main challenges: using matchMedia to handle responsive images, and preventing the default "Enter" behavior in forms. I also enjoyed working with classList, which was new for me. I overcame these obstacles by reading documentation and with the help of ChatGPT, which guided me especially with methods I had never seen before, like matchMedia

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

    To be honest, I still need a great deal of practice, especially with JavaScript. There are many methods I’m not yet familiar with, which often causes me to get stuck. I spent quite a bit of time figuring out how to use event.preventDefault it was a challenge, mostly due to syntax errors. Nevertheless, I’m ready to move forward to the next project

    Proyecto de suscripción a newsletter

    #accessibility
    2
    P
    moe•220
    @jellmoo
    Posted about 2 months ago

    Strengths:

    • Good responsive design with mobile/desktop image switching

    • Proper form validation with visual feedback

    • Clean CSS grid layout

    • Accessible form structure with fieldset/legend

    Areas for Improvement (JS):

    • There's commented-out broken code that should be removed

    • The regex pattern has an error: \$ should be $

    • Missing semicolons in some places

    • The comeBack() function uses window.location.href which will cause a page refresh

    • The email doesn't show on the success page.

    Marked as helpful
  • P
    George•180
    @GeorgeGit1
    Submitted about 2 months ago

    Css , JS

    1
    P
    moe•220
    @jellmoo
    Posted about 2 months ago

    Well done!

  • P
    Kumani Kidd•170
    @amancalledkidd
    Submitted 4 months ago
    What are you most proud of, and what would you do differently next time?

    The application of fluid typography and space using utopias tool (https://utopia.fyi/). This reduced the need for break points and allowed for a much more fluid/responsive design. I was happy with the application but I think the structure of my scss could be better. Also the ratios for the fluid type and spcae could be better, so I will work on this next time.

    What challenges did you encounter, and how did you overcome them?

    The Fluid space was the most difficult as there was not much infomation online. I used a combination of different sources alongside trial and error to get it working. Then I had to figure out the best practices to keep the overall structure understandable.

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

    Any one who is applying cube css have any recommendations?

    Any general suggestions or ways for me to improve would be greatly appreciated!

    Responsive meet landing page, using scss and Cube css methodology

    #cube-css#sass/scss
    1
    P
    moe•220
    @jellmoo
    Posted 3 months ago

    Strengths:

    Variable Usage:

    • The use of variables for colors, spacing, and typography is excellent. This makes it easy to maintain and update styles.

    Responsive Design:

    • The media queries are well-placed, ensuring that the layout adapts to different screen sizes.

    Area for improvments:

    Image Alt Attributes:

    • Some images have empty alt attributes. It's important to enhance accessibility.
  • P
    moe•220
    @jellmoo
    Submitted 4 months ago
    What specific areas of your project would you like help with?

    Any feedback helps!

    CSS Grid Testimonials

    #sass/scss
    1
    P
    moe•220
    @jellmoo
    Posted 4 months ago

    oops need to add quotation img to the desktop version! **

View more comments
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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Oops! 😬

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

Log in with GitHub