search

department-of-veterans-affairs / va.gov-cms

Editor-centered management for Veteran-centered content.
https://prod.cms.va.gov
GNU General Public License v2.0
97 stars 69 forks source link

[Events] SPIKE: Feasibility of automating event data files for every event list #10003

Open ryguyk opened 2 years ago

ryguyk commented 2 years ago

Status

[2024-08-01] [Fran] Michelle has asked if Daniel can add more details/explain this so we can decide if it remains on the Events v3 Initiative.

Description

See: https://dsva.slack.com/archives/C52CL1PKQ/p1659368011029689?thread_ts=1659363371.092899&cid=C52CL1PKQ

The desire is for something similar to KISS, but automated for every event list (event_listing) node. (and possibly other nodes) rather than explicitly defined in the KISS config file. As noted in the linked Slack comment, the data would be available at an endpoint like this: https://www.va.gov/bay-pines-health-care/events/json

Not blocking work elsewhere, research results may lead to bigger implementation later.

CMS Team

Please check the team(s) that will do this work.

jilladams commented 2 years ago

Relevant for https://github.com/department-of-veterans-affairs/va.gov-cms/issues/9576 as well.

swirtSJW commented 2 years ago

I think we want to change "but automated for every VAMC System node" to be "but automated for every event list (event_listing) node." Most right now are in the VAMC systems, but that will be changing as we roll events out to VBA and VetCenters.
Event list pages can theoretically be created anywhere in the site and are not currently restricted to VAMC systems, they were just the first product to need/use them.

davidmpickett commented 1 year ago

Something to include in your KISS knowledge share? @ryguyk