Repository: Expensify/App
Pull request #60296: Remove Classic copy from New Expensify travel hub
Author: login: strepanier03
Created: 2025-04-15T16:12:22Z | Merged: 2025-04-17T05:40:07Z

Coming from this [GH](https://github.com/Expensify/App/issues/58922) -- We are breaking up New and Classic travel docs into their own hubs. I have already created the Classic hub and put copies of each Classic doc in it. 

Now I just want to clean up the New Expensify hub.

<!-- If necessary, assign reviewers that know the area or changes well. Feel free to tag any additional reviewers you see fit. -->

### Explanation of Change
<!-- Explain what your change does and how it addresses the linked issue -->

### Fixed Issues
<!---
1. Please postfix `$` with a URL link to the GitHub issue this Pull Request is fixing. For example, `$ https://github.com/Expensify/App/issues/<issueID>`.
2. Please postfix  `PROPOSAL:` with a URL link to your GitHub comment, which contains the approved proposal (i.e. the proposal that was approved by Expensify).  For example, `PROPOSAL: https://github.com/Expensify/App/issues/<issueID>#issuecomment-1369752925`

Do NOT add the special GH keywords like `fixed` etc, we have our own process of managing the flow.
It MUST be an entire link to the github issue and your comment proposal ; otherwise, the linking and its automation will not work as expected.

Make sure this section looks similar to this (you can link multiple issues using the same formatting, just add a new line):

$ https://github.com/Expensify/App/issues/<issueID>
$ https://github.com/Expensify/App/issues/<issueID(comment)>

Do NOT only link the issue number like this: $ #<issueID>
--->
$
PROPOSAL:


<!--- 
If you want to trigger adhoc build of hybrid app from specific Mobile-Expensify PR please link it like this:

MOBILE-EXPENSIFY: https://github.com/Expensify/Mobile-Expensify/pull/<PR-number>

--->

### Tests
<!---
Add a numbered list of manual tests you performed that validates your changes work on all platforms, and that there are no regressions present.
Add any additional test steps if test steps are unique to a particular platform.
Manual test steps should be written so that your reviewer can repeat and verify one or more expected outcomes in the development environment.

For example:
1. Click on the text input to bring it into focus
2. Upload an image via copy paste
3. Verify a modal appears displaying a preview of that image
--->

- [ ] Verify that no errors appear in the JS console

### Offline tests
<!---
Add any relevant steps that validate your changes work as expected in a variety of network states e.g. "offline", "spotty connection", "slow internet", etc. Manual test steps should be written so that your reviewer and QA testers can repeat and verify one or more expected outcomes. If you are unsure how the behavior should work ask for advice in the `#expensify-open-source` Slack channel.
--->

### QA Steps
<!---
Add a numbered list of manual tests that can be performed by our QA engineers on the staging environment to validate that your changes work on all platforms, and that there are no regressions present.
Add any additional QA steps if test steps are unique to a particular platform.
Manual test steps should be written so that the QA engineer can repeat and verify one or more expected outcomes in the staging environment.

For example:
1. Click on the text input to bring it into focus
2. Upload an image via copy paste
3. Verify a modal appears displaying a preview of that image

It's acceptable to write "Same as tests" if the QA team is able to run the tests in the above "Tests" section.
--->
// TODO: These must be filled out, or the issue title must include "[No QA]."

- [ ] Verify that no errors appear in the JS console

### PR Author Checklist
<!--
This is a checklist for PR authors. Please make sure to complete all tasks and check them off once you do, or else your PR will not be merged!
-->
- [x] I linked the correct issue in the `### Fixed Issues` section above
- [x] I wrote clear testing steps that cover the changes made in this PR
    - [x] I added steps for local testing in the `Tests` section
    - [x] I added steps for the expected offline behavior in the `Offline steps` section
    - [x] I added steps for Staging and/or Production testing in the `QA steps` section
    - [x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    - [x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    - [x] I tested this PR with a [High Traffic account](https://github.com/Expensify/App/blob/main/contributingGuides/CONTRIBUTING.md#high-traffic-accounts) against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
- [x] I included screenshots or videos for tests on [all platforms](https://github.com/Expensify/App/blob/main/contributingGuides/CONTRIBUTING.md#make-sure-you-can-test-on-all-platforms)
- [x] I ran the tests on **all platforms** & verified they passed on:
    - [x] Android / native
    - [x] Android / Chrome
    - [x] iOS / native
    - [x] iOS / Safari
    - [x] MacOS / Chrome / Safari
    - [x] MacOS / Desktop
- [x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
- [x] I followed proper code patterns (see [Reviewing the code](https://github.com/Expensify/App/blob/main/contributingGuides/PR_REVIEW_GUIDELINES.md#reviewing-the-code))
    - [x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. `toggleReport` and not `onIconClick`)
    - [x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. `myBool && <MyComponent />`.
    - [x] I verified that comments were added to code that is not self explanatory
    - [x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    - [x] I verified any copy / text shown in the product is localized by adding it to `src/languages/*` files and using the [translation method](https://github.com/Expensify/App/blob/4bd99402cebdf4d7394e0d1f260879ea238197eb/src/components/withLocalize.js#L60)
      - [x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    - [x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the [localization methods](https://github.com/Expensify/App/blob/4bd99402cebdf4d7394e0d1f260879ea238197eb/src/components/withLocalize.js#L60-L68)
    - [x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the `Waiting for Copy` label for a copy review on the original GH to get the correct copy.
    - [x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    - [x] I verified the JSDocs style guidelines (in [`STYLE.md`](https://github.com/Expensify/App/blob/main/contributingGuides/STYLE.md#jsdocs)) were followed
- [x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
- [x] I followed the guidelines as stated in the [Review Guidelines](https://github.com/Expensify/App/blob/main/contributingGuides/PR_REVIEW_GUIDELINES.md)
- [x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like `Avatar`, I verified the components using `Avatar` are working as expected)
- [x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
- [x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
- [x] I verified that if a function's arguments changed that all usages have also been updated correctly
- [x] If a new component is created I verified that:
    - [x] A similar component doesn't exist in the codebase
    - [x] All props are defined accurately and each prop has a `/** comment above it */`
    - [x] The file is named correctly
    - [x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    - [x] The only data being stored in the state is data necessary for rendering and nothing else
    - [x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
        - [x] Any internal methods bound to `this` are necessary to be bound (i.e. avoid `this.submit = this.submit.bind(this);` if `this.submit` is never passed to a component event handler like `onClick`)
    - [x] All JSX used for rendering exists in the render method
    - [x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
- [x] If any new file was added I verified that:
    - [x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
- [x] If a new CSS style is added I verified that:
    - [x] A similar style doesn't already exist
    - [x] The style can't be created with an existing [StyleUtils](https://github.com/Expensify/App/blob/main/src/styles/StyleUtils.js) function (i.e. `StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)`)
- [x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
- [x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like `Avatar` is modified, I verified that `Avatar` is working as expected in all cases)
- [x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
- [x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
- [x] If a new page is added, I verified it's using the `ScrollView` component to make it scrollable when more elements are added to the page.
- [x] If the `main` branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the `Test` steps.
- [x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

### Screenshots/Videos
<details>
<summary>Android: Native</summary>

<!-- add screenshots or videos here -->

</details>

<details>
<summary>Android: mWeb Chrome</summary>

<!-- add screenshots or videos here -->

</details>

<details>
<summary>iOS: Native</summary>

<!-- add screenshots or videos here -->

</details>

<details>
<summary>iOS: mWeb Safari</summary>

<!-- add screenshots or videos here -->

</details>

<details>
<summary>MacOS: Chrome / Safari</summary>

<!-- add screenshots or videos here -->

</details>

<details>
<summary>MacOS: Desktop</summary>

<!-- add screenshots or videos here -->

</details>



Diff:
diff --git a/docs/articles/new-expensify/travel/Approve-travel-expenses.md b/docs/articles/new-expensify/travel/Approve-travel-expenses.md
index 34667f802643..71a59632a048 100644
--- a/docs/articles/new-expensify/travel/Approve-travel-expenses.md
+++ b/docs/articles/new-expensify/travel/Approve-travel-expenses.md
@@ -2,58 +2,6 @@
 title: Approve travel expenses
 description: Determine how travel expenses are approved
 ---
-<div id="expensify-classic" markdown="1">
-
-Travel expenses follow the same approval workflow as other expenses. Admins can configure travel expenses to be approved as soft approval, hard approval or passive approval. The approval method for in-policy and out-of-policy bookings can be managed under the **Policies** section in the **Program** menu for Expensify Travel. 
- 
-- **Soft Approval**: Bookings are automatically approved as long as a manager does not decline them within 24 hours. However, this also means that if a manager does not decline the expenses, the arrangements will be booked even if they are out of policy. If a booking is declined, it is refunded based on the voiding/refund terms of the service provider.
-- **Hard Approval**: Bookings are automatically canceled/voided and refunded if a manager does not approve them within 24 hours. 
-- **Passive Approval**: Managers are informed of out-of-policy travel, but there is no action to be taken.
-
-# Set Approval Method
-
-1. Click the **Travel** tab.
-2. Click **Book or manage travel**.
-3. Click the **Program** tab at the top and select **Policies**.
-4. Under General, select approval methods for Flights, Hotels, Cars and Rail.
-
-![Screenshot of Expensify Travel policy approval settings](https://help.expensify.com/assets/images/Travel_Policy.png){:width="100%"}
-
-# Approve Travel
-
-![Screenshot of Expensify Travel approval email](https://help.expensify.com/assets/images/travel-soft-approval.png){:width="100%"}
-
-## Soft Approval
-
-Once an employee has booked a trip, their approver will receive an email notifying them of the booking with a prompt to decline it if needed. 
-
-- To approve the booking, no action is required. 
-- To decline the booking, click **Decline booking** within 24 hours. Then click **Deny Booking**.
-
-## Hard Approval
-
-Once an employee has booked a trip, their approver will receive an email notifying them of the booking with a prompt to accept or decline the booking.
-
-To approve the booking, click **Approve booking**. Then click **Approve**.
-To decline the booking, click **Decline booking**. Then click **Deny**. 
-
-# FAQ
-
-## Are extended approval windows given for trips booked over the weekend or during company holidays?
-
-No, the approval window will always be 24 hours from when the trip is booked. 
-
-## How does Expensify Travel handle approvals when the assigned approver is out of office? 
-
-It is recommended to have multiple approvers for travel, as there is no delegated approval for out-of-office approvers.
-
-## Can travelers upload a document when submitting a trip for approval?
-
-Travelers are unable to add a document when submitting a trip for approval, but the company can add a ‘reason code’ in the Out of Policy rules that the traveler can complete at checkout. The traveler can then add the document to the expense report in Expensify when submitting the report. 
-
-</div>
-
-<div id="new-expensify" markdown="1">
 
 Travel expenses follow the same approval workflow as other expenses. Admins can configure travel expenses to be approved as soft approval, hard approval or passive approval. The approval method for in-policy and out-of-policy bookings can be managed under the **Policies** section in the **Program** menu for Expensify Travel. 
  
@@ -101,5 +49,3 @@ It is recommended to have multiple approvers for travel, as there is no delegate
 ## Can travelers upload a document when submitting a trip for approval?
 
 Travelers are unable to add a document when submitting a trip for approval, but the company can add a ‘reason code’ in the Out of Policy rules that the traveler can complete at checkout. The traveler can then add the document to the expense report in Expensify when submitting the report. 
-
-</div>
diff --git a/docs/articles/new-expensify/travel/Book-with-Expensify-Travel.md b/docs/articles/new-expensify/travel/Book-with-Expensify-Travel.md
index 5d25670ac5ab..e7ec9c1e9f6b 100644
--- a/docs/articles/new-expensify/travel/Book-with-Expensify-Travel.md
+++ b/docs/articles/new-expensify/travel/Book-with-Expensify-Travel.md
@@ -2,7 +2,6 @@
 title: Book with Expensify Travel
 description: Book flights, hotels, cars, trains, and more with Expensify Travel
 ---
-<div id="expensify-classic" markdown="1">
 
 Expensify Travel allows members to search and book flights, hotels, cars, and trains globally at the most competitive rates available. 
 
@@ -20,43 +19,6 @@ There is a flat fee of $15 per trip booked. A single trip can include multiple b
 
 # Book travel
 
-To book travel from the Expensify web app,
-
-1. Click the **Travel** tab.
-2. Click **Book or manage travel**.
-3. Use the icons at the top to select the type of travel arrangement you want to book: flights, hotels, cars, or trains.
-4. Enter the travel information relevant to the travel arrangement selected (for example, the destination, dates of travel, etc.). 
-5. Select all the details for the arrangement you want to book.
-6. Review the booking details and click **Book Flight / Book Hotel / Book Car / Book Rail** to complete the booking.
-
-The traveler is emailed an itinerary of the booking. Additionally,  
-- Their travel details are added to a Trip chat room under their primary workspace. 
-- An expense report for the trip is created.
-- If booked with an Expensify Card, the trip is automatically reconciled.
-
-{% include info.html %}
-The travel itinerary is also emailed to the traveler’s [copilots](https://help.expensify.com/articles/expensify-classic/copilots-and-delegates/Assign-or-remove-a-Copilot), if applicable.
-{% include end-info.html %}
-
-</div>
-
-<div id="new-expensify" markdown="1">
-Expensify Travel allows members to search and book flights, hotels, cars, and trains globally at the most competitive rates available. 
-
-With Expensify Travel, you can:
-- Search and book travel arrangements all in one place
-- Book travel for yourself or for someone else
-- Get real-time support by chat or phone
-- Manage all your T&E expenses in Expensify
-- Create specific rules for booking travel
-- Enable approvals for out-of-policy trips
-- Book with any credit card on the market
-- Book with the Expensify Card to get cash back and automatically reconcile transactions
-
-There is a flat fee of $15 per trip booked. A single trip can include multiple bookings, such as a flight, a hotel, and a car rental.
-
-# Book travel
-
 {% include selector.html values="desktop, mobile" %}
 
 {% include option.html value="desktop" %}
@@ -85,5 +47,3 @@ The traveler is emailed an itinerary of the booking. Additionally,
 - Their travel details are added to a Trip chat room under their primary workspace. 
 - An expense report for the trip is created.
 - If booked with an Expensify Card, the trip is automatically reconciled.
-
-</div>
diff --git a/docs/articles/new-expensify/travel/Configure-travel-policy-and-preferences.md b/docs/articles/new-expensify/travel/Configure-travel-policy-and-preferences.md
index d7d9c656a612..5195ccaeae4d 100644
--- a/docs/articles/new-expensify/travel/Configure-travel-policy-and-preferences.md
+++ b/docs/articles/new-expensify/travel/Configure-travel-policy-and-preferences.md
@@ -2,91 +2,6 @@
 title: Configure travel policy and preferences 
 description: Set and update travel policies and preferences for your Expensify Workspace
 ---
-<div id="expensify-classic" markdown="1">
-
-As a Workspace Admin, you can set travel policies for all travel booked under a workspace, including approval methods, flight booking class, and hotel star preferences. You can also create multiple policies with specific conditions for particular groups of employees and/or non-employees. 
-
-# Create or update a travel policy
-
-Workspace admins can create different travel policies that provide travel rules for different groups of travelers. When using Expensify Travel for the first time, you will need to create a new Travel Policy.
-
-To create or update a travel policy,
-
-1. Click the **Travel** tab.
-2. Click **Book or manage travel**. 
-3. Click the **Program** tab at the top and select **Policies**. 
-4. Under Employee or Non-employee in the left menu, click **Add new** to create a new policy. 
-5. Use the **Edit members** section to select the group of employees that belong to this policy.
-    1. **To select an existing policy:** Select the policy in the left menu.
-    2. **To add a new policy:** Click **Add new** under Employee or Non-employee in the left menu. Then under the Edit members section, select the group of employees that belong to this policy.
-
-{% include info.html %}
-A Legal Entity in Expensify Travel is the equivalent of an Expensify Workspace.
-{% include end-info.html %}
-
-10. Select which travel preferences you want to modify: General, flight, hotel, car, or rail. 
-11. Click the paperclip icon next to each setting to de-couple it from your default policy.
-12. Update the desired settings.
-
-# General
-
-Determine the currency and [approval type](https://help.expensify.com/articles/expensify-classic/travel/Approve-travel-expenses#set-approval-method) for different types of travel bookings. You can also upload a PDF of your company travel policy for employees to access when booking travel. 
-
-![Screenshot of Expensify Travel policy approval settings](https://help.expensify.com/assets/images/Travel_Policy.png){:width="100%"}
-
-# Flight
-
-Flight preferences include multiple sections with different settings: 
-
-- **Flights not allowed to be booked:** Restrict specific flight classes from being booked by employees.
-- **Cabin class settings:** Set the highest cabin class allowed for booking and whether employees can accept cabin upgrades. 
-- **Budget:** Set a percentage or fare cap for the median or cheapest fares on flights, and a maximum capped price. Flight fares above this cap will be considered out of policy. You can also add customization to allow for different caps for different flight durations. 
-- **Lowest logical fare settings:** Set a preference for layovers, number of stops, flight time window, and airport connection changes. Expensify automatically takes these preferences into account when showing the lowest logical travel fare. 
-- **Add Ons and Preferences:** Select what types of add-ons your employees can book, including:
-  - Additional baggage
-  - Early check-in
-  - Seat preference
-  - No add-ons allowed
-- **Booking windows:** Add a time limit to prevent employees from booking less than a certain number of days in advance to prohibit bookings too close to the flight time.
-- **Refundable/changeable tickets:** Allow employees to book fully or partially refundable fares. To allow all options, you can leave this as the default option. 
-- **Maximum CO2 per kilometer:** If the CO2 per passenger km exceeds this threshold, the flight will be marked as out of policy. You can leave the entry blank if you do not wish to use this policy.
-- **Out of policy reason codes:** If enabled, travelers will be asked to enter a reason code for an out-of-policy flight booking. This gives them a way to provide context for why the booking is still being placed. You can also modify the reason codes by clicking Manage reason codes below the toggle.
-
-# Hotel
-
-- **Restrict booking by keyword:** Keywords entered here will be compared to the hotel rate description. If any of the keywords are found, the hotel rate will be restricted. You also have the option to provide a reason why each keyword is restricted. 
-- **Hotel rates not allowed to be booked:** Restrict specific hotel rates (such as non-refundable, prepaid, and requires deposit) from being booked by employees. This overrides all other hotel policy rules. You also have the option to add a reason why these options aren’t available. 
-- **Maximum price:** Set a maximum price per night for bookings. You can also select the Customizations by location option to set a maximum price for each location.
-- **Booking window:**  Add a time limit to prevent employees from booking less than a certain number of days in advance to prohibit bookings too close to the flight time.
-- **Cancellation policy:** Allow your employees to book fully or partially refundable rooms. To allow all options, you can leave this as the default option. 
-- **Experience:** Set hotel ratings that are in and out of policy.
-- **Nightly median rate:** Determine which hotels to consider when calculating the median price. You can set a radius around the search location and include/disclude hotels above or below a certain rating.
-- **Out of policy reason codes:** If enabled, travelers will be asked to enter a reason code for an out-of-policy hotel booking. This gives them a way to provide context for why the booking is still being placed. You can also modify the reason codes by clicking Manage reason codes below the toggle.
-
-# Car
-
-- **Car categories not allowed:** Restrict specific car types from being booked by employees. This overrides any other car policy.
-- **Car categories in policy:** Define the types of cars that are in policy. If you do not list a specific car category, it will still be booked as long as it isn’t included in the Car categories not allowed setting. However, the booking will be classed as out of policy. 
-- **Car engine types not allowed:** Restrict specific engine types from being booked by employees regardless of other policy settings. 
-- **Maximum price:** Set a daily price cap per car (not including taxes and fees).
-- **Out of policy reason codes:** If enabled, travelers will be asked to enter a reason code for an out-of-policy car booking. This gives them a way to provide context for why the booking is still being placed. You can also modify the reason codes by clicking Manage reason codes below the toggle.
-
-# Rail
-
-- **Maximum price:** Set a maximum price per booking or customise by rail trip duration.
-- **Highest travel class:** Set a maximum travel class per booking or customise by rail trip duration.
-- **Booking window:** Add a time limit to prevent employees from booking less than a certain number of days in advance to prohibit bookings too close to the journey time.
-- **Out-of-policy reason code for rail:** If enabled, travelers will be asked to enter a reason code for an out-of-policy rail booking. This gives them a way to provide context for why the booking is still being placed. You can also modify the reason codes by clicking Manage reason codes below the toggle.
-
-# FAQ
-
-How do travel policy rules interact with Expensify’s [approval flows](https://help.expensify.com/articles/expensify-classic/travel/Approve-travel-expenses)?
-
-Travel policy rules define what can and can’t be booked by your employees while they’re making the booking. Once a booking is placed and the travel itself is [approved](https://help.expensify.com/articles/expensify-classic/travel/Approve-travel-expenses), the expense will appear in Expensify. It will then be coded, submitted, pushed through the existing expense approval process as defined by your workspace, and exported to your preferred accounting platform (if applicable).
-
-</div>
-
-<div id="new-expensify" markdown="1">
 
 As a Workspace Admin, you can set travel policies for all travel booked under your workspace, including approval methods, flight booking class, and hotel star preferences. You can also create multiple policies with specific conditions for particular groups of employees and/or non-employees. 
 
@@ -169,5 +84,3 @@ If the travel policy you want to configure is greyed out, it might be linked to
 1. Look for the “link” icon next to the dropdown menu. 
 2. Click the icon to unlink the policy from the parent policy. 
 3. Once unlinked, you’ll be able to make your selection.
-
-</div>
diff --git a/docs/articles/new-expensify/travel/Edit-or-cancel-travel-arrangements.md b/docs/articles/new-expensify/travel/Edit-or-cancel-travel-arrangements.md
index 35d069a285ec..152dd572690c 100644
--- a/docs/articles/new-expensify/travel/Edit-or-cancel-travel-arrangements.md
+++ b/docs/articles/new-expensify/travel/Edit-or-cancel-travel-arrangements.md
@@ -2,25 +2,7 @@
 title: Edit or cancel travel arrangements
 description: Modify travel arrangements booked with Expensify Travel
 ---
-<div id="expensify-classic" markdown="1">
 
-To edit or cancel a travel arrangement,
-1. Click Travel in the left menu.  
-2. Click Book or Manage Travel.  
-3. Select Trips, and **Individual** or **Company**. 
-4. Click into the booking to see more details. 
-5. Select **Modify** or **Cancel**. 
-
-If there is an unexpected change to the itinerary (for example, a flight cancellation), Expensify’s travel partner **Spotnana** will reach out to the traveler to provide updates on those changes. 
-
-{% include info.html %}
-You can click **Get Support** on your emailed travel itinerary for real-time help with the booking. Any modifications, exchanges, or voidings made to a trip via support will incur a $25 booking change fee.
-{% include end-info.html %}
-
-</div>
-
-<div id="new-expensify" markdown="1">
-  
 You can review your travel arrangements any time by opening the Trip chat in your inbox. For example, if you booked a flight to San Francisco, a “Trip to San Francisco” chat will be automatically added to your chat inbox.  
 
 To edit or cancel a travel arrangement,
@@ -35,5 +17,3 @@ If there is an unexpected change to the itinerary (for example, a flight cancell
 {% include info.html %}
 You can click **Get Support** on your emailed travel itinerary for real-time help with the booking. Any modifications, exchanges, or voidings made to a trip via support will incur a $25 booking change fee.
 {% include end-info.html %}
-
-</div>
diff --git a/docs/articles/new-expensify/travel/Manage-Travel-Member-Roles.md b/docs/articles/new-expensify/travel/Manage-Travel-Member-Roles.md
index eab24598b162..d1a9e68d9904 100644
--- a/docs/articles/new-expensify/travel/Manage-Travel-Member-Roles.md
+++ b/docs/articles/new-expensify/travel/Manage-Travel-Member-Roles.md
@@ -2,7 +2,6 @@
 title: Manage Travel Member Roles
 description: Modify member roles within Expensify Travel
 ---
-<div id="new-expensify" markdown="1">
 
 Admins can assign roles to different travel members to determine who they can book travel for (whether for themselves and/or for others) and whether they can adjust administrative settings.
   
@@ -21,5 +20,3 @@ To assign a role to a travel member,
     - View analytics and metrics 
     - Use the Safety feature
 6. Click **Save**. 
-
-</div>
diff --git a/docs/articles/new-expensify/travel/Track-Travel-Analytics.md b/docs/articles/new-expensify/travel/Track-Travel-Analytics.md
index c50fa11c7a15..041da33da987 100644
--- a/docs/articles/new-expensify/travel/Track-Travel-Analytics.md
+++ b/docs/articles/new-expensify/travel/Track-Travel-Analytics.md
@@ -2,49 +2,6 @@
 title: Track Travel Analytics
 description: Get insight into company travel bookings to ensure real-time duty of care reporting and travel policy compliance. 
 ---
-<div id="expensify-classic" markdown="1">
-
-Expensify Travel provides insights into company travel bookings to ensure real-time duty of care reporting and travel policy compliance. These analytics help Workspace Admins:
-
-- See global employee locations with a real-time employee location map
-- Analyze travel spend based on details such as trip, traveler, or carrier
-- Monitor booking trends and adherence to travel policy compliance
-- Generate environmental, social, and governance (ESG) reporting
-
-To view your analytics, 
-
-1. Click Travel in the left menu.
-2. Click **Book or Manage Travel**. 
-3. Click the **Analytics** tab at the top of the screen. 
-
-From here, you can see a variety of reports, including the Duty of Care report, Spend, and ESG metrics. 
-
-## Duty of Care report 
-
-Duty of care is a legal obligation for employers to safeguard the health, safety, and well-being of their employees both in the office and during business trips. With Expensify’s Duty of Care analytics, you can view a global map showing real-time employee locations. 
-
-1. Click the **Analytics** tab at the top and select Travelers.
-2. Use the map to see employee locations. If desired, you can use the filters above the map to show past and future trips, or travel booked to specific locations.
-
-## Spend and compliance report 
-
-Workspace Admins can analyze travel data based on a variety of trip, traveler, and compliance attributes. 
-
-1. Click the **Analytics** tab at the top and select Company Reports.
-2. Review the overview data, or select a specific report from the left menu.
-3. Click the three dot menu on the right of the screen to download the report as a PDF.
-
-## ESG report 
-
-Expensify Travel provides various ESG metrics, including carbon footprint analysis, sustainability scores, and ethical travel spending. 
-
-1. Click the **Analytics** tab at the top and select Company Reports.
-2. Click **Air Manifest** in the left menu. 
-3. Review the CO2 Emissions column in the table.
-
-</div>
-
-<div id="new-expensify" markdown="1">
 
 Expensify Travel provides insights into company travel bookings to ensure real-time duty of care reporting and travel policy compliance. These analytics help Workspace Admins:
 
@@ -83,5 +40,3 @@ Expensify Travel provides various ESG metrics, including carbon footprint analys
 1. Click the **Analytics** tab at the top and select Company Reports.
 2. Click **Air Manifest** in the left menu. 
 3. Review the CO2 Emissions column in the table.
-
-</div>


Reviews:
user: login: srikarparsi
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-15T19:06:00Z
user: login: srikarparsi
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-15T19:06:15Z
user: login: srikarparsi
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-15T19:09:43Z
user: login: greg-schroeder
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-16T17:07:27Z
user: login: greg-schroeder
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-16T17:13:33Z
user: login: greg-schroeder
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-04-16T17:13:54Z
user: login: strepanier03
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-16T21:09:00Z
user: login: strepanier03
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-16T21:09:37Z
user: login: srikarparsi
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-04-17T05:39:44Z

Review comments:
diff_hunk: @@ -2,58 +2,6 @@
 title: Approve travel expenses
 description: Determine how travel expenses are approved
 ---
-<div id="expensify-classic" markdown="1">
-
-Travel expenses follow the same approval workflow as other expenses. Admins can configure travel expenses to be approved as soft approval, hard approval or passive approval. The approval method for in-policy and out-of-policy bookings can be managed under the **Policies** section in the **Program** menu for Expensify Travel. 
- 
-- **Soft Approval**: Bookings are automatically approved as long as a manager does not decline them within 24 hours. However, this also means that if a manager does not decline the expenses, the arrangements will be booked even if they are out of policy. If a booking is declined, it is refunded based on the voiding/refund terms of the service provider.
-- **Hard Approval**: Bookings are automatically canceled/voided and refunded if a manager does not approve them within 24 hours. 
-- **Passive Approval**: Managers are informed of out-of-policy travel, but there is no action to be taken.
-
-# Set Approval Method
-
-1. Click the **Travel** tab.
-2. Click **Book or manage travel**.
-3. Click the **Program** tab at the top and select **Policies**.
-4. Under General, select approval methods for Flights, Hotels, Cars and Rail.
-
-![Screenshot of Expensify Travel policy approval settings](https://help.expensify.com/assets/images/Travel_Policy.png){:width="100%"}
-
-# Approve Travel
-
-![Screenshot of Expensify Travel approval email](https://help.expensify.com/assets/images/travel-soft-approval.png){:width="100%"}
-
-## Soft Approval
-
-Once an employee has booked a trip, their approver will receive an email notifying them of the booking with a prompt to decline it if needed. 
-
-- To approve the booking, no action is required. 
-- To decline the booking, click **Decline booking** within 24 hours. Then click **Deny Booking**.
-
-## Hard Approval
-
-Once an employee has booked a trip, their approver will receive an email notifying them of the booking with a prompt to accept or decline the booking.
-
-To approve the booking, click **Approve booking**. Then click **Approve**.
-To decline the booking, click **Decline booking**. Then click **Deny**. 
-
-# FAQ
-
-## Are extended approval windows given for trips booked over the weekend or during company holidays?
-
-No, the approval window will always be 24 hours from when the trip is booked. 
-
-## How does Expensify Travel handle approvals when the assigned approver is out of office? 
-
-It is recommended to have multiple approvers for travel, as there is no delegated approval for out-of-office approvers.
-
-## Can travelers upload a document when submitting a trip for approval?
-
-Travelers are unable to add a document when submitting a trip for approval, but the company can add a ‘reason code’ in the Out of Policy rules that the traveler can complete at checkout. The traveler can then add the document to the expense report in Expensify when submitting the report. 
-
-</div>
-
-<div id="new-expensify" markdown="1">
path: docs/articles/new-expensify/travel/Approve-travel-expenses.md
user: login: srikarparsi
body: I don't think we should have removed this div? Do you think we could add it back @strepanier03?
created_at: 2025-04-15T19:06:00Z
author_association: CONTRIBUTOR
diff_hunk: @@ -101,5 +49,3 @@ It is recommended to have multiple approvers for travel, as there is no delegate
 ## Can travelers upload a document when submitting a trip for approval?
 
 Travelers are unable to add a document when submitting a trip for approval, but the company can add a ‘reason code’ in the Out of Policy rules that the traveler can complete at checkout. The traveler can then add the document to the expense report in Expensify when submitting the report. 
-
-</div>
path: docs/articles/new-expensify/travel/Approve-travel-expenses.md
user: login: srikarparsi
body: This one as well, let me know if you would like me to do it and I can help :)
created_at: 2025-04-15T19:06:15Z
author_association: CONTRIBUTOR
diff_hunk: @@ -2,58 +2,6 @@
 title: Approve travel expenses
 description: Determine how travel expenses are approved
 ---
-<div id="expensify-classic" markdown="1">
-
-Travel expenses follow the same approval workflow as other expenses. Admins can configure travel expenses to be approved as soft approval, hard approval or passive approval. The approval method for in-policy and out-of-policy bookings can be managed under the **Policies** section in the **Program** menu for Expensify Travel. 
- 
-- **Soft Approval**: Bookings are automatically approved as long as a manager does not decline them within 24 hours. However, this also means that if a manager does not decline the expenses, the arrangements will be booked even if they are out of policy. If a booking is declined, it is refunded based on the voiding/refund terms of the service provider.
-- **Hard Approval**: Bookings are automatically canceled/voided and refunded if a manager does not approve them within 24 hours. 
-- **Passive Approval**: Managers are informed of out-of-policy travel, but there is no action to be taken.
-
-# Set Approval Method
-
-1. Click the **Travel** tab.
-2. Click **Book or manage travel**.
-3. Click the **Program** tab at the top and select **Policies**.
-4. Under General, select approval methods for Flights, Hotels, Cars and Rail.
-
-![Screenshot of Expensify Travel policy approval settings](https://help.expensify.com/assets/images/Travel_Policy.png){:width="100%"}
-
-# Approve Travel
-
-![Screenshot of Expensify Travel approval email](https://help.expensify.com/assets/images/travel-soft-approval.png){:width="100%"}
-
-## Soft Approval
-
-Once an employee has booked a trip, their approver will receive an email notifying them of the booking with a prompt to decline it if needed. 
-
-- To approve the booking, no action is required. 
-- To decline the booking, click **Decline booking** within 24 hours. Then click **Deny Booking**.
-
-## Hard Approval
-
-Once an employee has booked a trip, their approver will receive an email notifying them of the booking with a prompt to accept or decline the booking.
-
-To approve the booking, click **Approve booking**. Then click **Approve**.
-To decline the booking, click **Decline booking**. Then click **Deny**. 
-
-# FAQ
-
-## Are extended approval windows given for trips booked over the weekend or during company holidays?
-
-No, the approval window will always be 24 hours from when the trip is booked. 
-
-## How does Expensify Travel handle approvals when the assigned approver is out of office? 
-
-It is recommended to have multiple approvers for travel, as there is no delegated approval for out-of-office approvers.
-
-## Can travelers upload a document when submitting a trip for approval?
-
-Travelers are unable to add a document when submitting a trip for approval, but the company can add a ‘reason code’ in the Out of Policy rules that the traveler can complete at checkout. The traveler can then add the document to the expense report in Expensify when submitting the report. 
-
-</div>
-
-<div id="new-expensify" markdown="1">
path: docs/articles/new-expensify/travel/Approve-travel-expenses.md
user: login: srikarparsi
body: I believe this is what renders the Expensify Classic/New badge in the top right. But maybe we don't use this structure anymore?

<img width="1091" alt="image" src="https://github.com/user-attachments/assets/a0aecca2-7984-4530-9db7-d622c907b7a4" />

created_at: 2025-04-15T19:09:43Z
author_association: CONTRIBUTOR
diff_hunk: @@ -2,58 +2,6 @@
 title: Approve travel expenses
 description: Determine how travel expenses are approved
 ---
-<div id="expensify-classic" markdown="1">
-
-Travel expenses follow the same approval workflow as other expenses. Admins can configure travel expenses to be approved as soft approval, hard approval or passive approval. The approval method for in-policy and out-of-policy bookings can be managed under the **Policies** section in the **Program** menu for Expensify Travel. 
- 
-- **Soft Approval**: Bookings are automatically approved as long as a manager does not decline them within 24 hours. However, this also means that if a manager does not decline the expenses, the arrangements will be booked even if they are out of policy. If a booking is declined, it is refunded based on the voiding/refund terms of the service provider.
-- **Hard Approval**: Bookings are automatically canceled/voided and refunded if a manager does not approve them within 24 hours. 
-- **Passive Approval**: Managers are informed of out-of-policy travel, but there is no action to be taken.
-
-# Set Approval Method
-
-1. Click the **Travel** tab.
-2. Click **Book or manage travel**.
-3. Click the **Program** tab at the top and select **Policies**.
-4. Under General, select approval methods for Flights, Hotels, Cars and Rail.
-
-![Screenshot of Expensify Travel policy approval settings](https://help.expensify.com/assets/images/Travel_Policy.png){:width="100%"}
-
-# Approve Travel
-
-![Screenshot of Expensify Travel approval email](https://help.expensify.com/assets/images/travel-soft-approval.png){:width="100%"}
-
-## Soft Approval
-
-Once an employee has booked a trip, their approver will receive an email notifying them of the booking with a prompt to decline it if needed. 
-
-- To approve the booking, no action is required. 
-- To decline the booking, click **Decline booking** within 24 hours. Then click **Deny Booking**.
-
-## Hard Approval
-
-Once an employee has booked a trip, their approver will receive an email notifying them of the booking with a prompt to accept or decline the booking.
-
-To approve the booking, click **Approve booking**. Then click **Approve**.
-To decline the booking, click **Decline booking**. Then click **Deny**. 
-
-# FAQ
-
-## Are extended approval windows given for trips booked over the weekend or during company holidays?
-
-No, the approval window will always be 24 hours from when the trip is booked. 
-
-## How does Expensify Travel handle approvals when the assigned approver is out of office? 
-
-It is recommended to have multiple approvers for travel, as there is no delegated approval for out-of-office approvers.
-
-## Can travelers upload a document when submitting a trip for approval?
-
-Travelers are unable to add a document when submitting a trip for approval, but the company can add a ‘reason code’ in the Out of Policy rules that the traveler can complete at checkout. The traveler can then add the document to the expense report in Expensify when submitting the report. 
-
-</div>
-
-<div id="new-expensify" markdown="1">
path: docs/articles/new-expensify/travel/Approve-travel-expenses.md
user: login: greg-schroeder
body: Hmm, I think this intended based on the original GH. @strepanier03 said:

>If you view a help doc in the Travel repo on New Expensify, you can toggle between Classic and New Expensify docs.
>
>It is very difficult for customers using Classic to logically locate the help docs on our help site unless they use search.
>
>AgentZero has difficulty readying docs in the help site that uses the toggle functionality between classic and new.

created_at: 2025-04-16T17:07:27Z
author_association: CONTRIBUTOR
diff_hunk: @@ -2,58 +2,6 @@
 title: Approve travel expenses
 description: Determine how travel expenses are approved
 ---
-<div id="expensify-classic" markdown="1">
-
-Travel expenses follow the same approval workflow as other expenses. Admins can configure travel expenses to be approved as soft approval, hard approval or passive approval. The approval method for in-policy and out-of-policy bookings can be managed under the **Policies** section in the **Program** menu for Expensify Travel. 
- 
-- **Soft Approval**: Bookings are automatically approved as long as a manager does not decline them within 24 hours. However, this also means that if a manager does not decline the expenses, the arrangements will be booked even if they are out of policy. If a booking is declined, it is refunded based on the voiding/refund terms of the service provider.
-- **Hard Approval**: Bookings are automatically canceled/voided and refunded if a manager does not approve them within 24 hours. 
-- **Passive Approval**: Managers are informed of out-of-policy travel, but there is no action to be taken.
-
-# Set Approval Method
-
-1. Click the **Travel** tab.
-2. Click **Book or manage travel**.
-3. Click the **Program** tab at the top and select **Policies**.
-4. Under General, select approval methods for Flights, Hotels, Cars and Rail.
-
-![Screenshot of Expensify Travel policy approval settings](https://help.expensify.com/assets/images/Travel_Policy.png){:width="100%"}
-
-# Approve Travel
-
-![Screenshot of Expensify Travel approval email](https://help.expensify.com/assets/images/travel-soft-approval.png){:width="100%"}
-
-## Soft Approval
-
-Once an employee has booked a trip, their approver will receive an email notifying them of the booking with a prompt to decline it if needed. 
-
-- To approve the booking, no action is required. 
-- To decline the booking, click **Decline booking** within 24 hours. Then click **Deny Booking**.
-
-## Hard Approval
-
-Once an employee has booked a trip, their approver will receive an email notifying them of the booking with a prompt to accept or decline the booking.
-
-To approve the booking, click **Approve booking**. Then click **Approve**.
-To decline the booking, click **Decline booking**. Then click **Deny**. 
-
-# FAQ
-
-## Are extended approval windows given for trips booked over the weekend or during company holidays?
-
-No, the approval window will always be 24 hours from when the trip is booked. 
-
-## How does Expensify Travel handle approvals when the assigned approver is out of office? 
-
-It is recommended to have multiple approvers for travel, as there is no delegated approval for out-of-office approvers.
-
-## Can travelers upload a document when submitting a trip for approval?
-
-Travelers are unable to add a document when submitting a trip for approval, but the company can add a ‘reason code’ in the Out of Policy rules that the traveler can complete at checkout. The traveler can then add the document to the expense report in Expensify when submitting the report. 
-
-</div>
-
-<div id="new-expensify" markdown="1">
path: docs/articles/new-expensify/travel/Approve-travel-expenses.md
user: login: greg-schroeder
body: Seems to me that she wants to remove the ability to switch and just have this article be NewDot only, which makes this change correct, no?
created_at: 2025-04-16T17:13:33Z
author_association: CONTRIBUTOR
diff_hunk: @@ -2,58 +2,6 @@
 title: Approve travel expenses
 description: Determine how travel expenses are approved
 ---
-<div id="expensify-classic" markdown="1">
-
-Travel expenses follow the same approval workflow as other expenses. Admins can configure travel expenses to be approved as soft approval, hard approval or passive approval. The approval method for in-policy and out-of-policy bookings can be managed under the **Policies** section in the **Program** menu for Expensify Travel. 
- 
-- **Soft Approval**: Bookings are automatically approved as long as a manager does not decline them within 24 hours. However, this also means that if a manager does not decline the expenses, the arrangements will be booked even if they are out of policy. If a booking is declined, it is refunded based on the voiding/refund terms of the service provider.
-- **Hard Approval**: Bookings are automatically canceled/voided and refunded if a manager does not approve them within 24 hours. 
-- **Passive Approval**: Managers are informed of out-of-policy travel, but there is no action to be taken.
-
-# Set Approval Method
-
-1. Click the **Travel** tab.
-2. Click **Book or manage travel**.
-3. Click the **Program** tab at the top and select **Policies**.
-4. Under General, select approval methods for Flights, Hotels, Cars and Rail.
-
-![Screenshot of Expensify Travel policy approval settings](https://help.expensify.com/assets/images/Travel_Policy.png){:width="100%"}
-
-# Approve Travel
-
-![Screenshot of Expensify Travel approval email](https://help.expensify.com/assets/images/travel-soft-approval.png){:width="100%"}
-
-## Soft Approval
-
-Once an employee has booked a trip, their approver will receive an email notifying them of the booking with a prompt to decline it if needed. 
-
-- To approve the booking, no action is required. 
-- To decline the booking, click **Decline booking** within 24 hours. Then click **Deny Booking**.
-
-## Hard Approval
-
-Once an employee has booked a trip, their approver will receive an email notifying them of the booking with a prompt to accept or decline the booking.
-
-To approve the booking, click **Approve booking**. Then click **Approve**.
-To decline the booking, click **Decline booking**. Then click **Deny**. 
-
-# FAQ
-
-## Are extended approval windows given for trips booked over the weekend or during company holidays?
-
-No, the approval window will always be 24 hours from when the trip is booked. 
-
-## How does Expensify Travel handle approvals when the assigned approver is out of office? 
-
-It is recommended to have multiple approvers for travel, as there is no delegated approval for out-of-office approvers.
-
-## Can travelers upload a document when submitting a trip for approval?
-
-Travelers are unable to add a document when submitting a trip for approval, but the company can add a ‘reason code’ in the Out of Policy rules that the traveler can complete at checkout. The traveler can then add the document to the expense report in Expensify when submitting the report. 
-
-</div>
-
-<div id="new-expensify" markdown="1">
path: docs/articles/new-expensify/travel/Approve-travel-expenses.md
user: login: strepanier03
body: Yes, sorry, I could have made that clearer. I purposely removed the /div because we want to separate New Expensify and Classic, and remove the ability to see the tag at the top right or switch between platforms in the article itself. 
created_at: 2025-04-16T21:09:00Z
author_association: CONTRIBUTOR
diff_hunk: @@ -101,5 +49,3 @@ It is recommended to have multiple approvers for travel, as there is no delegate
 ## Can travelers upload a document when submitting a trip for approval?
 
 Travelers are unable to add a document when submitting a trip for approval, but the company can add a ‘reason code’ in the Out of Policy rules that the traveler can complete at checkout. The traveler can then add the document to the expense report in Expensify when submitting the report. 
-
-</div>
path: docs/articles/new-expensify/travel/Approve-travel-expenses.md
user: login: strepanier03
body: We want the /div removed so this is correct.
created_at: 2025-04-16T21:09:37Z
author_association: CONTRIBUTOR

PR comments:
user: login: OSBotify
created_at: 2025-04-15T16:15:20Z
body: A preview of your ExpensifyHelp changes have been deployed to https://d07ab858.helpdot.pages.dev ⚡️
<!-- Created by actions-cool/maintain-one-comment -->
author_association: CONTRIBUTOR
user: login: strepanier03
created_at: 2025-04-15T16:16:57Z
body: The build looks good, but my Mac is restarting for an OS update, so I'll do the rest of the changes to the other docs once I'm back.
author_association: CONTRIBUTOR
user: login: strepanier03
created_at: 2025-04-15T16:40:07Z
body: I updated the rest of the docs, I'll let the build do it's thing and then review each one.
author_association: CONTRIBUTOR
user: login: melvin-bot[bot]
created_at: 2025-04-15T17:06:05Z
body: ### Concierge reviewer checklist:

 - [x] **I have verified the accuracy of the article**
    - [ ] The article is within a hub that makes sense, and the navigation is correct
    - [ ] All processes, screenshots, and examples align with current product behavior.
    - [ ] All links within the doc have been verified for correct destination and functionality.
 - [x] **I have verified the readability of the article**
    - [ ] The article's language is clear, concise, and free of jargon.
    - [ ] The grammar, spelling, and punctuation are correct.
    - [ ] The article contains at least one image, or that an image is not necessary
- [x] **I have verified the formatting of the article**
    - [ ] The article has consistent formatting (headings, bullet points, etc.) with other HelpDot articles and that aligns with the [HelpDot formatting standards](https://stackoverflowteams.com/c/expensify/questions/17353).
    - [ ] The article has proper text spacing and breaks for readability.
- [x] **I have verified the article has the appropriate tone and style**
    - [ ] The article's tone is professional, friendly, and suitable for the target audience.
    - [ ] The article's tone, terminology, and voice are consistent throughout.
- [x] **I have verified the overall quality of the article**
    - [ ] The article is not missing any information, nor does it contain redundant information.
    - [ ] The article fully addresses user needs.
- [x] **I have verified that all requested improvements have been addressed**

For more detailed instructions on completing this checklist, see [How do I review a HelpDot PR as a Concierge Team member?](https://stackoverflowteams.com/c/expensify/questions/20516)

cc @greg-schroeder

author_association: NONE
user: login: melvin-bot[bot]
created_at: 2025-04-15T17:06:08Z
body: @srikarparsi @greg-schroeder One of you needs to copy/paste the Reviewer Checklist from [here](https://raw.githubusercontent.com/Expensify/App/main/contributingGuides/REVIEWER_CHECKLIST.md) into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]
author_association: NONE
user: login: strepanier03
created_at: 2025-04-15T17:06:57Z
body: I've reviewed each doc in the build and they all look perfect. 

tl;dr: The purpose of this PR is just to remove the Classic copy from the New Expensify travel hub. I already created the travel hub in Classic and put copies of the classic docs in there.
author_association: CONTRIBUTOR
user: login: strepanier03
created_at: 2025-04-15T17:07:19Z
body: @greg-schroeder @srikarparsi - This is ready for you :) thanks for the reviews!
author_association: CONTRIBUTOR
user: login: srikarparsi
created_at: 2025-04-15T19:03:29Z
body: ## Reviewer Checklist

- [x] I have verified the author checklist is complete (all boxes are checked off).
- [x] I verified the correct issue is linked in the `### Fixed Issues` section above
- [x] I verified testing steps are clear and they cover the changes made in this PR
    - [x] I verified the steps for local testing are in the `Tests` section
    - [x] I verified the steps for Staging and/or Production testing are in the `QA steps` section
    - [x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    - [x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
- [x] I checked that screenshots or videos are included for tests on [all platforms](https://github.com/Expensify/App/blob/main/contributingGuides/CONTRIBUTING.md#make-sure-you-can-test-on-all-platforms)
- [x] I included screenshots or videos for tests on [all platforms](https://github.com/Expensify/App/blob/main/contributingGuides/CONTRIBUTING.md#make-sure-you-can-test-on-all-platforms)
- [x] I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
- [x] I verified tests pass on **all platforms** & I tested again on:
    - [x] Android: Native
    - [x] Android: mWeb Chrome
    - [x] iOS: Native
    - [x] iOS: mWeb Safari
    - [x] MacOS: Chrome / Safari
    - [x] MacOS: Desktop
- [x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
- [x] I verified proper code patterns were followed (see [Reviewing the code](https://github.com/Expensify/App/blob/main/contributingGuides/PR_REVIEW_GUIDELINES.md#reviewing-the-code))
    - [x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. `toggleReport` and not `onIconClick`).
    - [x] I verified that comments were added to code that is not self explanatory
    - [x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    - [x] I verified any copy / text shown in the product is localized by adding it to `src/languages/*` files and using the [translation method](https://github.com/Expensify/App/blob/4bd99402cebdf4d7394e0d1f260879ea238197eb/src/components/withLocalize.js#L60)
    - [x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the [localization methods](https://github.com/Expensify/App/blob/4bd99402cebdf4d7394e0d1f260879ea238197eb/src/components/withLocalize.js#L60-L68)
    - [x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    - [x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    - [x] I verified the JSDocs style guidelines (in [`STYLE.md`](https://github.com/Expensify/App/blob/main/contributingGuides/STYLE.md#jsdocs)) were followed
- [x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
- [x] I verified that this PR follows the guidelines as stated in the [Review Guidelines](https://github.com/Expensify/App/blob/main/contributingGuides/PR_REVIEW_GUIDELINES.md)
- [x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like `Avatar`, I verified the components using `Avatar` have been tested & I retested again)
- [x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
- [x] I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
- [x] If a new component is created I verified that:
    - [x] A similar component doesn't exist in the codebase
    - [x] All props are defined accurately and each prop has a `/** comment above it */`
    - [x] The file is named correctly
    - [x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    - [x] The only data being stored in the state is data necessary for rendering and nothing else
    - [x] For Class Components, any internal methods passed to components event handlers are bound to `this` properly so there are no scoping issues (i.e. for `onClick={this.submit}` the method `this.submit` should be bound to `this` in the constructor)
    - [x] Any internal methods bound to `this` are necessary to be bound (i.e. avoid `this.submit = this.submit.bind(this);` if `this.submit` is never passed to a component event handler like `onClick`)
    - [x] All JSX used for rendering exists in the render method
    - [x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
- [x] If any new file was added I verified that:
    - [x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
- [x] If a new CSS style is added I verified that:
    - [x] A similar style doesn't already exist
    - [x] The style can't be created with an existing [StyleUtils](https://github.com/Expensify/App/blob/main/src/utils/index.ts) function (i.e. `StyleUtils.getBackgroundAndBorderStyle(theme.componentBG`)
- [x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
- [x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like `Avatar` is modified, I verified that `Avatar` is working as expected in all cases)
- [x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
- [x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
- [x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    - [x] I verified that all the inputs inside a form are aligned with each other.
    - [x] I added `Design` label and/or tagged `@Expensify/design` so the design team can review the changes.
- [x] If a new page is added, I verified it's using the `ScrollView` component to make it scrollable when more elements are added to the page.
- [x] For any bug fix or new feature in this PR, I verified that sufficient [unit tests](https://github.com/Expensify/App/blob/main/tests/README.md) are included to prevent regressions in this flow.
- [x] If the `main` branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the `Test` steps.
- [x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

### Screenshots/Videos
<details>
<summary>Android: Native</summary>

<!-- add screenshots or videos here -->

</details>

<details>
<summary>Android: mWeb Chrome</summary>

<!-- add screenshots or videos here -->

</details>

<details>
<summary>iOS: Native</summary>

<!-- add screenshots or videos here -->

</details>

<details>
<summary>iOS: mWeb Safari</summary>

<!-- add screenshots or videos here -->

</details>

<details>
<summary>MacOS: Chrome / Safari</summary>

<!-- add screenshots or videos here -->

</details>

<details>
<summary>MacOS: Desktop</summary>

<!-- add screenshots or videos here -->

</details>

author_association: CONTRIBUTOR
user: login: strepanier03
created_at: 2025-04-16T21:11:12Z
body: Removing the /div is correct. We want to separate the platforms and not allow for toggling between platforms on a single help article. It was a format we started to adopt and have now moved away from. It also plays havoc with AZ reading the help site. 
author_association: CONTRIBUTOR
user: login: srikarparsi
created_at: 2025-04-17T05:34:50Z
body: Ah sounds good, thanks for clarifying!
author_association: CONTRIBUTOR
user: login: github-actions[bot]
created_at: 2025-04-18T20:42:39Z
body: 🚀 [Deployed](https://github.com/Expensify/App/actions/runs/14540961916) to staging by https://github.com/srikarparsi in version: 9.1.30-0 🚀

platform | result
---|---
🖥 desktop 🖥|success ✅
🕸 web 🕸|success ✅
🤖 android 🤖|success ✅
🍎 iOS 🍎|success ✅
author_association: CONTRIBUTOR
user: login: github-actions[bot]
created_at: 2025-04-21T23:21:19Z
body: 🚀 [Deployed](https://github.com/Expensify/App/actions/runs/14582998832) to production by https://github.com/AndrewGable in version: 9.1.30-4 🚀

platform | result
---|---
🖥 desktop 🖥|success ✅
🕸 web 🕸|success ✅
🤖 android 🤖|failure ❌
🍎 iOS 🍎|success ✅
author_association: CONTRIBUTOR