Wire meetups to hosted community API#12
Open
Elvis020 wants to merge 2 commits into
Open
Conversation
Elvis020
commented
Jun 20, 2026
Elvis020
commented
Contributor
- Add a remote-first meetup loader that fetches the DevCongress Community public API, normalizes the hosted JSON into the existing Astro meetup shape, resolves relative remote assets against the community app, and falls back to local YAML when the API is unavailable.
- Update the home page, all-meetups index, meetup detail routes, and shared meetup section to consume the normalized loader instead of reading the meetups collection directly.
- Document the hosted meetup API environment variables and add manual plus twice-weekly GitHub Pages rebuild triggers so static deploys can refresh published meetup data without a content commit.
- Update the generated Astro meetup schema metadata for location.url/location.label and verify the site with pnpm build.
- Add a remote-first meetup loader that fetches the DevCongress Community public API, normalizes the hosted JSON into the existing Astro meetup shape, resolves relative remote assets against the community app, and falls back to local YAML when the API is unavailable. - Update the home page, all-meetups index, meetup detail routes, and shared meetup section to consume the normalized loader instead of reading the meetups collection directly. - Document the hosted meetup API environment variables and add manual plus twice-weekly GitHub Pages rebuild triggers so static deploys can refresh published meetup data without a content commit. - Update the generated Astro meetup schema metadata for location.url/location.label and verify the site with pnpm build.
Contributor
Author
|
Don't merge yet...need to update with migrated url |
Use the migrated Events Management public origin for meetup data and relative assets instead of the retired devcongress-comm Worker and Pages hosts. Keep a single optional EVENTS_MANAGEMENT_ORIGIN build variable so admins can redirect the static build without changing code if the Events Management deployment moves. Update the README to document the new source endpoint and GitHub Actions variable. Verification: pnpm build; EVENTS_MANAGEMENT_ORIGIN=https://events-management.pages.dev pnpm build.
Contributor
Author
|
updated the PR to use the migrated event-mangement repo under devcongress but you will need to add this as an additional step..I created a fallback in the code but just in case the url changes..we can change via github instead of codebase Name: EVENTS_MANAGEMENT_ORIGIN Path: This lets the website static build fetch meetup data from the Events Management public API: Let me know if anything |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.