Request: I need to improve my “thinking in React” in terms of componentizing/composing everything. I also want to start organizing my CSS in a way that’s scalable for larger projects when they come. Critiques in these two veins, especially from those with experience in those two arenas, are highly and humbly requested.
- type in markdown, watch html come out.
- You can copy the HTML to the clipboard by pressing a button.
- You can resize either window to maximize or restore it.
Background: I came back to FCC after a few months away. Since the Beta had expired, I had the choice of cut/pasting all my prior work, or redoing the challenge waypoints. Things which I didn’t use out of unfamiliarity (ES6 syntax, array functions) became my primary purpose to master. It was great to see if I could outhack myself. In a similar vein, I am re-submitting my Front End projects after forcing myself to understand the Redux lessons, and having spent a lot of time reading the React documentation / Dan Abramov’s posts.
This Project: My Markdown Previewer I made in pure React (no Redux), and I initially had one Container component that was controlling all the JSX because I couldn’t see how to componentize it. This is a refactoring of that initial submission for the Beta. I’ve added comments to develop good habits for myself and to make your lives easier. Please tell me if the comments are lacking.
Update: Calling out mods I think I remember talking about working with React in a professional context for help. If I missed the mark, but you know someone who can guide me better, please do. @kevinSmith, @DanCouper. @others?