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

In Browser Markdown Editor created with NextJS

next, react, sass/scss
Minh Le•200
@ledminh
A solution to the In-browser markdown editor challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Another fun project to work on. This time, I decided to add some more features.

  • Shortcut: user can use shortcuts to perform most of the app's functionalities. Press Ctrl-Shift-? to see the list of shortcuts supported.
  • Save to localStorage.
  • Naming new file. This is my favorite feature.

More about naming new file

In Windows (or in any OS nowadays), right after you click a button to create a new file and before you give it a name, most likely its temporary name will be something like “new-file”, or ‘new-document’. If ‘new-file’ already exists, the name will probably be ‘new-file-1’. If ‘new-file-1’ is already exists, ‘new-file-2’ will be chosen.

I decided to add this feature to my app, with some modifications. When user created a new file but haven't saved it yet,its name will be 'new-file.md'. If there are 3 new files that has not been saved yet, their names will be 'new-file-1.md', 'new-file-2.md', 'new-file-3.md'. If user deletes 'new-file-2.md', the next new file will be named 'new-file-2.md' and the one created after that is 'new-file-4.md'

To implement this idea, I created a counter object that has 2 functions: getIndex and markRemove. Internally, it has an array of booleans. Each time a 'new-file-(i).md' is deleted, markRemove will be called to set the ith element of the array to false. Each time a new file is created, getIndex will be called and return the index of the first false element of the array. If all array's elements are true, getIndex will return the array's length.

In the future, I might upgrade it into full-stack by adding log-in function and register user will be able to save documents to database.

Please tell me what you think. Any suggestion for improvement is welcomed.

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 Minh Le'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

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.