Strapi demo to determine architecture

[aboydnw]

Context

The goal is to determine architectural direction for the CMS integration. We are assuming that we will move forward with a Strapi integration. We can use the template instance to prototype, test, and demo.

[snmln]

In flight Demo PR for visibility: NASA-IMPACT/next-veda-ui#54

[aboydnw]

@snmln posting my thoughts on what this demo should contain, but I know you are already in progress so feel free to tell me if you have a different plan.

1. Prototype should integrate with the template instance
2. Users should be able to view a list of existing stories
3. Users can add a new story and define some metadata and content
4. Metadata just has to be the minimum required to publish a story (I think just ID and name?)
5. Content can include multiple blocks of different types
6. New stories can then be saved and appear in the list of stories

Nice to haves for this prototype:

1. Some sort of status on stories, or somehow indicate which ones are published and which ones are not, even better would be to be able to push unpublished stories to production (does staging vs production really exist for the template instance?)
2. Some indication of what a block would look like with a custom VEDA Component, like a map. Doesn't have to be actually functional, but some idea what that might look like
3. Somehow showing what this would look like for non-mdx pages
4. CMS is somehow password protected. Cheapest way would be best here, I think we will eventually integrate with VEDA Auth

Things I'm ambivalent about for the prototype but we'll have to do eventually either way:

1. We'll need to do this for both datasets and stories. If we get both for free now, great. If you'd rather do datasets now, that's fine too.
2. Uploading images, linking to videos, other website-buidling things.
3. All the other story metadata like hero image, description, topics, etc
4. Editing existing stories. Again, if we get it for free, great. If not, showing we can add new stories should give confidence we can figure out the editing.

[aboydnw]

I'm starting to build out a backlog here but I'll wait to see where this demo goes before making too many tickets.

[snmln]

Thank you for this Anthony! I have the bulk of these items completed at the moment. I do have one question, could you provide some additional clarification on what we are anticipating with metadata?

Is this taxonomy and metadata of the specific story or web metadata used to more specifically inform search engine web crawlers?

[aboydnw]

I was picturing taxonomy and metadata for the story mdx file, but I suppose both might be relevant. We've had a backlog item to somehow improve SEO performance, but our lighthouse scores on that front have not been terrible so we haven't prioritized spending time on it yet.

So the metadata at the top of the mdx files would be top of mind for me, like this one.

---
featuredOn:
  - eis
id: "fire-life-cycle"
name: Hydrological Drivers and Impacts of Fire
description: "NASA's Earth Information System investigates pre-fire hydrological conditions and post-fire impacts on eco-hydrology"
media:
  src: ::file ./fire-cover.png
  alt: Satellite imagery (false color) of East Troublesome fire spreading to the Rockies
  author:
    name: Lauren Dauphin/Landsat 8
    url: https://eoimages.gsfc.nasa.gov/images/imagerecords/147000/147452/coloradofire752_oli_2020296_lrg.jpg
pubDate: 2023-01-25
taxonomy:
  - name: Topics
    values:
      - Wildfire
      - Fire Severity 
      - Fire Risk 
      - Fire Impacts 
      - Hydrology 
      - Debris Flow
  - name: Source
    values:
      - NASA EIS
---

[snmln]

Linked here is a short recording of the Strapi Demo: https://drive.google.com/file/d/1RWPBtCkIs4M2V3ad-5zq1y0SIO7Fu34D/view?usp=sharing

And the associated PR: NASA-IMPACT/next-veda-ui#54

[aboydnw]

Thanks @snmln I think we could probably move this into Ready for Review, especially if you think it's ready for @hanbyul-here and @ajinkyakulkarni to get some eyes on it

This will be good context to have heading into next week's meeting on next steps

[snmln]

Related Pr: NASA-IMPACT/next-veda-ui#54

Context for your reviews, after a recent meeting with leadership there has been some minor directional shift. We are shifting CMS focus on enabling the MDXeditor in various CMS solutions that the instances have selected. So moving forward we are pausing the Strapi efforts for the time being. With that background if you could review this work with solutions towards optimizing the API fetch layer and extracting it to wrap the veda front-end rather then inject it into the individual pages.

Meeting Recording: https://docs.google.com/document/d/1QbNf87Modm028VMxE4SMDXuJq22sdM7LCp0onYtVAow/edit?usp=sharing

[snmln]

Closing this ticket while Strapi initiative is paused.