Static Content

So - you’ve used one of the approaches here on Train-ee.com to build dynamic navigation from posts in an ExpressionEngine weblog—but now you want to mix in a link to a different page type - say a contact form.  And, you want this link to be sorted in the middle of the navigation items coming from weblog posts.  How to do that?

Here’s a fourth way to build navigation for static content in ExpressionEngine, using one weblog, one template, no categories, and relationships.  Previously I’ve posted 3 other ways to do this on a mini-site.  The advantages to this newest approach is everything can be contained in one weblog, using one template, no categories, and one relationship field.  Here’s a working example of this approach.

This is the fourth installment in a series on building static content areas using the native functionality in ExpressionEngine. 

In this post I’ll show an alternate method of presenting three-level content in EE.  The navigation model in this approach is less like traditional navigation and more like a weblog in that the category (2nd) level pages uses the main content area for blurbs with “Read More >>“ links to the detail (3rd) level content. I use this approach sometimes because I like how it gives the user more detail as you move through the site.  It’s also a nice way to get around needing category-index level content that often times says nothing more than “below this page are three more pages”. 

This is the third installment in a series on building static content areas using the native functionality in ExpressionEngine.  Previously I’ve covered a simple two-tier approach for content with an “index and sub-page” structure.  Then I covered how to use EE categories to add a third level into the sub-navigation.  That approach uses categories to organize the sub-navigation, but doesn’t provide true second-level category content. In this post I’ll show how to add that second level content using another EE template.

Previously here on Train-ee.com I showed how simple two-tier static content could be presented using native ExpressionEngine functionality.  This article builds on that approach to use EE categories to add another level of navigation to static content.

This is one of those times where the flexibility of EE really shows, as I quickly came up with three different ways to do this, using one, two and three templates respectively.  In this post I’ll cover the single EE template approach, and follow this up with the more complex approaches.