Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
18
Comments
19
P
Kyle Mulqueen
@kmulqueen

All solutions

  • Responsive news homepage HTML/CSS/JS


    P
    Kyle Mulqueen•400
    Submitted 12 days ago

    I'd really like to revisit the desktop layout, particularly making the "New" stories section more fluid across larger screen sizes. The three-article grid at the bottom also needs work to handle the image-to-text proportions better across different breakpoints.


    1 comment
  • Responsive and accessible contact form with validation

    #accessibility

    P
    Kyle Mulqueen•400
    Submitted 16 days ago

    I'd appreciate input on whether my form validation approach follows standard practices, or if there are better patterns I should be using. Specifically interested in feedback on the Map-based approach for handling input-to-error-message relationships.


    1 comment
  • Responsive FAQ Accordion with only HTML/CSS


    P
    Kyle Mulqueen•400
    Submitted 21 days ago

    Best practices when using absolute positioning for items.


    1 comment
  • Rating Component with React, TypeScript, and Tailwind CSS

    #accessibility#react#tailwind-css#typescript#vite

    P
    Kyle Mulqueen•400
    Submitted 25 days ago

    Context-API and state management patterns. Also I would appreciate feedback on my Tailwind CSS usage. I think that has been improving but I'm still not sure I'm using utility and component classes correctly.`


    1 comment
  • Frontend Quiz App - React, TypeScript & Tailwind

    #accessibility#react#tailwind-css#typescript#vite

    P
    Kyle Mulqueen•400
    Submitted 26 days ago

    TypeScript best practices.


    1 comment
  • Password Generator using TypeScript, React, Tailwind


    P
    Kyle Mulqueen•400
    Submitted about 2 months ago
    1. Optimization of the password generation algorithm to ensure truly random and secure passwords.
    2. Advanced accessibility testing methodologies beyond basic keyboard navigation.
    3. Better TypeScript patterns for complex state management.
    4. Performance optimization techniques for React component rendering.

    1 comment
  • Tip Calculator App HTML/CSS/JS


    P
    Kyle Mulqueen•400
    Submitted about 2 months ago
    • Testing strategy: Implementing unit tests for calculation functions to verify accuracy with edge cases like zero values and decimal precision

    • State management: Refactoring to a more structured approach using a central state object or module pattern instead of separate variables

    • Input validation: Enhancing error handling with more descriptive user feedback for different error conditions

    • Accessibility verification: Testing with actual screen readers to ensure ARIA implementations and dynamic updates work correctly

    • Browser compatibility: Ensuring consistent form behavior across different browsers, especially regarding form state persistence


    1 comment
  • Responsive Time Tracking App HTML/CSS/JS


    P
    Kyle Mulqueen•400
    Submitted about 2 months ago
    1. Performance Optimization - Reducing unnecessary re-renders and DOM manipulations
    2. Code Organization - Better separation of concerns between data, UI, and event handling
    3. Responsive Design - More thorough testing across different viewport sizes

    1 comment
  • Responsive Newsletter Signup Form HTML/CSS/JS


    P
    Kyle Mulqueen•400
    Submitted about 2 months ago

    Form validation without using a library. How did others go about applying the error styles effectively?


    1 comment
  • Responsive Article Preview Component HTML / CSS / JS


    P
    Kyle Mulqueen•400
    Submitted about 2 months ago
    1. Creating a more elegant solution for the speech bubble styling that works well across all screen sizes

    2. Improving my CSS Grid implementation to better handle complex layouts

    3. Implementing smooth transitions/animations when toggling the visibility of elements

    4. Developing a more comprehensive focus management system for better keyboard accessibility


    1 comment
  • Responsive Meet landing page HTML/CSS


    P
    Kyle Mulqueen•400
    Submitted 2 months ago

    I'd appreciate feedback on:

    1. Performance optimization for the responsive images implementation
    2. Best practices for cross-browser compatibility, especially for overflow handling
    3. Ways to improve accessibility for the text overlaid on images
    4. More elegant solutions for creating spacing between grid items
    5. Techniques for testing that the correct responsive images are loading at different breakpoints

    1 comment
  • Responsive Testimonials section using CSS Grid


    P
    Kyle Mulqueen•400
    Submitted 2 months ago

    Specific areas where I'd like help

    I would appreciate guidance on:

    1. Best practices for organizing grid items without heavy reliance on nth-child selectors
    2. Techniques for creating more accessible decorative elements that enhance design without impacting usability
    3. Approaches to streamline responsive layouts with fewer media queries
    4. Strategies for making the layout more resilient to content changes and additions

    1 comment
  • Responsive 4 Card Section using CSS Grid


    P
    Kyle Mulqueen•400
    Submitted 2 months ago

    I'd appreciate guidance on implementing fluid typography more effectively. While I've used clamp() functions for responsive text sizing, I'm unsure if my approach is optimal. Additionally, I'm interested in learning more efficient methods for maintaining consistent spacing ratios across different screen sizes. Finally, I'd welcome feedback on my CSS organization, particularly whether my text preset system could be structured more efficiently.


    1 comment
  • Responsive product card component using HTML & CSS


    P
    Kyle Mulqueen•400
    Submitted 2 months ago

    I'd appreciate guidance on:

    1. Typography scaling - my use of clamp() for responsive font sizing led to compounding effects with my CSS custom properties
    2. Best practices for SVG implementation - particularly controlling color and size efficiently
    3. More accessible markup patterns for product cards - ensuring my component follows best practices for screen readers and keyboard navigation

    1 comment
  • Responsive recipe page using HTML & CSS


    P
    Kyle Mulqueen•400
    Submitted 3 months ago

    Areas I'd Like Help With

    1. Responsive Design Feedback - I'd appreciate input on how my layout adapts to different screen sizes and if there are better practices I could implement.

    2. CSS Organization - I'm interested in learning better ways to organize my CSS for maintainability as projects grow larger.

    3. Performance Optimization - Are there any ways I could optimize my HTML/CSS for better performance?

    4. Accessibility Review - I've focused on semantic HTML, but I'd like feedback on other accessibility aspects I might have missed.

    5. Browser Compatibility - I'd like to ensure my solution works across all modern browsers and gracefully degrades in older ones.


    1 comment
  • Social links profile using HTML & CSS


    P
    Kyle Mulqueen•400
    Submitted 3 months ago

    I would appreciate feedback on:

    1. Accessibility: Are there any ways I could improve the accessibility of my social links? Is my current approach with unstyled but semantic lists and links following best practices?

    2. Responsive design: Does my solution maintain proper proportions across different screen sizes? Are there any breakpoints I should add or adjust?

    3. CSS organization: I tried to keep my CSS organized, but I wonder if there are better ways to structure it. Would a methodology like BEM have been beneficial for this project?

    4. Performance optimization: Are there any unnecessary CSS rules that could be removed or combined to improve loading performance?


    1 comment
  • Blog preview card using HTML & CSS


    P
    Kyle Mulqueen•400
    Submitted 3 months ago

    Areas Where I'd Like Feedback

    CSS Transition Best Practices

    I'm seeking guidance on:

    • Whether my implementation of transitions follows current best practices
    • If there are performance considerations I should keep in mind with CSS animations
    • How to effectively combine multiple transitions for more complex interactions

    Interactive Design Principles

    I'd appreciate feedback on:

    • Whether my hover effects enhance or potentially distract from the user experience
    • If the visual feedback provided is sufficient for users to understand interactivity
    • How I might improve the accessibility of these interactive elements

    Component Structure

    While I've implemented the blog card component successfully, I'd like to know:

    • If my HTML structure effectively supports the intended interactions
    • Whether there are opportunities to make the component more reusable
    • If there are additional states (focus, active, etc.) I should be considering beyond hover

    1 comment
  • Responsive QR Code using HTML & CSS


    P
    Kyle Mulqueen•400
    Submitted 3 months ago

    Areas Where I'd Like Feedback

    CSS Organization and DRY Principles

    I'm seeking guidance on striking the right balance with my CSS classes. I want to:

    • Keep my code DRY (Don't Repeat Yourself) through thoughtful class creation
    • Avoid overdoing utility classes which might lead to "div soup" with too many classes
    • Establish a maintainable pattern for styling components

    Stylesheet Readability

    I'd appreciate feedback on whether my CSS stylesheet is:

    • Organized in a logical, intuitive way for other developers
    • Structured to make it clear where new styles should be added
    • Commented appropriately to explain complex or non-obvious styling decisions
    • Following naming conventions that make the purpose of styles clear

    HTML Optimization

    While I've improved my semantic HTML structure, I'd still like to know:

    • If there are additional accessibility enhancements I could implement
    • Whether there are SEO opportunities I'm missing in my markup
    • Whether the document structure could be further optimized for screen readers

    2 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

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