In my information architecture work I often come across navigation problems that have generally applicable solutions. Here's an example of a "navigation pattern" that you will hopefully find useful.
A user needs to add, edit and delete items.
Click thumbnail to view image
When to use
- In an application that is task and workflow oriented.
- When the user is expected to perform one task at a time to complete an action.
- Suitable for devices that are not feature-rich, such as mobile phones.
- Self-contained, has a minimal number of screens.
- Indicates page transitions clearly.
- Provides confirmation for an accomplished task.
- Navigable with links.