On the Laravel side we'd use a url-slug field in the orgs model and then have a /orgs/{url-slug} route to render the order detail pages.
The existing Laravel orgs model already has the old full URIs for the orgs in a paths field, so it should be easy to run a manual query to popular the new slug field based on those old paths.
Bogdan suggested we could also put a list of upcoming events on these org detail pages.
We are in the process of replacing the old Drupal site that has housed the public facing organizations pages and API since 2016.
We want to maintain detail pages like https://data.openupstate.org/organization/hackgreenville
These have SEO value and we'd like to no break any links or bookmarks by 301 redirecting the old to the new.
https://data.openupstate.org/organization/hackgreenville https://hackgreenville.com/orgs/hackgreenville
On the Laravel side we'd use a url-slug field in the orgs model and then have a /orgs/{url-slug} route to render the order detail pages.
The existing Laravel orgs model already has the old full URIs for the orgs in a paths field, so it should be easy to run a manual query to popular the new slug field based on those old paths.
Bogdan suggested we could also put a list of upcoming events on these org detail pages.