Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions migration-services/enterprise.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@
We review your submission and lead a kick-off call with our migration team to walk through your current setup, understand any limitations, and address any questions your team might have.
</Step>

<Step title="Receive scoping and timeline (1-2 business days)">
<Step title="Receive scoping and timeline (1-2 days)">
We review and analyze the context from the call and provide an estimated delivery timeline within 24-48 hours. We'll flag any custom components or areas of your migration that need discussion.
</Step>

Expand All @@ -38,8 +38,8 @@
We deliver your migration via GitHub PR or zip file based on your preference.
</Step>

<Step title="Feedback window (seven business days)">
<Step title="Feedback window (seven days)">
Submit any feedback on content, assets, or branding. We address all in-scope issues within the same timeframe.

Check warning on line 42 in migration-services/enterprise.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

migration-services/enterprise.mdx#L42

Did you really mean 'timeframe'?
</Step>

<Step title="Go-live support">
Expand All @@ -52,15 +52,15 @@
We work with vetted third-party vendors and conduct an internal quality audit before delivery. Here's what we check for:

<Card title="Content completeness" icon="file-check">
- All documentation from your source has been migrated.

Check warning on line 55 in migration-services/enterprise.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

migration-services/enterprise.mdx#L55

In general, use active voice instead of passive voice ('been migrated').
- Content is properly formatted with Mintlify components.
- Navigation structure matches your specifications.
</Card>

<Card title="Visual elements" icon="palette">
- Images and videos display correctly.
- Custom fonts are applied throughout.

Check warning on line 62 in migration-services/enterprise.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

migration-services/enterprise.mdx#L62

In general, use active voice instead of passive voice ('are applied').
- Light and dark mode logos are used appropriately.

Check warning on line 63 in migration-services/enterprise.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

migration-services/enterprise.mdx#L63

In general, use active voice instead of passive voice ('are used').
- Color schemes meet contrast requirements in both modes.
</Card>

Expand Down Expand Up @@ -98,7 +98,7 @@
</Accordion>

<Accordion title="Can I request changes after delivery?">
Yes. You have a 7-day feedback window after delivery to request changes to content, assets, or branding. We address all in-scope feedback within the same timeframe and work with you right until you are ready to go live.

Check warning on line 101 in migration-services/enterprise.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

migration-services/enterprise.mdx#L101

Did you really mean 'timeframe'?
</Accordion>

<Accordion title="What do I need to do after the migration is complete?">
Expand All @@ -111,11 +111,11 @@
</Accordion>

<Accordion title="Can I customize the navigation structure?">
Yes. You can provide a custom information architecture and we implement it for you. We also work with you on custom component development if that is needed and supported by the platform.

Check warning on line 114 in migration-services/enterprise.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

migration-services/enterprise.mdx#L114

In general, use active voice instead of passive voice ('is needed').
</Accordion>

<Accordion title="What happens if my documentation changes during the migration?">
Since migrations require a code freeze, any changes made to your source documentation after submission won't be included. We recommend completing all updates before starting the migration.

Check warning on line 118 in migration-services/enterprise.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

migration-services/enterprise.mdx#L118

In general, use active voice instead of passive voice ('be included').

If this is not possible, our team works with you to set short sprints to migrate certain sections or reserve dedicated time after the first sprint to migrate the delta changes made during the migration.
</Accordion>
Expand Down
6 changes: 3 additions & 3 deletions migration-services/pro.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@
Provide your documentation source, brand assets (logos, color codes, fonts), OpenAPI specs, go-live date, and preferred delivery method (GitHub PR or zip file).
</Step>

<Step title="Receive scoping and timeline (1-2 business days)">
<Step title="Receive scoping and timeline (1-2 days)">
We review your submission and provide an estimated delivery timeline within 24-48 hours. We'll flag any custom components or areas of your migration that need discussion.
</Step>

Expand All @@ -41,8 +41,8 @@
We deliver your migration via GitHub PR or zip file based on your preference.
</Step>

<Step title="Feedback window (three business days)">
<Step title="Feedback window (three days)">
Submit any feedback on content, assets, or branding. We address all in-scope issues within the same timeframe.

Check warning on line 45 in migration-services/pro.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

migration-services/pro.mdx#L45

Did you really mean 'timeframe'?
</Step>

<Step title="Go-live support">
Expand All @@ -55,15 +55,15 @@
We work with vetted third-party vendors and conduct an internal quality audit before delivery. Here's what we check for:

<Card title="Content completeness" icon="file-check">
- All documentation from your source has been migrated.

Check warning on line 58 in migration-services/pro.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

migration-services/pro.mdx#L58

In general, use active voice instead of passive voice ('been migrated').
- Content is properly formatted with Mintlify components.
- Navigation structure matches your specifications.
</Card>

<Card title="Visual elements" icon="palette">
- Images and videos display correctly.
- Custom fonts are applied throughout.

Check warning on line 65 in migration-services/pro.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

migration-services/pro.mdx#L65

In general, use active voice instead of passive voice ('are applied').
- Light and dark mode logos are used appropriately.

Check warning on line 66 in migration-services/pro.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

migration-services/pro.mdx#L66

In general, use active voice instead of passive voice ('are used').
- Color schemes meet contrast requirements in both modes.
</Card>

Expand Down Expand Up @@ -97,11 +97,11 @@

<AccordionGroup>
<Accordion title="How long does a migration take?">
We typically deliver migrations within 10 business days, depending on complexity. You'll receive a specific timeline within 24-48 hours of submitting your migration form.
We typically deliver migrations within 10 days, depending on complexity. You'll receive a specific timeline within 24-48 hours of submitting your migration form.
</Accordion>

<Accordion title="Can I request changes after delivery?">
Yes. You have a 3-day feedback window after delivery to request changes to content, assets, or branding. We address all in-scope feedback within the same timeframe.

Check warning on line 104 in migration-services/pro.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

migration-services/pro.mdx#L104

Did you really mean 'timeframe'?
</Accordion>

<Accordion title="What do I need to do after the migration is complete?">
Expand All @@ -118,6 +118,6 @@
</Accordion>

<Accordion title="What happens if my documentation changes during the migration?">
Since migrations require a code freeze, any changes made to your source documentation after submission won't be included. We recommend completing all updates before starting the migration.

Check warning on line 121 in migration-services/pro.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

migration-services/pro.mdx#L121

In general, use active voice instead of passive voice ('be included').
</Accordion>
</AccordionGroup>
Loading