Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 7 months ago

Bookmark Landing Page using Tailwind, Astro and Sass

accessibility, astro, sass/scss, tailwind-css
P
Kamran Kiani•2,780
@kaamiik
A solution to the Bookmark landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

Proud of:

  • Successfully integrating Tailwind CSS for the first time while maintaining a balanced approach between utility classes and custom CSS
  • Creating a comprehensive landing page that covers various CSS techniques
  • Building responsive layouts that work across different devices
  • Achieving a minimal and clean design aesthetic

Do differently next time:

  • Plan a better strategy for Tailwind configuration upfront
  • Create a more structured approach to deciding when to use utility classes vs. custom CSS classes
  • Establish a more consistent pattern for managing styles across components
  • Set up a design system using Tailwind's theme customization earlier in the project
What challenges did you encounter, and how did you overcome them?

Main challenges:

  1. Tailwind Integration:
  • Challenge: Balancing between utility classes and custom CSS
  • Solution: Used Tailwind as a complementary tool rather than forcing everything into utility classes
  1. Technical Implementation:
  • Challenge: Creating a responsive tabbed interface
  • Solution: Implemented custom CSS Grid and flexbox layouts combined with Tailwind utilities
  1. Responsive Backgrounds:
  • Challenge: Making background images responsive while maintaining design integrity
  • Solution: Utilized responsive design patterns and careful consideration of breakpoints
What specific areas of your project would you like help with?
  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
Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • khalagai•370
    @khalagai
    Posted 7 months ago

    First time I am coming across Astro. Your solution is great. I will clone this and study it.

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.

Oops! 😬

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

Log in with GitHub