OVERVIEW

• In MTC, have a banner for the EOL of MTC on December 2026.

• Mention that MTA by July 2026 would be the replacement of MTC, with feature parity

• In the migration section of the documentation, point to MTA As the replacement of current MTC. 

This ticket involves a combination of content creation, documentation updates, and cross-linking to ensure users are fully informed about the Migration Toolkit for Containers (MTC) End-of-Life (EOL) and the transition to its replacement, the Migration Toolkit for Applications (MTA).

1. Content Creation for the MTC EOL Banner

The writer must draft the precise, concise, and actionable text that will be displayed in the MTC product banner. This text will be provided to the product or engineering team for implementation.

• Draft the Core Message: Create a clear, high-priority notification that includes all mandated dates and replacement information.

• • Required information: MTC End of Life: December 2026.

• • Required information: Replacement: Migration Toolkit for Applications (MTA).

• • Required information: MTA Status: Expected to reach feature parity by July 2026.

• Include Link: Determine and include the URL for the most relevant MTA documentation landing page or a dedicated announcement page for the migration path.

• Final Banner Text Review: Secure approval from product management or relevant stakeholders (e.g., Marketing, Legal) for the exact phrasing and dates before delivering the final copy to the development team.

2. Updates to MTC Documentation

The technical writer must systematically update the MTC documentation, specifically targeting the provided location (e.g., https://docs.redhat.com/.../migration_toolkit_for_containers/index).

A. Add a Prominent EOL Notice

• Front Matter/Landing Page: Add a highly visible End-of-Life Notice directly on the MTC documentation landing page (the index page) and/or in the release notes section.

• Dedicated EOL Section: Create a small, mandatory "MTC End-of-Life" chapter or topic. This section should clearly state the EOL date (December 2026) and the official replacement path.

B. Revise the Migration Section

• Identify Target: Locate the existing chapter or section dedicated to the "Migration" process within the MTC documentation (e.g., "Performing a Migration," "Getting Started").

• Insert Replacement Directive: Immediately within this section, insert a clear statement that MTC is deprecated and that future migration projects and feature development will be handled by MTA.

• Add Link: Ensure this section contains a working hyperlink to the relevant MTA documentation, making the transition seamless for the user.

C. Update Overview and Scope

• Introduction/Overview Chapter: Modify the introductory chapter to include a deprecation notice and a forward-looking statement about MTA, framing MTC as a product with a limited lifespan.

• Maintain Integrity: Ensure that instructions for using MTC remain accurate for customers who need to complete migrations before the EOL date, but surround this content with clear warnings about the upcoming EOL.

3. Cross-Linking and Documentation Alignment (MTA)

While the ticket focuses on MTC, the technical writer is responsible for ensuring the information is consistent and easy to find across the entire product suite. This requires coordinating with the team managing the MTA documentation.

• Locate MTA Documentation: Identify the current landing page and relevant migration guide for the Migration Toolkit for Applications (MTA).

• Create MTC Transition Topic (in MTA Docs): Ensure the MTA documentation includes a dedicated section (e.g., "Migration Path from MTC") that explicitly welcomes MTC users. This topic should:

• • Acknowledge the MTC EOL date (December 2026).

• • Confirm Feature Parity: Reassure users that MTA will have feature parity with MTC by July 2026.

• • Provide a Conversion Guide: Offer guidance on how a user familiar with MTC concepts can start using MTA, highlighting any key differences or new features.

• Verify Bidirectional Links: Confirm that the link from the MTC documentation to MTA is active and correct, and that the MTA documentation links back to the official EOL announcement.