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

Markdown Master: Next.js & Tailwind

next, tailwind-css
P
Skyz Walker•1,215
@Skyz03
A solution to the In-browser markdown editor 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?

I am most proud of being aware of the vast ecosystem of libraries available and utilizing their awesome ideas to build this project effectively. Leveraging these libraries not only streamlined the development process but also enabled me to focus on creating a polished and feature-rich application.

If I were to do things differently next time, I would spend more time in the initial planning phase to explore alternative libraries and tools that could further optimize the application. Additionally, I would incorporate more user feedback earlier in the development cycle to ensure the features align even better with user needs.

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

One of the challenges I encountered was ensuring proper synchronization of Markdown content. At times, changes in the editor were not reflected in the preview as expected. To overcome this, I implemented a debouncing mechanism to handle rapid updates efficiently and ensured that the state management was robust and reactive, allowing seamless updates between the editor and the preview.

Another challenge was troubleshooting issues with dark and light mode styling while utilizing module.css. S

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

I would appreciate help specifically with refining the theming implementation. While the current setup using module.css and theme-specific classes works, there might be more efficient or modern approaches that could improve maintainability and performance. For example:

Dynamic Theming: Suggestions on utilizing CSS-in-JS libraries (like styled-components or emotion) or frameworks with built-in theming support. Improved Theme Switching: Ideas for smoother transitions when toggling between dark and light modes. Best Practices for Module.css: Feedback on how to better organize and scope styles in module.css to avoid conflicts or unnecessary complexity. Additionally, I'd welcome creative ideas to enhance the overall user experience with theming—such as customizable themes, animations during theme switches, or accessibility improvements like high-contrast modes. Any feedback or resources to explore would be invaluable!

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 Skyz Walker'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.