Skip to content

docs: update broken links to customizing admin panel location #16480

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
arnarb94 wants to merge 1 commit into
base: 3.x
Choose a base branch
from
+5 −5
Open

docs: update broken links to customizing admin panel location #16480

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
10 changes: 5 additions & 5 deletions docs/admin/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ The `admin` directory contains all the _pages_ related to the interface itself,
<Banner type="success">
**Tip:** The `(payload)` folder location is flexible. You can move it to match
your application's structure by updating the `routes` and `admin.importMap`
configuration. See [Customizing Admin Panel Location](./customizing-location)
configuration. See [Customizing Admin Panel Location](./admin-panel-location)
for step-by-step instructions.
</Banner>

Expand Down Expand Up @@ -246,7 +246,7 @@ app
<Banner type="info">
**Advanced Routing:** For complex scenarios like nesting the admin panel at
custom paths (e.g., `/admin/content`) or organizing multiple admin dashboards,
see [Customizing Admin Panel Location](./customizing-location).
see [Customizing Admin Panel Location](./admin-panel-location).
</Banner>

### Admin-level Routes
Expand Down Expand Up @@ -424,15 +424,15 @@ The following options are available for the `admin.toast` configuration:

### Can I move the Payload admin panel to a custom location?

Yes! Payload is flexible about where the admin panel lives. You can move it to custom routes like `/dashboard`, `/cms`, or nested paths like `/admin/content`. See [Customizing Admin Panel Location](./customizing-location) for step-by-step instructions.
Yes! Payload is flexible about where the admin panel lives. You can move it to custom routes like `/dashboard`, `/cms`, or nested paths like `/admin/content`. See [Customizing Admin Panel Location](./admin-panel-location) for step-by-step instructions.

### Which auto-generated files can I safely modify?

Most files in the `(payload)` folder are only created once and can be safely modified. Only the `importMap.js` file is regenerated automatically. See [Understanding Auto-Generated Files](./customizing-location#understanding-auto-generated-files) for a complete reference table.
Most files in the `(payload)` folder are only created once and can be safely modified. Only the `importMap.js` file is regenerated automatically. See [Understanding Auto-Generated Files](./admin-panel-location#understanding-auto-generated-files) for a complete reference table.

### Why does layout.tsx say "DO NOT MODIFY" if I need to edit it?

This warning is misleading. The `layout.tsx` file was generated during initial project setup but is never regenerated by Payload. It is safe to modify, especially when customizing your folder structure. See [About the "DO NOT MODIFY" Warning](./customizing-location#about-the-do-not-modify-warning) for details.
This warning is misleading. The `layout.tsx` file was generated during initial project setup but is never regenerated by Payload. It is safe to modify, especially when customizing your folder structure. See [About the "DO NOT MODIFY" Warning](./admin-panel-location#about-the-do-not-modify-warning) for details.

### What happens if I edit the import map file directly?

Expand Down
Loading