When you serve your application that we’ve been making over the past 6 instalments, you’ll notice that the title and meta description tags are empty. We could set them to a static default, but they’d be the same on every page. This wouldn’t be terribly useful to your visitors, nor would it help when it came to SEO (search engine optimization) and how we appear on the SERP’s (search engine results page) would be less than desirable.
In part 7 of this series we will make a meta service that will set the title and meta description tags dynamically, determined by the title on content of the page that is currently being served.
In part 6 I will show you how to reuse that sitemap data to create a dynamic footer which links to all the page that don’t render in the navigation by default.
In this post I will show you how to reuse the sitemap data to create an always up to date, dynamic sitemap that is in sync with your navigation. This is a super short article.
In this post I am going to finish what we started in part 3 by putting the finishing touches on our navigation with active state, drop-down items and more. It won’t be a long post, but after the epic that was part 3, I am sure you’ll be fine with that.
In part 3 of this series I am going to show you how I tackled the dynamic navigation problem. I’m not going to lie, this part of the solution isn’t ideal but short of extending the WP REST API Plugin to return navigation objects (which is something I will look into when I have time), this solution is the best I could come up with.