Add teaching resources to clusters

[LukasWallrich]

Link to other resources beyond the reading list

Add buttons below sub-cluster description which open up these resources above the readings.

For each view, highlight top resources per cluster - top 5, then show more. Do rough pass now, then ask specialists to correct

Explain "specialist resources" on hover

Data sources:

• Lesson plans & slides: https://forrt.org/lesson-plans/ plus new list from @max-fw
• Syllabi: from website https://forrt.org/syllabus/
• Games: https://docs.google.com/spreadsheets/d/1cmydWjD1OuyKxJVfDlv0N3T474zwymfB04yFDZQO-TY/edit?gid=610093275#gid=610093275

Deduplicated across sources:

• Reading is only in the clusters
• Any syllabus is only in syllabi
• Lesson plans there
• And only the remainder in curated resources

Make sure sub-clusters without resources are not shown (@flavioazevedo, I removed "study design" that had only a repeated study)

[flavioazevedo]

Add sub-cluster-specific resource buttons to the Clusters page

Summary

Add a section for additional resources at the bottom of each sub-cluster on the FORRT Clusters page.

These resources must be associated with the individual sub-cluster, rather than with the broader cluster or the Clusters page as a whole. Depending on what is available for a particular sub-cluster, users may see one or more resource-category buttons, such as:

• Lesson Plans

• Slides

• Curated Resources

• Educators’ Corner

• Games and Activities

• Syllabi

• Summaries

• Other relevant FORRT resources

Not every sub-cluster will have resources from every category. The interface should display only the categories for which resources are available.

Intended user experience

At the bottom of each expanded sub-cluster, display a clearly labelled section such as:

Additional resources for this sub-cluster

Below this heading, show one button for each available resource category.

For example:

Lesson Plans (3) Slides (2) Curated Resources (5)

When a user clicks a button, the page should reveal the resources belonging to that category and sub-cluster. This could use an expandable panel, accordion, or another accessible disclosure component.

Each displayed resource should include, where available:

• Resource title

• Short description

• Link to the resource

• Author or contributor

• Resource type or format

• Relevant accessibility or language information

The resources should appear within the sub-cluster section so that it remains clear that they are specifically related to that sub-cluster.

Display logic

1. Resource buttons appear only when at least one resource has been assigned to the sub-cluster.

2. Only categories containing resources are displayed.

3. A sub-cluster may have one, two, three, or more resource-category buttons.

4. Each button should optionally show the number of available resources.

5. Clicking a button reveals only the resources in that category for that sub-cluster.

6. Clicking the button again should collapse the resource list, unless another established interaction pattern is used consistently.

7. If no additional resources are available, the additional-resources section should not be displayed.

8. Resource buttons and expandable content must be keyboard accessible and use appropriate ARIA attributes.

9. The layout should work on both desktop and mobile, with buttons wrapping onto additional lines where necessary.

Data source and back-end requirements

The Clusters page is populated from a Google Sheet. The additional resources should follow the same data-driven approach rather than being entered manually in the website code.

The Google Sheet should contain sufficient information to connect each resource to:

• A unique cluster

• A unique sub-cluster

• A resource category

• The individual resource

A separate sheet or tab, such as Subcluster Resources, could contain fields similar to:

Field | Purpose -- | -- cluster_id | Stable identifier for the parent cluster subcluster_id | Stable identifier matching the relevant sub-cluster resource_category | For example, Lesson Plans, Slides, or Educators’ Corner resource_title | Title displayed to users resource_url | Link to the resource resource_description | Optional short description resource_author | Optional author or contributor information resource_language | Optional language information resource_format | Optional format, such as PDF, slide deck, webpage, or activity display_order | Optional ordering within the category active | Whether the resource should currently be displayed

Stable identifiers should be used instead of matching sub-clusters solely by their visible names. This will prevent links from breaking when sub-cluster wording is edited.

The website should:

1. Read the additional-resource records from the Google Sheet.

2. Group the records by subcluster_id.

3. Within each sub-cluster, group the records by resource_category.

4. Generate the appropriate category buttons dynamically.

5. Display the corresponding resources when users activate a button.

6. Ignore incomplete or inactive records without causing the rest of the page to fail.

7. Handle duplicated entries and invalid URLs appropriately.

Suggested data structure

Conceptually, the processed data could follow this structure:

Sub-cluster
├── Existing scholarly references
└── Additional resources
    ├── Lesson Plans
    │   ├── Resource 1
    │   └── Resource 2
    ├── Slides
    │   └── Resource 3
    └── Educators’ Corner
        ├── Resource 4
        └── Resource 5

Acceptance criteria

• Each sub-cluster can be associated with zero or more additional resources.

• Additional resources are retrieved from the Google Sheet.

• Resources are associated using a stable sub-cluster identifier.

• A separate button is generated for every available resource category.

• Categories without resources are not displayed.

• Activating a button reveals the correct resources for that sub-cluster and category.

• Resources from one sub-cluster never appear under another sub-cluster.

• Sub-clusters without additional resources do not display an empty section.

• Resource counts are accurate when shown on buttons.

• Buttons and expandable panels are keyboard and screen-reader accessible.

• The feature works on mobile and desktop layouts.

• Adding or removing a row in the Google Sheet updates the page without requiring changes to the website code.

Rationale

The Clusters page currently provides the conceptual structure and scholarly evidence associated with each sub-cluster. This feature would connect that evidence base to FORRT’s practical educational materials.

Placing the buttons directly within each sub-cluster will allow educators to move from understanding a topic to finding materials they can use to teach it, while preserving the specificity of the taxonomy. It will also make relevant FORRT resources more discoverable without presenting users with categories or materials unrelated to the sub-cluster they are viewing.

## Add sub-cluster-specific resource buttons to the Clusters page

Summary

Add a section for additional resources at the bottom of each sub-cluster on the [FORRT Clusters page](https://forrt.org/clusters/).

These resources must be associated with the individual sub-cluster, rather than with the broader cluster or the Clusters page as a whole. Depending on what is available for a particular sub-cluster, users may see one or more resource-category buttons, such as:

• Lesson Plans
• Slides
• Curated Resources
• Educators’ Corner
• Games and Activities
• Syllabi
• Summaries
• Other relevant FORRT resources

Not every sub-cluster will have resources from every category. The interface should display only the categories for which resources are available.

Intended user experience

At the bottom of each expanded sub-cluster, display a clearly labelled section such as:

Additional resources for this sub-cluster

Below this heading, show one button for each available resource category.

For example:

Lesson Plans (3) Slides (2) Curated Resources (5)

When a user clicks a button, the page should reveal the resources belonging to that category and sub-cluster. This could use an expandable panel, accordion, or another accessible disclosure component.

Each displayed resource should include, where available:

• Resource title
• Short description
• Link to the resource
• Author or contributor
• Resource type or format
• Relevant accessibility or language information

The resources should appear within the sub-cluster section so that it remains clear that they are specifically related to that sub-cluster.

Display logic

1. Resource buttons appear only when at least one resource has been assigned to the sub-cluster.
2. Only categories containing resources are displayed.
3. A sub-cluster may have one, two, three, or more resource-category buttons.
4. Each button should optionally show the number of available resources.
5. Clicking a button reveals only the resources in that category for that sub-cluster.
6. Clicking the button again should collapse the resource list, unless another established interaction pattern is used consistently.
7. If no additional resources are available, the additional-resources section should not be displayed.
8. Resource buttons and expandable content must be keyboard accessible and use appropriate ARIA attributes.
9. The layout should work on both desktop and mobile, with buttons wrapping onto additional lines where necessary.

Data source and back-end requirements

The Clusters page is populated from a Google Sheet. The additional resources should follow the same data-driven approach rather than being entered manually in the website code.

The Google Sheet should contain sufficient information to connect each resource to:

• A unique cluster
• A unique sub-cluster
• A resource category
• The individual resource

A separate sheet or tab, such as Subcluster Resources, could contain fields similar to:

Field	Purpose
cluster_id	Stable identifier for the parent cluster
subcluster_id	Stable identifier matching the relevant sub-cluster
resource_category	For example, Lesson Plans, Slides, or Educators’ Corner
resource_title	Title displayed to users
resource_url	Link to the resource
resource_description	Optional short description
resource_author	Optional author or contributor information
resource_language	Optional language information
resource_format	Optional format, such as PDF, slide deck, webpage, or activity
display_order	Optional ordering within the category
active	Whether the resource should currently be displayed

Stable identifiers should be used instead of matching sub-clusters solely by their visible names. This will prevent links from breaking when sub-cluster wording is edited.

The website should:

1. Read the additional-resource records from the Google Sheet.
2. Group the records by subcluster_id.
3. Within each sub-cluster, group the records by resource_category.
4. Generate the appropriate category buttons dynamically.
5. Display the corresponding resources when users activate a button.
6. Ignore incomplete or inactive records without causing the rest of the page to fail.
7. Handle duplicated entries and invalid URLs appropriately.

Suggested data structure

Conceptually, the processed data could follow this structure:

Sub-cluster
├── Existing scholarly references
└── Additional resources
    ├── Lesson Plans
    │   ├── Resource 1
    │   └── Resource 2
    ├── Slides
    │   └── Resource 3
    └── Educators’ Corner
        ├── Resource 4
        └── Resource 5

Acceptance criteria

• Each sub-cluster can be associated with zero or more additional resources.
• Additional resources are retrieved from the Google Sheet.
• Resources are associated using a stable sub-cluster identifier.
• A separate button is generated for every available resource category.
• Categories without resources are not displayed.
• Activating a button reveals the correct resources for that sub-cluster and category.
• Resources from one sub-cluster never appear under another sub-cluster.
• Sub-clusters without additional resources do not display an empty section.
• Resource counts are accurate when shown on buttons.
• Buttons and expandable panels are keyboard and screen-reader accessible.
• The feature works on mobile and desktop layouts.
• Adding or removing a row in the Google Sheet updates the page without requiring changes to the website code.

Rationale

The Clusters page currently provides the conceptual structure and scholarly evidence associated with each sub-cluster. This feature would connect that evidence base to FORRT’s practical educational materials.

Placing the buttons directly within each sub-cluster will allow educators to move from understanding a topic to finding materials they can use to teach it, while preserving the specificity of the taxonomy. It will also make relevant FORRT resources more discoverable without presenting users with categories or materials unrelated to the sub-cluster they are viewing.