-
Notifications
You must be signed in to change notification settings - Fork 153
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
Move /opportunity pages to /initiatives #2971
Comments
Looping @anilkanji in on this for approval... I think this is something Jesse started a while ago. Originally, most staff would create pages under /campaign or /opportunity. But then a decision was made to use /initiatives instead of /opportunity (sorry, I don't have anymore insight into this but assuming it's because Initiatives sounds more accurate and is broader than Opportunity). The intention was to then sunset /opportunity but it just never happened, but only because of neglect and lack of prioritization. So now things are spread across both /opportunity and /initiatives and it's confusing to know which pages should go where. Sooo I think the time has come to move things over and sunset /opportunity. You ok with that? @alanmoo do you have any more context to add? Would you be able to socialize this with staff once it's happened? |
To confirm - we're moving over /opportunity pages over to /initiatives? Sounds good. Alan flagged the need for a broader IA review. |
RIP Long live /initiatives |
I'm going to suggest a manually coded URL redirect rather than doing this in the Wagtail dashboard since there are so many pages. Let's set up the appropriate urls.py file to redirect anything at |
Good plan! |
@kristinashu is this considered as part of the bigger IA work? If so, it's better that we tackle it along with other IA dev tickets (when they are ready for implementation). |
@mmmavis this is something we're wanted to do for a very long time and I think the longer we leave it the more confusing and more work it will be to undo it later. So I don't think it should be blocked by the other IA work. Do you have any concerns about it? |
@kristinashu can you clarify what you meant by "archive /opportunity"? |
I mean that users should no longer be able to create pages under "opportunity" so it shouldn't even show up as an option to a users in the CMS. |
PR for redirecting pages under
@kristinashu do you know when will be a good time to do this? |
@mmmavis I can probably move the pages over next week. What to assign the ticket to me until I've done this? |
@kristinashu done assigning! Right before you start moving the pages next week, can you let the engineering team know so we can be ready to merge and push the redirect PR live? |
I can help with the manually move but I'm not comfortable running backend/database commands myself. Is there any concern with moving pages manually? |
Just that there are a lot of pages 😭, especially considering the sub- pages and translations. And I thought Pomax said there was a way to do it, but maybe I misunderstood. |
@cadecairos - we have 18 wagtail pages and all their subpages to move and set up redirects. We're hoping to not do it manually. Is this something you or Lucie might be able to help do? I wonder if Wagtail has a tool for bulk page management - I've seen that in other cms. |
Wagtail has a management command that can be run to move pages: http://docs.wagtail.io/en/v2.0/reference/management_commands.html#move-pages @Pomax can you coordinate running this command? |
Yay! 🎉 @Pomax just helped moving all pages under I'll file a PR for the cleanup work (e.g., update fake data script etc) |
w00t! Thank you so much for save me hours and hours of work! Also thank you for helping clean up the CMS and making it easier for all staff to use. |
Yes! Please remove it. |
Done! Thanks all! 🎉 |
awesome! 🥇 thanks all for making that happen! |
At some point we decided to no longer use /opportunity and use /initiatives instead. Now we have projects arbitrarily split between both which is more confusing and complicated for staff and users.
Next steps:
The text was updated successfully, but these errors were encountered: