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

In-browser markdown editor Next.js, TS, Redux

next, react, redux, typescript
P
Elina Shelest•150
@evengene
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?
  1. In this project I used MongoDb Atlas for the first time so that the docs could be stored there. I had to learn how to use it and how to connect it to my project.
  2. I also used Vercel Functions to create a serverless api to handle the requests to the database (/save, /delete, etc.) This was also a first for me.
  3. I created an architecture for the project that is easy to understand and navigate. I have a separate folder for the components, hooks and utils functions.
  4. I'm using createSlice from Redux Toolkit to manage the state of the app. It is better because it is more concise and easier to understand than the traditional Redux.

Since this app is more for learning purposes, I have added a limit of 5 notes that can be created. Potentially in the future I could add a login system and a way to save more notes for particular users.

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

Challenges and how to overcome them:

  1. The first challenge was to find a way how to save docs. I could use a local storage but I wanted to work with a database. I found MongoDb Atlas to be very popular.
  2. The second challenge was to create a serverless api to handle the requests to the database. I used Vercel Functions for this.
  3. Other challenges include creating more elegant way to handle styles changes for the theme switcher and to make the app more responsive since the layout is different on desktop/mobile.

I see a potentially ways to refactor the project more and will be updating it as the time goes.

What specific areas of your project would you like help with?
  1. What do you like about the project?
  2. What can be done better?
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 Elina Shelest'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 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.