Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
54
Comments
182
P
Kamran Kiani
@kaamiik

All solutions

  • Rest Countries Api using React and Tailwind

    #fetch#react#swr#tailwind-css#vite

    P
    Kamran Kiani•2,780
    Submitted 2 months ago

    Areas I'd like help with

    1. Performance Optimization

      • Best practices for reducing unnecessary re-renders
      • Strategies for optimizing API calls and caching
    2. State Management

      • When to use Context vs. Props vs. State Management Libraries
      • Better patterns for managing complex state
    3. Accessibility

      • Ensuring the application meets WCAG standards
      • Improving keyboard navigation and screen reader support

    1 comment
  • Mortgage Repayment Calculator using React Tailwind

    #accessibility#react#tailwind-css#vite

    P
    Kamran Kiani•2,780
    Submitted 3 months ago

    I'm looking for input on further optimization of state management and performance, ways to boost accessibility compliance, and strategies to improve project scalability.

    Feel free to share any additional thoughts or suggestions!


    2 comments
  • Product list Card using React, Tailwind and TypeScript

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

    P
    Kamran Kiani•2,780
    Submitted 4 months ago

    I would appreciate feedback on several specific areas of my project. First and foremost, I am looking for insights into whether there are any issues with my state management or component structure. I want to ensure that my use of the useState hook is optimal and that my components are designed for maximum reusability and clarity. Additionally, I’d like feedback on how I’ve implemented TypeScript in the project, particularly whether my type definitions and type safety practices are effective and maintainable. Furthermore, I would like to receive feedback on the accessibility features I implemented, particularly the aria-live announcements for screen readers. It’s important to me that my application is accessible to all users, so any suggestions for improvement in this area would be valuable. Lastly, I am open to any general advice on how I can enhance my code quality, whether through better practices, performance optimizations, or improved styling techniques.


    1 comment
  • Result Summary Component using react and tailwind

    #accessibility#fetch#react#tailwind-css

    P
    Kamran Kiani•2,780
    Submitted 4 months ago

    I would appreciate help with optimizing the application's performance, particularly in terms of improving responsiveness. Additionally, any advice on best practices for structuring larger React applications would be valuable as I continue to scale this project and others in the future.


    1 comment
  • Pomodoro App using Astro, Sass, Tailwind and Vanilla JS

    #accessibility#astro#sass/scss#tailwind-css

    P
    Kamran Kiani•2,780
    Submitted 5 months ago

    I would like help with optimizing the performance of the app, particularly in terms of reducing any potential layout shifts or flickers when loading user settings. Additionally, guidance on implementing a more robust state management solution would be beneficial, as it could improve the scalability and maintainability of the application. Lastly, any advice on further enhancing the app's accessibility features would be greatly appreciated.


    1 comment
  • Galleria Slideshow using Astro, Sass, Tailwind and Vanilla JS

    #accessibility#astro#cube-css#sass/scss#tailwind-css

    P
    Kamran Kiani•2,780
    Submitted 5 months ago

    I used Astro to build this project, including dynamic routes. I’d like to know if my approach is correct for creating multiple pages within a folder. Specifically, I added a [slug].astro file and used a data.json file to generate the pages.

    Regarding the CSS, is my implementation of the masonry layout correct?

    If you notice any other issues in my HTML, Accessibility, or CSS, I would appreciate your feedback on those as well.


    1 comment
  • Space Tourism Website using Sass, Tailwind and Astro

    #accessibility#astro#sass/scss#tailwind-css

    P
    Kamran Kiani•2,780
    Submitted 6 months ago

    I’d love to learn about alternative approaches to building this website. The project includes a data.json file, and I used Astro to develop it. I’m curious if there’s a more efficient way to manage the project with less code. For instance, I currently have four separate pages in the pages folder. Would it be better to use a single page and handle everything dynamically with the data.json file?

    I also made an effort to prioritize accessibility in my project, but there’s always room for improvement. If you notice any issues or have suggestions to enhance accessibility, I’d really appreciate your feedback.


    1 comment
  • Bookmark Landing Page using Tailwind, Astro and Sass

    #accessibility#astro#sass/scss#tailwind-css

    P
    Kamran Kiani•2,780
    Submitted 6 months ago
    1. CSS Best Practices:
    • Optimization of current CSS structure
    • Better ways to handle responsive backgrounds
    • More efficient approaches to component styling
    1. Accessibility Improvements:
    • ARIA attributes implementation
    • Semantic HTML structure
    • Keyboard navigation
    • Screen reader compatibility
    1. Code Organization:
    • Better separation of concerns between Tailwind and custom CSS
    • More efficient configuration setup
    • Component structure optimization

    1 comment
  • Room Homepage Master using Astro, Sass and cube css

    #accessibility#astro#cube-css#sass/scss

    P
    Kamran Kiani•2,780
    Submitted 7 months ago

    Feedback on CSS structure and animations would be very helpful. Suggestions on improving the CSS organization or refining the animations would be useful, especially if there are ways to make them more effective without extra complexity. Also, any recommendations for improving HTML, JavaScript, or accessibility would be appreciated, as these adjustments could enhance the code’s overall quality and accessibility.


    1 comment
  • Loopstudios Landing Page using Astro, Sass and CUBE CSS

    #accessibility#astro#cube-css#sass/scss

    P
    Kamran Kiani•2,780
    Submitted 7 months ago

    I would like feedback on the HTML structure, especially regarding semantic use, and on the accessibility features I implemented. Additionally, any insights into optimizing CSS for responsive layouts or suggestions on how to further refine my Sass and CUBE CSS code for maintainability would be valuable.


    1 comment
  • NFT Preview Card with Astro, Sass and CUBE CSS

    #accessibility#astro#cube-css#sass/scss

    P
    Kamran Kiani•2,780
    Submitted 7 months ago

    I’d appreciate feedback on the CSS code and methodology I’ve used, specifically if it's been applied correctly. Additionally, if you notice any issues with my HTML code or accessibility, please let me know. Your feedback is incredibly valuable to me.


    1 comment
  • Tic Tae Toe Game using Astro, Sass with Vanilla JS

    #accessibility#astro#sass/scss

    P
    Kamran Kiani•2,780
    Submitted 7 months ago

    I would appreciate feedback on accessibility and JavaScript code improvements. Specifically, I want to know if there are any areas where I could enhance the accessibility of my project, especially regarding screen reader support. I would also love to get feedback on my JavaScript logic, particularly around managing the game state and handling user interactions efficiently. Additionally, if you notice any other areas for improvement in my project, I would be grateful for your feedback!


    2 comments
  • BMI Calculator using Astro and sass

    #accessibility#astro#sass/scss

    P
    Kamran Kiani•2,780
    Submitted 8 months ago

    I would like help with CSS, accessibility, and the project’s JavaScript code. Feedback in these areas would be greatly appreciated to improve the overall quality and functionality of the project.


    1 comment
  • E-commerce Product Page using Astro, Sass and Vanilla JavaScript

    #accessibility#astro#sass/scss

    P
    Kamran Kiani•2,780
    Submitted 8 months ago

    I would like help with ensuring that my implementation of the lightbox and cart dialogs is as efficient and accessible as possible. Additionally, any feedback on improving the overall accessibility and responsiveness of the navbar would be greatly appreciated.


    2 comments
  • News Home Page using Astro and Sass

    #accessibility#astro#sass/scss

    P
    Kamran Kiani•2,780
    Submitted 8 months ago

    I’d like feedback on the accessibility aspects of my project, particularly regarding the implementation of the hamburger menu. I want to make sure it meets all accessibility standards and provides a smooth experience for users with assistive technologies.


    1 comment
  • Contact Form using Astro and Sass

    #accessibility#astro#sass/scss

    P
    Kamran Kiani•2,780
    Submitted 9 months ago

    I'd like feedback on any suggestions on how to improve the accessibility and responsiveness of the form. Specifically, I'd love to hear if there's a more efficient way to manage form validation and toast notifications in Astro or in React for future iterations of the project.


    1 comment
  • FAQ Accordion using Astro and Sass

    #accessibility#astro#sass/scss

    P
    Kamran Kiani•2,780
    Submitted 9 months ago

    I think the area where I need the most help is accessibility. One problem with accessibility is that the screen reader NVDA I used does not read content in Firefox, and I’m not sure why. Initially, when I did not use aria-polite, it did not read the content after expanding, even though I have aria-expanded in my code and linked my summary to the content with aria-controls. I want to know how I can solve this and what the problem in my code might be.


    1 comment
  • Interactive Rating Component Using Astro and Sass


    P
    Kamran Kiani•2,780
    Submitted 9 months ago

    I think accessibility issues is the most important part and html structure is important too.


    1 comment
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