dsschapira / saber-ball-blog Goto Github PK

After discussing with client - we don't want a subscribe button. The functionality is very rarely used and it is better to just tweet out links to the new post.

Maybe a random post button???

Below the pagination buttons, it would be nice to show the title of the next post this will lead to.

Create a search results page. This will be a separate page template from the already existing ones,

Currently, the excerpt for the post cards on the homepage is pulled from the excerpt that Wordpress generates from a created post. They use the beginning of a post to generate this excerpt. This comes with a few issues:

1. If something like a getty image embed is used, it will include the tag line to the image embed.
2. The beginning of a post may just be a lead-in and not give a solid idea of the posts content.
3. Even if a beginning of a post is fairly descriptive, an Excerpt can be used to draw users in more reliably if it is specifically crafted.

Create the post archive page.

Determine how to build the archive footer - should it be dynamically built or use some of the WP admin functionality and require user input?

The filters on the home page are currently hard coded categories. These should instead pull dynamically from the categories built in wordpress.

Implement using the search query WP API on form submit from the navbar.

In part of refactoring the state/store, make sure the app knows whether you go to the home page from the brand header button. If you do, go to the top of the page.

Add support for featured images to be used on the post cards on the home page.

Can't see the google adsense ads included until we move this to a live version (or I'm at least not aware of how to get this working on a non-live version).

Should create div boxes to house the ads for when we do go live or at least setup the positioning for where they will be.

Need to decide how user interaction should work.... we have 2 options.

1. Pre-started tweet @SaberBallBlog with a link to the post/page.
2. Comments pulled from and pushed to Wordpress.

I'm leaning towards twitter. It is quicker to implement, and will probably have higher user engagement than trying to get people to log into a Wordpress or blog-specific account. Can come back later as an enhancement to add blog-specific comments and use social media account integration for it.

Should add an active class to the navbar when we are at the correct page.

Add social media share buttons to the post pages.

The site's WP api integration should be refactored. Currently, we re-query the WP backend every time we head to a new route. The store state should be setup in the App component so that the sub-components don't need to keep re-querying.

Need to add pagination to the single-post pages.

The pagination should keep track of which view you entered from. If you go from most recent, continue on in that order, but we should filter to the correct category if they entered from a category filter.

Currently, the archive links in the footer are static. They should update as posts are added. Limit the number of links to the current number so the footer doesn't grow too large.