FRONTPAGE - OUR EVOLVING STORY SECTION NOTES:

This is a single wordpress post (an article) that could be displayed within our front-page section "our evolving story"  at anytime - illustrating how our front page can introduce new content as the organization communicates its story. The query embedded in this section allows us to present any published article to the public (curated as defined by organizational protocols) as we see fit.

On a development note, we are pulling 'post' content into the page dynamically from posts tagged with the 'featured' tag - utilizing the built in 'tag' taxonomy of Wordpress. To add or remove a tag from any post, use the wordpress classic editor to perform this function.  (Even though this article or post content is being assembled in Cornerstone, there is  no mechanism to assign a wordpress 'tag' - to do so, you must open the post on the back-end in the standard wp-post editor) Therefore, to add or remove any article from the frontpage's "our evolving story" section, you first must add/remove the tag "featured" from the specific post and then pay attention to the following.

To achieve the content and layout of the "our evolving story" section, we are using Cornerstone's looper provider placed on the row "tale winds" looping through a query providing the data string of the posts tagged with 'featured'. The tagged articles are sorted as to publishing date but this sort can be altered were a special need arise. The amount of "featured articles" can be unlimited, however, the display number is fixed within the looper consumers of two layout structures. Note: only the current articles being featured on the frontpage should be carry the 'featured' tag to reduce resource time for the initial looper providing the query request. Limiting the number of articles on the frontpage to the most recent two seems to make sense right now.

UNDERSTANDING THE LAYOUT DISPLAY

1. TOP LINE ARTICLE

Our looper consumer is placed on the column TOP LINE ARTICLE and is set to consume 1 post.  The layout is text left column / image right column. The data being consumed by the layout is TEXT.

1. post title  '{{'dc:post:title'}}'

2. last update:  '{{'dc:post:modified_date'}}'

3. excerpt - lead line  '{{'dc:post:excerpt'}}

NOTE the excerpt can carry simple <p> html tags for formatting

IMAGE right - a ACF META DATA FIELD named FRONTPAGE BLOG   '{{'dc:acf:post_field field="frontpage_blog"}}  a custom image for the article's archived display that is minimally square or possessing a greater vertical height as opposed to width - preferred aspect ratio 4:5 or fallback 1:1  Ideal pixel 520x650

NOTE the image height is determining the overall height of the section row containing the post's information - text column is using flexbox for vertically centering column's text

2. SECONDARY ARTICLE ARTICLE

Our looper consumer is placed on the column SECONDARY ARTICLE and is set to consume 1 post (here is where we would alter presenting more frontpage articles greater than our default 2 by increasing the amount of looper consumption).  The layout is image left column / text right column. The data being consumed by the layout is TEXT.

1. post title  '{{'dc:post:title'}}'

2. last update:  '{{'dc:post:modified_date'}}'

3. excerpt - lead line  '{{'dc:post:excerpt'}}'

NOTE the excerpt can carry simple <p> html tags for formatting

IMAGE right - a ACF META DATA FIELD named FRONTPAGE BLOG   '{{'dc:acf:post_field field="frontpage_blog"'}}'  a custom image for the article's archived display that is minimally square or possessing a greater vertical height as opposed to width - preferred aspect ratio 4:5 or fallback 1:1  Ideal pixel 520x650

NOTE the image height is determining the overall height of the section row containing the post's information - text column is using flexbox for vertically centering column's text

Articles (posts) written specifically for "our evolving story" will be published and archived under the category Our Evolving Story / slug 'our-evolving-story and archived PAGE Our Evolving Story with custom META category page link affixed in classic wordpress post editor