Skip to content
OverviewSolutions
17
Comments
15

tortiman

@tortiman270 points

I’m a mysterious individual who has yet to fill out my bio. One thing’s for certain: I love writing front-end code!

Latest solutions

View more solutions

Latest comments

  • Lê Mạnh Đan•400
    @DanKRT-Star
    What are you most proud of, and what would you do differently next time?

    I'm most proud of building a fully responsive news homepage that adapts seamlessly across screen sizes—from mobile to desktop—using only semantic HTML, modern CSS (Flexbox & Grid), and a touch of JavaScript. The mobile menu interaction is accessible, animated smoothly, and works with both mouse and keyboard, which was a big focus for me.

    What I would do differently next time is:

    Refactor the JavaScript to be more modular and readable, especially as logic grows (e.g., trap focus inside the menu).

    Explore using :focus-visible instead of :focus to improve accessibility without visual noise for mouse users.

    Use CSS variables for spacing and typography too, not just colors, for better scalability.

    Possibly structure the CSS with a preprocessor like SCSS to maintain larger stylesheets more efficiently.

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

    One of the biggest challenges was implementing a mobile navigation menu that is both visually smooth and accessible to screen readers and keyboard users. Managing the toggle logic with aria-hidden and ensuring that focus transitions correctly between elements took some experimentation.

    Another challenge was balancing between Flexbox and CSS Grid for different screen sizes. I initially tried using only Grid but realized that Flexbox provided more flexibility for stacking content on mobile. Switching to a hybrid layout helped resolve those layout issues.

    I also had to carefully manage focus states for accessibility—ensuring :focus outlines were visible and meaningful while keeping the design visually clean. Testing with the keyboard helped me identify which elements needed better focus styles or tabindex.

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

    I'd love feedback on:

    How to further improve the accessibility of the mobile navigation menu, especially things like focus trapping inside the menu when it's open.

    Best practices for CSS architecture (e.g., BEM, utility-first, or component-based structure) as projects grow.

    Ideas to make the homepage more dynamic—like adding theme toggles or user-preference features—while keeping performance and accessibility in mind.

    Whether using a framework (like React or Vue) would have benefited a project of this size—or if plain HTML/CSS/JS is preferred for static sites like this.

    Responsive homepage using flexbox, grid

    #accessibility
    1
    tortiman•270
    @tortiman

    you have to improve the design

  • FR-UX-EN•240
    @FR-UX-EN
    What are you most proud of, and what would you do differently next time?

    Applying more accessibility features! Tried my best to refactoring JS code to make it clean and collaborative.

    Responsive contact form

    #accessibility#sass/scss
    1
    tortiman•270
    @tortiman

    very good

  • Tel•270
    @telsabate-hub
    What specific areas of your project would you like help with?

    I would very much appreciate any suggestions that could improve my skills.

    Thank you!

    FAQ Accordion Using SCSS/SASS

    #accessibility#sass/scss
    1
    tortiman•270
    @tortiman

    very well

  • tortiman•270
    @tortiman

    very well

  • Yamien Ariel•210
    @ariel172
    What are you most proud of, and what would you do differently next time?

    I'm most proud of how I managed to refactor my JavaScript code into small, reusable, and readable functions. It really improved the clarity and maintainability of my code. I also made sure to follow a mobile-first approach and handle form validation properly with clear feedback for the user.

    If I had to do it differently next time, I would separate my logic into multiple JavaScript modules from the start, to make the project even more scalable and organized. I’d also consider implementing unit tests.

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

    One of the main challenges I faced was managing form validation and error feedback without making the code messy or repetitive. At first, I was duplicating logic across several event listeners. To overcome this, I refactored my code by creating reusable functions like recupererValeurInput() and verifierChamp() to keep things clean and modular.

    Another challenge was handling responsive design properly. I followed a mobile-first approach and then used media queries to adjust the layout for larger screens, making sure everything looked good at each breakpoint.

    I also had to ensure that all user interactions were intuitive — like showing real-time error messages and enabling/disabling the reset button dynamically. I used a combination of condition checks and helper functions to solve these issues effectively.

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

    I would appreciate feedback on the following areas:

    JavaScript code structure: Are there ways I could improve the organization of my functions or reduce coupling between logic and DOM manipulation?

Form validation: Does my current validation logic follow best practices for maintainability and accessibility?

Responsive design: I used a mobile-first approach and added a desktop layout using media queries — is my implementation flexible enough for all screen sizes?

CSS structure and naming conventions: I used BEM-like class naming in French — is this clear and consistent for others to read and maintain?

    Any suggestions on how to further improve clarity, modularity, or performance are very welcome!

    tip calculator developed by Ariel Yamien

    #accessibility
    1
    tortiman•270
    @tortiman

    good

    Marked as helpful
  • tortiman•270
    @tortiman

    incorrect design and don't use forEach in Javascript

View more comments