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.
In this instalment I will show you how to dynamically render any page from WordPress based on the URL in our AngularJS app. This becomes useful when your team’s Content Creator creates new pages, we don’t have to add anything new to our front-end.
In this post I am going to show you how to build a rapid prototype web application using AngularJS on the front-end and WordPress on the backend. This first article will just be a primer to get WordPress and your application communicating. It should take you no more than 1/2 an hour. In future posts I will get into more detail about structuring your dynamic application.