Build .md content file structure

[mushon]

No description provided.

[mayarichman]

This will be based upon how we'd like the site to traverse the cards #9 .

We could collect the cards into subfolders based on the section of card titles (i.e. Risk Mapping, Make My Pact) so that the url includes this information pact-kit.org/risk-mapping/where-to-start.md. This is useful for the purpose of clarity and organization, but does not add any specific information to any one post.

We could also add a "category" to the meta data of each .md, such as Risk Mapping, and then in the post template only loop through and link to .md files with the same category.

[mushon]

@mayarichman, I think it actually makes sense to do both, no?
As far as categories we also have the numbering system (1.1, 1.2, 1.3…).
Do you guys think adding the category name to each card is also required?

[mayarichman]

Agreed. I think just adding a container category 1.x, 2.x will suffice. We should have custom title's for each card, but perhaps not categories.

---
layout: card
title: Risk Mapping
cardOrder: 1.1
categories:
- PACT Activities
---

---
layout: card
title: PACT intro
cardOrder: 1.2
categories:
- PACT Activities
---

[mushon]

Yes, that looks about right,
We should create at least one full card and try to make sure the structure makes sense and everything works before we get AI entering content.
I think other things to consider is the other special fields, like:

• goals
• methodology
• time span
• remember [array]
• materials
• link to download
• short link (for the 'more online' link in the print)
• content

*I'm thinking the 'More Online' section could just be a part of the content

@mayarichman @tingeber have I missed anything?

[tingeber]

Looks complete, we'll see if AI has additional insight, will update you

[mayarichman]

@mushon I added fields you mentioned above, except for the short link, and populated them with the card you filled out in this @cb0797ec79db1502277fd06fe0930db9fd379409. All cards have been added, all except Risk Mapping require both metadata and content.