loading...
Cover image for React Rebuild, React Router and Git, Oh My!

React Rebuild, React Router and Git, Oh My!

alexlsalt profile image Alex Morton Updated on ・2 min read

This post was originally published on October 20, 2020 on my blog.

Happy Tuesday! I'm feeling good - I'm going to be rewriting my Ladies Code Collective (currently just HTML/CSS/JS) into a React app!

I'm really excited about it because I've been practicing and getting more and more used to React Router.

Also, I'll be able to successfully pull my podcast episode data from an API. I was just running into way too many complications trying to do it with a static ol' site.

Anyway, I just finished up mapping out my component/app structure (with pencil, paper, and highlighters, mind you!) and I'm ready to get straight to it.

Sketches of React components on paper

Getting the structure onto paper first helps so much in just getting a clear picture in your mind - I love it.

So often, I get way too ahead of myself and want to start in on the code as soon as possible - only to inevitably come up against several early organizational obstacles.

Also! I consider myself to be very comfortable with Git, but the thing is - I only commit and push my code changes to the main production branch.

Starting now, I'm going to be pushing to development branches and merging from there.

Updates to come! Wish me luck!


P.S. Did you know I have a podcast with new episodes each Wednesday? Go listen right over here >>

The Ladies Code Collective Podcast cover art

Discussion

pic
Editor guide
Collapse
dana94 profile image
Dana Ottaviani

I need to start drawing my components out on paper before the coding step - really helps in the long run.

Yeah, best get into creating feature branches for everything, it helps if you ever need to reverse some changes.

Collapse
alexlsalt profile image
Alex Morton Author

Yeah, it's so nice! Once you have the structure in front of you, it's so easy to just code along with it :D