- Intuitive Naming: File names should be intuitive, simple, and concise.
- Reasoning : By keeping the naming intuitive and simple, it allow a user to easily search and find any documentation on the website.
- Simple File Names: File names should only contain letters, numbers, and the underscore (_) if a space is needed.
- Reasoning : Spaces and special characters cannot be read by all software. To avoid conflicts, it is best to always use a simple file name that does not include any spaces or special characters.
- Short File Names: File names should not exceed 25 characters.
- Reasoning : Most fields in modules that accept documents have a character size limit to ensure optimal functionality. Keeping the file names under 25 characters makes them compatible in any module.
Global navigation categories should be as broad and overarching as possible; e.g., government, services, about us, visitors, business etc.
- Reasoning : CivicPlus recommends this best practice to ensure the categories are broad enough to encompass many topics and flexible enough to accommodate future needs and updates; if an item doesn't house navigation below it, it is better suited for the left navigation, graphic button, or under another global. For example, if “Council” is a global navigation category, it limits the type of information users will expect to find under it. Using “Government” allows for the grouping of similar types of information.
Naming of pages, files, and links should be intuitive, simple, and concise.
- Reasoning: By keeping the naming intuitive and simple, it will limit any user misunderstanding the purpose of a global navigation item.
- Resource: Category Names to Avoid by Hoa Loranger with the Nielsen / Norman Group
- Related Topic: Learn about how to optimally name files in the system.