Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate level of effort on keeping same Wagtail Instance #13429

Open
data-sync-user opened this issue Jan 28, 2025 · 0 comments
Open

Investigate level of effort on keeping same Wagtail Instance #13429

data-sync-user opened this issue Jan 28, 2025 · 0 comments

Comments

@data-sync-user
Copy link
Collaborator

data-sync-user commented Jan 28, 2025

Please investigate how much effort and what are some expected tasks if we were to follow through the option of keeping the same Wagtail instance for the new foundation website, with the following questions:

  • Annoying/difficult code maintenance and clean up? What conflicts will there be if we remain on the same instance?
    • Can old stuff be isolated? Like PNI?
    • Can we avoid cleaning up the current stack?
  • What are the benefits to remaining on the same instance as opposed to starting a new instance?
  • What are the draw backs?
  • Will we be able to start fresh and build the site the way we want? What are the constraints?
  • What’s possible from an ‘archive’ site perspective (can we keep old content up and accessible in some fashion? Can it remain on the same URL?
  • Will we need to migrate any content?
  • Long term maintenance concerns?
  • More doable deadline wise than starting a new instance?

┆Issue is synchronized with this Jira Task

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant