In-browser markdown editor - HTML, SCSS, TypeScript, localStorage, RWD
Design comparison
Solution retrospective
I am proud of the TypeScript stuff I have made to code the way of converting Markdown to HTML and implement some tests trying to follow the principles of TDD. Event though my implementation is basic, I am anxious to later develop my Markdown-to-HTML script to take more advanced and complex syntax and situations into consideration.
What challenges did you encounter, and how did you overcome them?To display the markdown editor, I first used the textarea
element, but I wanted to expand it all over the available height. The easiest way to do it is to use the field-sizing: content
CSS declaration; but, the field-sizing
property is not supported by Firefox and Safari (Firefox 131- and Safari 18- at the time when I wrote these lines). So, instead of textarea
, I used a div
with the contenteditable
attribute set to "true"
.
I was also quite hard to find a way of hiding the sidebar and the preview without any overflow using grid layout at the same time. It cost me quite much time, but I managed to overcome that.
What specific areas of your project would you like help with?Feel free to give me feedback about the class I coded to manage the Markdown-to-HTML conversion and about the tests I implemented.
Community feedback
- @dylan-dot-cPosted 27 days ago
This seems perfect! I'm impressed with how the code is organized and how the design and animations look.
I'm not much of a pro so I don't have much to offer in terms of feedback, but I would like to connect and learn from you.
I'm planning to get premium but only when I reach like 1k points. I would appreciate if you could give me some feedback on some of my challenges.
Well done again!
0
Please log in to post a comment
Log in with GitHubJoin 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