Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 3 years ago

Multi-Page Website Using TailwindCSS, Leaflet API, & Swiper.JS

tailwind-css
Nyrell Leonor•400
@nyrellcl
A solution to the Arch Studio multi-page website challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Finally finished this multi-pager. This was my first official project that I completed using TailwindCSS. I did start small projects to get a feel of how to approach the design process with using tailwind, but it wasn't anything worth publishing, just sandboxing.

However, this one was a very satisfying challenge to complete. Using tailwind with this project, introduced me to a lot of new concepts and ways to restructure my design process. With tailwind, approaching projects at a mobile-first approach is vital. Of course, it is good practice to do so, whether or not you are using tailwind, but this framework really pushes that.

Given that it's my first project using tailwind, I'm certain syntax and structuring could use a lot ore refinement, that's why I am 100% open to any and all suggestions regarding that area. As well as any improvements to how to best make the project more efficient and easy to understand.

I did try out the bonus challenge for the mapping part. I used leaflet.JS API as suggested in the challenge. I find utilizing APIs a very fun challenge and something I want to get much better at using. Additionally, I used swiper.JS for the slider part of the home page.

For some reason, github pages wouldn't render all my files, only partially. So i had to publish it through netlify and connect my github repo. If there's a way to shorten that process, please let me know. I initially had a "dist" folder for all my html files and css file, but for some reason github wouldn't process it, so i had to move them all to the root folder of my project. Which solved the problem and I was able to publish everything.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Nyrell Leonor's solution.

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 all CSS, SCSS and Less files in your repository.

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.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.