Review test coverage and augment / strategize as needed.

[zenlex]

Don't think there'll be much logic to unit-test here. I'd like to see some component tests for our markdown translation and some basic UI e2e test suites to handle automating regression testing in the future.

[zenlex]

Test coverage initial goals (will take Techlahoma Hacktoberfest PR for each task)

Browser Tests:

• Blog index route loads and shows blog card components
• Blog post route loads and displays a post
• Blog index next and prev buttons work
• Blog index does not create card for empty or malformatted blog object
• Events index route loads and shows event card components
• Event detail loads and displays an event page
• Event index next and prev buttons work
• Event index route does not create card for empty or malformatted event object
• Connections page loads and shows links to meetup, slack, github, and twitter
• Projects index page loads and shows project carousel
• Project index does not create card for empty or malformatted project object

Component Tests:

• Blog index card correctly displays blog metadata
• Event index card correctly displays event data
• Project card correctly displays project data with clickable links
• Nav menu collapses to hamburger correctly on mobile
• Dark / light mode toggles work on all components

Unit/Feature tests

• Markdown Blog files parsed into blog posts correctly
• Markdown blog files parsed into blog index cards correctly
• Markdown Event files parsed into event pages correctly
• Markdown Event files parsed into event index cards correctly
• Markdown Project files (repo readmes) parsed into Project cards correctly

Integration Tests:

• Build step fetch of project data from CFT Project repo readme.md files
• Meetup data fetch for events
• Twitter data fetch for widget

[laylark]

I'll work on some of the blog browser tests.