Coding an Advent Calendar: Day 10
This year, I decided to create an Advent Calendar website in HTML5, CSS3, and JavaScript. My hopes for the site are to showcase some of my frontend development abilities as well as make something fun, functional, and reusable.
Day 10
- Finish Lynda.com videos
- Today I finished the Lynda.com Course Learn React.js: The Basics. Here are a few of the biggest takeaways from the Course:
- React IS actually incredibly fast
- React syntax may be new (to me) but doesn’t feel unfamiliar (it’s a kind of XML)
- React sites are built with React Components (each with
props
andstate
) - Each React Component has a “lifecycle” (mounting, updating, and unmounting)
- React Components can utilize parent-child relationships
- Get all React Components working
- After a bit of debugging and editing, I was able to get (my version of) each of the React Components in the Lynda.com Course working – including in Storybook. I’ve also updated by public Gist on the basics to include correct syntax and comments.
I noticed two of my most common errors in my original React syntax were:
- If you want to string together functions separated by commas, like an Object (i.e.
getInitialState() {...}, componentWillMount() {...}, render() {...}
, then you MUST use the React Native syntax (var MyComponent = React.createClass() {...}
) and NOT ES6 syntax nor the stateless functional syntax. - For some reason, I’d accidentally had an extra closing curly bracket
}
after myrender()
function – this was producing the “horrible error message” I mentioned yesterday. But at least now I learned what to look for the next time.
- If you want to string together functions separated by commas, like an Object (i.e.
- Begin creating a Christmas Scene
- Finally, I started putting everything together into a kind of Christmas “scene” (as evidenced by the Featured Image on this Post). I DEFINITELY feel like React is useful for creating parent-child relationships between Components and for allowing me to dynamically create, add, or remove Components based on the code.
For example, the image above was created using code for
Scene.js
(the parent Component) andGift.js
(the child Component).Scene.js
calledGift.js
25 times and looped through it to create 25 separate Components – each with its own unique ID and properties. This will definitely prove to be useful when I start looking into pulling in blog Posts from WordPress using the WP REST API.
Work Completed (to date)
- December 10, 2016
- Finish Lynda.com videos
- Get all React Components working in Storybook
- Begin creating a Christmas Scene
- December 9, 2016
- Learn and use Create-React-App
- Learn and use Storybook for developing React Components in isolation
- Update npm and node and figure out my git process between Windows and Mac
- December 8, 2016
- Use React and Babel via CDN to get it working “locally”
- Install React developer Tools for Chrome
- Create very basic React.js pages to learn it
- December 7, 2016
- Pull post data with the WP REST API in WordPress core!!
- Write structural code for the React Component to be rendered
- Install and setup BabelJS to compile the React code
- December 6, 2016
- Add README.md
- Add a GitHub Issue to hold usable images
- Add LICENSE
- December 5, 2016
- Create a GitHub repository and full site files for easier management
- Setup Grunt.js to compile my Sass into CSS
- Begin blogging about the process
- December 4, 2016
- Countdown clock (JS Date class & jQuery Easing) with SVGs
- Dynamic text output for Year based on the current date
- CSS only slider (off by 5px each slide)
- December 3, 2016
- CSS bow & ribbon
- Footer with FontAwesome presents
- Hover, active, and “Christmas Day” styles for footer presents
- December 2, 2016
- React.js + Axios.js initial code structure
- Color palette
- CSS → Sass
- December 1, 2016
- Let it snow
- Typography choices
- CSS presents (first design)
- Design notes menu