This note gives guidance outlines the naming and url conventions for organizing monthly posts, where the structure allows for a clear historical evolution and supports both daily and non-daily entries ¹, which also serves as the monthly overview and as an example of what a typical monthly overview post looks like ².

monthly overview

First post in a month covers:

• Conventions (e.g. post structure, tags, numbering),
• Guidelines (how to write, categorize, etc.),
• Plans (goals, projects, intentions for the month),
• Summaries or resumes (what happened or will happen),
• Meta info (any behind-the-scenes notes),

where not all are implemented immediatly and also can be subject to change.

post prefixes

• 00 — Reserved for the monthly overview post.
• 01 to 31 — Reserved for daily notes or plans corresponding to calendar days.
• 32 to 99 — Reserved for other posts in the month (e.g., reflections, event notes, topic-specific entries).
• Extended range — If needed, additional posts can use alphanumeric prefixes starting from a0 to a9, then b0 to z9.

url structure

Each post URL consists of three parts:

• Year: Two-digit year (e.g., 25 for 2025),
• Month: One-letter code (a = January, b = February, …, l = December),
• Post ID: Two-digit or extended alphanumeric prefix (e.g., 00, 15, 98, a3, z7).

Example URL:

• /25a00/ → January 2025 monthly overview,
• /25c15/ → March 15th daily note,
• /25g99/ → July 2025 miscellaneous post,
• /25la2/ → December 2025 overflow post.

table

• Status: 0 (unprocessed), 1 (processed).
• Symbols: p (planned), s (started), u (unfinished), e (ended), c (continued), x (uncertain) ³.

notes

• Current url structure is limited to 2099 ⁴ and must be later considered to advance.
• Daily note will use notelist shortcode ⁵ and it should be the first note in a day, but it might be not today.

refs