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
In #523 and its subissues, we created generic "content blocks" for the website, like an image with a caption, a text area, or a Youtube embedded video. This set of issues involves creating "content sections," which are areas on the site that will house content blocks. The defining feature of a content section is that it is an area which horizontally covers the entire page of indeterminate vertical height.
The end vision is that non-tech people will be able to go into our CMS and input information in content blocks which are in turn in content sections, then pass a drawn up mockup of how they want the sections and blocks to be arranged on a web page via a Github issue.
A key piece of terminology to understand below is "banner" vs. "margined." A banner content section, like a banner image, should extend all the way to the edges of the screen when viewing the site on desktop. A margined section should appear with the natural margins on the sides of the page. An example of the banner style on the current site is https://distributeaid.org/routes/uk-to-france, and an example of the margined style on the current site is https://distributeaid.org/about-us/.
These are the following content sections we need:
(During triage turn these into separate issues)
Front end feature screenshots
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Description
In #523 and its subissues, we created generic "content blocks" for the website, like an image with a caption, a text area, or a Youtube embedded video. This set of issues involves creating "content sections," which are areas on the site that will house content blocks. The defining feature of a content section is that it is an area which horizontally covers the entire page of indeterminate vertical height.
The end vision is that non-tech people will be able to go into our CMS and input information in content blocks which are in turn in content sections, then pass a drawn up mockup of how they want the sections and blocks to be arranged on a web page via a Github issue.
A key piece of terminology to understand below is "banner" vs. "margined." A banner content section, like a banner image, should extend all the way to the edges of the screen when viewing the site on desktop. A margined section should appear with the natural margins on the sides of the page. An example of the banner style on the current site is https://distributeaid.org/routes/uk-to-france, and an example of the margined style on the current site is https://distributeaid.org/about-us/.
These are the following content sections we need:
(During triage turn these into separate issues)
Front end feature screenshots
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: