Legacy URL directory

Legacy GFX^TM Directory

Use this directory when a GFX^TM or older Fundy link does not resolve cleanly to one exact new page. The goal is to move users out of dead ends quickly, choose the right operational route, and keep archive context available when needed.

Choose the route

Pick one path in one decision pass

This page is a routing map, not a tool page. Open one destination only after the context check. If intent is clear, use direct routing. If intent is mixed or old paths are ambiguous, use search and archive context first.

Current Photoshop hubChoose this when files, shortcuts, actions, brushes, or KYS assets are the immediate action. Tools directoryChoose this for browser utility tasks, file tweaks, and practical one-off workflows. Guides libraryChoose this for step by step process support, task planning, and method choice before edits. Fundy searchChoose this when intent is uncertain or multiple possible destinations match the legacy path.

Route decision rules

Use this short matrix for every legacy hit:

If the old path name maps to a clearly equivalent current feature, route to the matching live page directly.
If the old path describes Photoshop only, route to the Photoshop hub and avoid archive detail pages.
If the old path is about utilities for image, color, css, or prompt craft, route to Tools, Image Tools, Color Tools, or AI Design depending on the first explicit verb in the path.
If the old path is about process, onboarding, or best practices, route to Guides.
If intent is unknown after one pass, route to Search with the user-facing phrase from the legacy slug, then route again based on top result class.

Concrete workflows

Use the following sequence to keep decisions consistent:

Read the incoming legacy link and extract intent tokens: topic, tool type, and expected output.
Check if the same intent exists as a current page family. If yes, create one direct handoff.
If no single match exists, choose the nearest practical family from Tools, Photoshop, Guides, or Search.
Record the legacy context only once, then send the user to current content so they continue with fresh workflow pages.
If the path references a deprecated file type or missing feature, stop routing to old duplicates and instead guide the user to the archive context and a modern equivalent.

Limits and stop conditions

Do not use this directory as a fallback catch-all for live tasks. Stop here only when a direct route is truly absent and keep the message tight.

Stop when the request is a current, high clarity action, such as opening a known tool, downloading an asset, or viewing a guide that already exists.
Stop creating clone pages for old links. Legacy pages must route, not reproduce old content.
Stop rewriting old URLs into hidden or unsupported workflows. Link must point to canonical, supportable tools and pages.
Stop when the result is too broad, for example a generic landing phrase with no task detail, and escalate to Search.
Stop if the intent contains upload-heavy or server-side inference behavior, and route to supported Fundy only.

Operational boundary and handoff priorities

The archive boundary is short by design. The handoff order is fixed to reduce duplicate friction:

Primary handoff: exact equivalent task in the live tool area.
Secondary handoff: Photoshop hub for editing-centric workflows and assets.
Tertiary handoff: guide or search when the legacy reference lacks clear action verbs.
Archive handoff: GFX^TM archive explanation when no safe route can be confirmed in one pass.

Useful next steps

GFX^TM Archive - Return to archive context and historical routing notes.
Search Fundy - Resolve ambiguous legacy paths with exact modern terms.
Fundy Downloads - Move here if the user asks for current downloadable assets.
Tools directory - Move here for direct browser utility actions once intent is confirmed.
Image tools - Use for image file processing tasks.
Color tools - Use for palette, contrast, and tone workflows.
AI design workflows - Use for prompt and AI-aided creative steps.

Why this route exists

Legacy links are still visited by scripts, bookmarks, and references. A strong route chooser keeps those visits useful by guiding users toward supported pages with minimal clicks, clear expectations, and explicit boundaries.

For operators, this reduces support load because the page does not promise content it cannot deliver. It provides clear decisions and practical paths to where work continues today.