-
Notifications
You must be signed in to change notification settings - Fork 30
Meta
Peter Nied edited this page Sep 19, 2024
·
6 revisions
This page is meant to describe how the Migration Assistant (MA) documentation is organization and used.
- All pages should have a commented out section with metadata information used for determining what styles should be applied, eg.
<!-- Document: Meta -->
.- Meta these follow unique conventions to the documentation's implementation.
- Home This is the primary entry point to the project, there should only be one such page.
- Guide take a user through an substantial part of the MA workflow. Duplicated information is OK. They should be styled simaliarally to one another.
- Topic describe a specific area of functionality in MA and are meant to be digestible from top to bottom in a single sitting. After the user has read the topic they would use a sidebar navigate to pick the next topic.
- Sidebar navigation should include all guides and topics.
- There is no hierarchy in project all files are off of the root.
- All internal links should use the
[[<DISPLAY-NAME>|<PAGE-NAME>]]
format so testing on forks is easy and broken page links are easier to detect
Encountering a compatibility issue or missing feature?
- Search existing issues to see if it’s already reported. If it is, feel free to upvote and comment.
- Can’t find it? Create a new issue to let us know.
- Migration Assistant Overview
- Is Migration Assistant Right for You?
- Existing Data Migration - Quick Start Guide
- A. Snapshot Creation Verification
- B. Client Traffic Switchover Verification
- C. Traffic Capture Verification
- D. System Reset Before Migration