How to use the Information Architecture Generator.
Information architecture should reflect user tasks and content relationships. Avoid copying the organization's internal structure when visitors do not think in those terms.
Make the workflow fit your task.
Group content according to user tasks and meaningful relationships, then label destinations in language visitors recognize. Test where representative items belong and identify cross-links for content that supports more than one journey.
- What you provide
- Content inventory and user tasks.
- What you get
- Proposed navigation hierarchy with rationale.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Content includes invoices, payment methods and export instructions.
Completed example
Group billing tasks together and place export guidance where users manage reports, with clear cross-links where needed.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should navigation mirror the organization's departments?
Use that structure only when it matches users' needs. Internal ownership and visitor understanding are often different organizing principles.
Why do users expect the same item in several places?
Identify the primary home and useful cross-links or alternate paths. A single hierarchy does not have to carry every relationship.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑