[New Feature Launch]: Restructured Study Guides

[mon4our]

Product

Web (LaCE)

Brief description of the feature.

Restructure the current subtopic pages to have multiple sections and rename them to study guides.

Proposal

Link to the ProdOps Drive folder for this feature

https://drive.google.com/drive/folders/1u5_RaN-j4hZJ6W9IKl7yIIJ_rBnzG60Y

Expected code-complete date

2025 Q2

Developer point-of-contact

mon4our

Dev Leads

• mon4our
• kevintab95

Required roles for testing

• Curriculum admin

Feature flag name

show_restructured_study_guides

Link to the PR which moved the flag to the TEST feature stage

oppia/oppia#22798

Instructions for ProdOps Team

When you are assigned to this issue, please do the following. Tick each
checkbox item as you complete each step:

Tech-lead prep (to be done by a tech lead)

• Ensure that this issue is filed correctly. Ask for any missing info if needed.
• Ensure that the Drive folder is in the ProdOps Feature Launch folder and that it contains the pre-launch review doc, PRD, TDD, etc. (these should be the actual docs, not just shortcut links to them).
• Ensure that the "Information for Testers" page of the pre-launch review doc is fully filled in.- [x] Ask the developer and the relevant dev team leads to subscribe to this issue thread for updates, and ensure that they've done so.
• Verify that the "test stage" PR has been merged (see the "Link to the PR which moved the flag to the TEST feature stage" field), and that it actually moves the feature flag to the TEST stage.
• Once the "test stage" PR has been merged, deploy it to the backup-server.
• Enable the feature flag on the backup-server.
• Verify that the feature's CUJs actually work technically on the backup-server (with the flag enabled). Clarify any CUJs that aren't clear with the developer.
• Ensure that the ProdOps assignee has the correct permissions on the backup-server to do a dry-run of the feature.
• Hand off this issue to the ProdOps team (deassign yourself and tag/add the correct assignee from ProdOps).

Preparation and Dry-Run (ProdOps team)

• Verify that the Marketing team's tracker has a sheet for this product launch.
• Do a full run-through of the feature, and make updates to clarify the CUJ descriptions as needed. Then, post a new comment to this thread with the testing report, and cc the developer and relevant dev team leads. Ensure that any bugs found during this process are filed and assigned to the developer. If you see design issues, it's fine to loop in the design team. If issues were discovered in the run-through, repeat the above as needed until there are no more issues. (Only mark this step as complete once that stage is reached -- at this point, ProdOps is saying "I'm happy with the feature, it can go to full QA.")

Full feature testing (ProdOps team)

• Set up a "launch command channel" Google Space for this feature launch and invite all relevant parties (design, developer, QA, campaign strategy team members + leads). Name the channel as follows: "[Feature Launch] Restructured Study Guides".
• Send QA team (qa-team AT oppia DOT org) an email that a new feature is ready for testing. Send them the pre-launch doc (with CUJs) and request the list of tester usernames. Do the same for any members from the Campaign Strategy (campaign-strategy-team@) and Design teams (design-team@) who want to participate.
• Ask the tech leads to provide the necessary permissions (see "Required roles for testing", above) to the tester usernames on the backup-server.
• Ask QA leads to start the feature testing process. As testing progresses, make updates to clarify the CUJ descriptions as needed. Add a comment to this issue thread with a link to the feature testing report, and cc the developer and relevant dev team leads. Ensure that any new bugs are filed and assigned to the developer. Periodically check the Looker Studio dashboard to verify that metrics are being correctly recorded during feature testing, and adjust the metrics, if needed, to make them more useful. If issues were discovered in the testing, repeat the above as needed until there are no more issues. (Only mark this step as complete once the feature passes testing.)
• Tell the tech leads that the feature has passed QA and can be moved to PROD stage. They should link to the PR here once it is merged: ______.
• Send a message to the Campaign Strategy leads to let them know that the product is ready for launch.
• If the Campaign Strategy team wants to include a "trusted tester" phase, run through this with them following the guidance in the Product/Marketing Communication Process document.

Rollout (ProdOps team)

• Agree on launch date with Marketing team and tech leads, and document it here. Launch date: ______.
• Verify that the QA team has added the feature's CUJs to the master CUJ document.
• Work with the server admins team to flip the feature flag 5-7 days before the launch date, and confirm that the feature works in production.
• Send out a congratulatory launch email, crediting all the folks involved in the launch.
• Monitor post-launch metrics through the feature's Looker Studio dashboard (constructed above).
• Monitor post-launch feedback through GitHub issues, filed and Google Groups forum.
• 2 weeks after launch, compile a post-launch report and schedule a post-launch review with everyone on the command channel (design, developers, marketing, QA).
• Ask the tech leads to remove the feature flag. Link to PR that removes the flag: _____.
• Close this bug. This concludes the feature launch, congratulations! 🎉

[Nik-09]

Adding mentors for reference: @kevintab95 @chris7716

[Nik-09]

Hi @tczerwinski726,
Just checking in to see if we’re good to proceed with the feature launch. Could you please share if there are any remaining concerns or items that still need to be addressed?

Thanks!
cc/ @mon4our @seanlip

[seanlip]

Assigning @mon4our @kevintab95 for the tech-lead side of this.

@mon4our @kevintab95 Please complete the tech-lead side and hand off to @tczerwinski726 for ProdOps. Thanks!

[tczerwinski726]

This is the milestone 1 launch that won’t go to learners yet, right? I’m fine with it launching. I’ll have some time in the morning to do the work on my end.

…

On Wed, Aug 13, 2025 at 11:06 PM Sean Lip ***@***.***> wrote: *seanlip* left a comment (oppia/product-operations-team#33) <#33 (comment)> Assigning @mon4our <https://github.com/mon4our> @kevintab95 <https://github.com/kevintab95> for the tech-lead side of this. @mon4our <https://github.com/mon4our> @kevintab95 <https://github.com/kevintab95> Please complete the tech-lead side and hand off to @tczerwinski726 <https://github.com/tczerwinski726> for ProdOps. Thanks! — Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BSFRLVD7QWZSKTTWE5WDXO33NQRO5AVCNFSM6AAAAAB6NNSNHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCOBXGA4DAMBQG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[seanlip]

This is the milestone 1 launch that won’t go to learners yet, right?

Actually, this milestone 1 launch will go to learners and will change how study guides show up for them. The one that won't go to learners is for a different project (#35).

I think @kevintab95 and @mon4our still need to do a bit of work before this can be handed off to ProdOps, though (see updated checklist).

[tczerwinski726]

Ok, so we ship the UI improvements for study guides as M1 to learners, and then follow with worked solutions, yes? What day do we want to target for the launch? What works for engineering?

…

On Thu, Aug 14, 2025 at 12:05 AM Sean Lip ***@***.***> wrote: *seanlip* left a comment (oppia/product-operations-team#33) <#33 (comment)> This is the milestone 1 launch that won’t go to learners yet, right? Actually, this milestone 1 launch will go to learners and will change how study guides show up for them. The one that won't go to learners is for a different project (#35 <#35>). I think @kevintab95 <https://github.com/kevintab95> and @mon4our <https://github.com/mon4our> still need to do a bit of work before this can be handed off to ProdOps, though (see updated checklist). — Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BSFRLVFJ5UEQO4FXJ4PLBJL3NQYKJAVCNFSM6AAAAAB6NNSNHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCOBXGIYDQOBUGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[kevintab95]

What day do we want to target for the launch? What works for engineering?

Hi @tczerwinski726, there are a few minor changes that @mon4our made based on recent feedback. Once the changes are merged, I will deploy those changes to the backup server and do a quick round of testing before handing it over to you (per the checklist) -- I expect this to be Saturday EOD.