Naming Conventions

A nomenclature “Naming Convention” is a system for naming things in a specific way. It can be used to create a consistent and organized way to refer to things in a specific context.

Chill Naming

Uses a two-digit incremental number (01–89), followed by a dot and a name in Train Case (each word capitalized and separated by hyphens).

Block Naming

Uses increments of 100 (e.g., 100, 200, 300), followed by a dot and a name in UPPERCASE.
This is a variant of Chill Naming, and its Ideal for top-level or broad categories

Control Naming

This follows a variable-based structure, where each part is defined by the user’s own criteria. Although parts may share patterns or context, the structure is flexible and tailored individually to each case, making it ideal for managing projects and tasks with contextual control and clarity.

Control Naming (for Folders)

Used by Workboard Nodes, this structure was designed for quick recognition and easy filtering between projects.

That is usually separated by three main Stages joined by underscores:

TRACKING _ METADATA _ NAME

Each stage contains the following structure:

<Id><Traker>_<Date><Breadcrumb><Holder>_<Name>

Element	Brief description
*Id	A code label that identifies the type of workboard
*Tracker	A sequential index of 3-digit that provides chronological order
Date	A timestamp within in parentheses, the common format is YY-MM-DD
Breadcrumb	Its like a category tag, typically aligned with the parent folder’s category
Holder	Its the owner or client always within in brackets
*Name	A descriptive phrase that helps identify purpose or content

*This element is required for this naming convention

Use Example

Full Use Example:

Root/200.WORK/02.Vide-Edition/

📁 PJ.033_(23-03-03)-Video-Tutorials-[MikeWorldYt]_how-to-organize-documents

This one is quickly identified as an video edition project, seems a tutorial about how to organize documents that belongs to MikeWorldYt and probably deliveries on March 3rd.

Partial Use Example:

Root/400.ACADEMIC/12.Science/

📁 HW.024_(12G-U2)-Physics-_Electromagnetism-research

This one is Science Homework, seems a research about electromagnetism, its from a Student of 12th grade in their second unit of Physics.

Root/500.HOBBIES/03.Drawing/01.Courses/

📁 CR.015_Sketiching-for-storyboards

This one is just a Drawing Course about sketching for storyboards, seems its their 15th course.

Control Naming (for Files)

Used by Files, their main porpose is organize, filter and identify.

Seems complicated, but it is Copy-Pasteable

Although visually they usually have long file names, when a new file is added, usually just copy the name of a existing one and pasted with a couple of changes.
Practically it is incorporating quickly and easily to the system.

That is usually separated by three main Stages joined by underscores:

METADATA _ ID _ NAME

Each Stage countain the following structure:

<Date><Breadcrumb><Holder>_<Id>_<Name>

Element	Brief description
Date	A timestamp within in parentheses, the common format is YY-MM-DD
Breadcrumb	Its like a category tag, typically aligned with the parent folder’s category
Holder	Its the owner or client always within in brackets
Id	A short, descriptive label that identifies the content or focus of the workboard,
Name	A short, descriptive label that identifies the content or focus of the workboard,
Wildcard	Any element that aid to add more context, even if is repited

*This element is required for this naming convention

Root/100.PERSONAL/05.Finantials

📄 (23-03-03)-Citi-Bank-[Emma-C]_FST_Bank-statement March-2023.pdf
📄 (23-04-03)-Citi-Bank-[Emma-C]_FST_Bank-statement April-2023.pdf
📄 (23-04-11)-Citi-Bank-[Emma-C]_CNT_Mortgage-contract Houston.pdf ←
📄 (23-05-03)-Citi-Bank-[Emma-C]_FST_Bank-statement May-2023.pdf
 . . .

Elements of Naming Conventions

Identificators (for Workboards)

The identificator is a code label that identifies the type of workboard.
Some of the most common identificators are:

• PJ: Project
• PR: Practice
• HW: Homework
• CR: Course
• TK: Task

Identificators (for Files)

…

Tracker (for Workboards)

The tracker is a sequential index that provides chronological order and simple referencing.

While many systems can sort by date, a tracker provides a quick way to follow progress without relying on timestamps.

Used in tandem with the identificator, it instantly communicates the type and order of the workboard.

Use example

📁 PJ.005_(24-03-30) Tut . . . ← for projects
📁 PJ.006_(24-04-12) Sal . . .

📁 HW.015_Gramm . . . ← for school homeworks
📁 HW.016_Gramm . . .

Only need 3-digit counters

As a workboard node are temporary and meant to be eventually stored or removed, Its recommended just use 3-digit counters, this allows up to 999 items per type; if exceeded, the counter may will reset.

Date and Timestamps

Although labeled as “Date”, this element works like a flexible timestamp that adapts to context.
When is used must appear within in parentheses, to ensure quick visual identification.

This one is not required, but aid to visualize important time such as deadlines, milestones, start dates, periods, seasons, etc.

You may used these formats:

• YY-MM-DD (Year-Month-Day) — Most commonly, used for Start dates, Deadlines, deliveries, etc.
• YY-MM (Year-Month) — For monthly tracking, reports, or retainers.
• YY-QQ (Year-Quarter) — Used for Finantials Quarters (trimesters).
• YY-V.1, YY-V.2 (Year-Version) — For versioning or iterations.
• YY-U1 or YY-C1 (Year-Unit/Chapter) — For units or chapters in educational contexts.
• 9G, 10G, 12G (Grade) — For schoolar grades; 9th grade, 10th grade, 12th grade.
• S2, S3, S4 (Semester) — For School Semester, often used in curriculum tracking.

Breadcrumbs

A breadcrumb defines the contextual type of the workboard, usually based on the parent folder’s category.

This one is not required but completely recommended, Because acts like a category-tag, aiding as extra filter and avoiding the creation of more levels.

Use example

When use it, you create a visual grouping in the same level.

📁 02.Video-Edition
 ├── 📁 PJ.015_(25-04-01) Video-Tutorial [Sadvir]_How-To . . .
 ├── 📁 PJ.016_(25-04-08) Video-Tutorial [Sadvir]_Making . . .
 └── 📁 PJ.016_(25-04-11) Gameplay [Aradir]_Weather-simul . . .

Whitout use it

Otherwise, you force to create more levels to group them even if just have a few.

📁 02.Video-Edition
 ├── 📁 01.Video-Tutorials
 │    ├── 📁 PJ.015_(25-04-01) [Sadvir]_How-To . . .
 │    └── 📁 PJ.016_(25-04-08) [Sadvir]_Making . . .
 ├── 📁 02.Gameplay
 │    └──📁 PJ.016_(25-04-11) [Aradir]_Weather-simul . . .

Holders and Clients

The holder identifies who the workboard belongs (client, brand, organization, school, owner).
When is used must appear within in brackets, to ensure quick visual identification.

It provides ownership context and is especially useful when managing multiple clients or persons.

Use example

📁 HW.1 . . . ances [Oxford]_Revolving-deb . . . ← Institutions
📁 PJ.0 . . . eplay [Aradir]_Weather-simul . . . ← Client
📁 PR.0 . . . awing [Henry-Dav]_anatomy-po . . . ← even Yourself (Owner)

Recomendation

Try not use name that are too long or complex.
(e.g. “College-of-William-&-Mary-Law-School” instead of “W&M-Laws”)

Besides if you need to keep confidentiality or privacy, You could use a pseudo-name with aid a Client List document that could well be saved in another site.

Use example with a Client List

📁 PJ.0 . . . eplay [C-018-Ara]_Weather-simul . . .  ← Its Aradir, the client n.18
📁 PR.0 . . . eling [C-031-Bea]_Machu-Pichu-o . . .  ← Do you could guess who is?

Name (for Workboards)

This is a short, descriptive label that identifies the content or focus of the workboard,
In other words, its just the name or title.

Using train-case or kebab-case is recommended to separate any concepts amoung themselves.

Use example

📁 PJ.01 . . . ova]_landingpage-redesign pet-store
📁 HW.02 . . . Ark]_environmental-law-essay
📁 PJ.03 . . . dYt]_how-to-organize-documents

Name (for Files)

…

Wildcard

The <wildcard> element is a flexible placeholder that allows the user to append any additional element(s) to the filename as needed.

This can include duplicates or variations of existing elements like <Date>, <Holder>, <Id>, or entirely new metadata relevant to the specific use case. Its position and composition are user-defined, offering maximum customization when a fixed naming structure is not sufficient.

Use example

📁 PJ.01 . . . ova]_landingpage-redesign pet-store [John-Doe] ← Holder as Wildcard
📁 HW.02 . . . Ark]_environmental-law-essay (03-23) ← Date as Wildcard

Wildcard Use Cases :

Here we can see some Finantials Documents:

Root/100.PERSONAL/05.Finantials

📄 (23-03-03)-Citi-Bank-[Emma-C]_FST_Bank-statement March-2023.pdf
📄 (23-04-03)-Citi-Bank-[Emma-C]_FST_Bank-statement April-2023.pdf
📄 (23-04-11)-Citi-Bank-[Emma-C]_CNT_Mortgage-contract Houston.pdf ←
📄 (23-05-03)-Citi-Bank-[Emma-C]_FST_Bank-statement May-2023.pdf
 . . .

This one are using the Full Naming Convention following strict order, though here he has left a file between the bank statements

If we remove the date, we can solve it, and now is already separated

Root/100.PERSONAL/05.Finantials

📄 -Citi-Bank-[Emma-C]_CNT_Mortgage-contract Houston.pdf ←
📄 -Citi-Bank-[Emma-C]_FST_Bank-statement.pdf
📄 -Citi-Bank-[Emma-C]_FST_Bank-statement.pdf
📄 -Citi-Bank-[Emma-C]_FST_Bank-statement.pdf
 . . .

Though now get another issue, We’ve similar name files
Besides that the OS your computer will not let you, Could you identify what month each one is from?

So you should come back the date again, though not in the same order

Root/100.PERSONAL/05.Finantials

📄 -Citi-Bank-[Emma-C]_CNT_Mortgage-contract Houston.pdf
📄 -Citi-Bank-[Emma-C]_FST_Bank-statement (03-23) March.pdf
📄 -Citi-Bank-[Emma-C]_FST_Bank-statement (04-23) April.pdf
📄 -Citi-Bank-[Emma-C]_FST_Bank-statement (05-23) May.pdf
 . . .

Now in the last part, conbined in the name element.

---