Three-Tier Static Content in ExpressionEngine: Approach C
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”.
Three-Tier Static Content in ExpressionEngine: Approach B
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.
Three-Tier Static Content in ExpressionEngine: Approach A
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.
No-Module-Required Static Content in ExpressionEngine
Here’s a “back to basics” tutorial for newcomers to ExpressionEngine - how to build a static portion of a website, with no plugins, extensions, or modules required.
While this has always been possible in EE, I think the popularity of Mark Huots “Tome" Module or the availability of the native EE Pages Module has mislead some folks into thinking that these modules are required for presenting static content in EE.
Nothing could be further from the truth - and in fact there are some advantages to sticking with native EE functionality for static content.
18 - Implementing the Beliefs Section
For any potential visitor using a church’s website to help make a decision of whether or not to attend, a Beliefs section is pretty important. Getting the corporate church beliefs posted on the website can also focus members on them in a way that’s not possible otherwise. In this chapter of the Building a Church Site on ExpressionEngine series, I’ll cover the implementation of the Beliefs section on the example website. From an ExpressionEngine perspective there is nothing notable about this chapter save for the speed at which it can be done - there isn’t any new ground here as far as coding approaches.
