Naming Add-Ons in Wireframes
This SOP explains how to use the right naming convention when creating new files for wireframing, emphasizing the inclusion of project names, add-ons if applicable, and specific tasks to maintain organization and searchability.
Step by step:
1. Overview
Add-ons should be managed within the scope of the main project, organized into appropriately named folders. This ensures that all related tasks and add-ons are easily accessible and logically grouped.
2. Guidelines for Creating and Naming Add-ons
Wireframe Creation:
- New Wireframes for Add-ons: Create a new wireframe for each add-on within the main project wireframe.
- Organization: All add-ons should be stored in a folder named "Add-ons" within the main project's scope.
Naming Conventions:
- Main Project Scope: Clearly indicate the main project scope in the naming structure.
- Folder Structure:
- Folder Name:
Add-ons
- Folder Name:
- Add-on Naming: Name each add-on following this format:
Project Name/Add-Ons Task Name (Task # + Task # + Task #)
3. Example
Project Name: Skyframe
-
Add-ons Folder:
Skyframe/Add-ons
-
Add-on Task Example:
Skyframe/Add-ons/New Feature Integration (Task 101 + Task 102 + Task 103)
4. Implementation
- Consistency: Ensure all team members follow these guidelines consistently for all projects.
- Documentation: Document each add-on within the main project's documentation, noting the specific tasks and their respective wireframes.