You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue involves creating an "Our Story" page (to go under the About section on the website) using the new infrastructure we've been building on the CMS side of things. The purpose of this process is to set up a system whereby non-tech team members can input text, images, and other content into our CMS (Forestry) in an organised way and then pass it off to coders on Github to rapidly turn it into a page.
Overall Page
File path: Path: content/pages/our-story.md
This instance of the generic page template should contain the following field/information:
As you can see, there are two "content sections" that we want to appear on this page. I'll include screenshots of the CMS side of things below, though this shouldn't be necessary for future issues of this type.
Content Section 1
This content section will be a banner image to appear at the top of the page.
The content section has metadata and a single content block:
This is the metadata:
This is the content block itself. Note that caption is blank because we want this to be a banner photo with no visible caption.
Content Section 2
The content section has metadata and a few content blocks:
This is the metadata:
You can find the data for the other four content blocks should be available in the file path. Since there are four of them, I won't screenshot them to include them here. Not that the metadata for the content section says how to arrange them: 1 column top-to-bottom in order.
The timeline requested here already exists on the site. It's currently on the About Us page (which will continue to exist). We'd like to move it from that page to this page and make sure it's connected with the content/pages/our-story.md timeline fields in our CMS so we can edit timeline entries from there.
Front end feature screenshots
This is the general idea. Note that the fonts, spacing, etc. are not precisely chosen for this rough mockup.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Description
This issue involves creating an "Our Story" page (to go under the About section on the website) using the new infrastructure we've been building on the CMS side of things. The purpose of this process is to set up a system whereby non-tech team members can input text, images, and other content into our CMS (Forestry) in an organised way and then pass it off to coders on Github to rapidly turn it into a page.
Overall Page
File path: Path: content/pages/our-story.md
This instance of the generic page template should contain the following field/information:
As you can see, there are two "content sections" that we want to appear on this page. I'll include screenshots of the CMS side of things below, though this shouldn't be necessary for future issues of this type.
Content Section 1
This content section will be a banner image to appear at the top of the page.
The content section has metadata and a single content block:
This is the metadata:
This is the content block itself. Note that caption is blank because we want this to be a banner photo with no visible caption.
Content Section 2
The content section has metadata and a few content blocks:
This is the metadata:
You can find the data for the other four content blocks should be available in the file path. Since there are four of them, I won't screenshot them to include them here. Not that the metadata for the content section says how to arrange them: 1 column top-to-bottom in order.
The timeline requested here already exists on the site. It's currently on the About Us page (which will continue to exist). We'd like to move it from that page to this page and make sure it's connected with the content/pages/our-story.md timeline fields in our CMS so we can edit timeline entries from there.
Front end feature screenshots
This is the general idea. Note that the fonts, spacing, etc. are not precisely chosen for this rough mockup.
Code of Conduct
The text was updated successfully, but these errors were encountered: