Switch from local data to Sanity

[tinymachine]

• Place all current data calls in index.astro instead of spread throughout components. #11
• Determine correct GROQ query to retrieve project data (including referenced image metadata for the 'stills') and add the query as a comment on this issue below
• Install Astro's Sanity plugin?
• Replace .md files with Sanity as data source
  • Update About section
    • Image
    • Social and other links
    • Text
  • Update Reel (and stills) at top of page
  • Update projects
    • Fetch projectSet data from Sanity
    • Loop through projectSets to display projects in correct groupings and order
• Remove any unused npm packages (e.g. @sanity/image-url, @sanity/visual-editing)

[tinymachine]

Reel query:

*[_type=="reel"][0]

or (with image dereferenced)

*[_type=="reel"][0] {
  ...,
  placeholderStills[]{
    ...,
    asset->
  }
}

Settings query:

*[_type=="settings"][0] {
  ...,
  projectSets[]->
}

About query:

*[_type=="about"][0]

or (with image dereferenced)

*[_type=="about"][0] {
  ...,
  image{
    ...,
    asset->
  }
}

with null check

*[_type == "about"][0] {
  ...,
  image != null => { 
    "image": {
      ...image,
      "asset": image.asset->,
    }
  }
}

Project sets query:

*[_type=="project"][] {
  ...,
  projectSet->,
  featuredStill {
    ...,
    asset->
  },
  stills[] {
    ...,
    asset->
  }
}

[tinymachine]

Reference GROQ from my other project that you can modify:

  *[_type == "household" && isActive] {
      ...,
      photo != null => { "photo": {
        ...photo,
        "dimensions": photo.asset->metadata.dimensions,
        "url": photo.asset->url,
      }}
    } | order(primarySurname asc, primaryAdultFirstNames asc)

[OshanBathiya]

Custom renderPortableText Function VS Astro Portable Text

renderPortableText function can only render

• Text
• Bold
• Italic
• Links

while Astro Portable Text package can handle

• Headings, Nested lists, Custom blocks, Code, Images and more.

astro-portabletext