Skip to content

Case Studies should be a separate Table #124

Description

@samjam48

Currently, we use a hard-coded implementation to render a case study by just going to a specific row (e.g. 85) in the projects table and that data is filled in as a case study instead of a project like the other objects in that table.

Instead, we should have a table that is purely for case studies and then we only ever show the first three studies from that table and Generation Change can update them as they like.

  • Create case_studies table in airtable db
  • Copy relevant data from projects_table into the case_studies table
  • Create Netlify call to poll the airtable db for just the case_studies on home screen
  • Change hard-coded reference to project_table rows and use dynamic first three case_studies data
  • Remove case study data from the projects_table

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions