Custom Workflow
PARA is just one way to organize Theme Notes in LifeOS -- it's not the only option. LifeOS's underlying mechanisms are flexible enough for you to customize workflows to suit your needs.
Theme Tags Are Universal Connectors
No matter what folder structure you use, Theme Tags are the bridge connecting Periodic Notes and Theme Notes. As long as you tag records in your daily notes, the corresponding Theme Notes will automatically collect those records.
This means folder structures can be freely adjusted without affecting the tag mechanism. You can replace PARA with any categorization method you prefer.
Custom Folder Structures
Beyond PARA
If PARA doesn't suit you, consider other organizational approaches. For example, the IPO (Input/Process/Output) model:
Or an even simpler division by domain:
The key is to choose a structure you can intuitively understand. The more the categorization aligns with your thinking habits, the easier it is to stick with.
Configuring Folder Paths
In settings, you can specify the folder paths that LifeOS recognizes. The system will organize the sidebar display and home view based on the configured paths.
Custom Periodic Note Templates
Every type of periodic note (daily, weekly, monthly, quarterly, yearly) can have a custom template.
Template File Location
Default templates are stored in the 0. 周期笔记/Templates/ directory. You can change the template path in settings.
Modifying Template Content
Open the corresponding template file and modify as needed. For example, if you don't need the "Role Dimension" breakdown, you can remove that section and keep only the "Key Focus Areas":
Or add your own sections, such as "Gratitude Journal" or "Mood Tracker."
Available LifeOS Code Blocks
The following code blocks can be used in templates, and the system will automatically render the corresponding content:
You can insert these code blocks anywhere in your templates, combining them to create a review and planning structure that suits you.
Custom Theme Note Templates
Each PARA folder can contain a Template.md file. When creating a new note in that folder, this template will be automatically applied.
For example, place a Template.md under 1. 项目/:
This way, the index structure is automatically generated each time you create a new project.
You can set different templates for different folders. Project notes might need task lists and deadlines, while resource notes might only need file lists and note indexes.
Workflow Examples
Writer's Workflow
In daily notes, use tags like #素材/AI or #草稿/年度总结 to associate records.
Student's Workflow
Plan study schedules by course in weekly notes; at semester's end, view accumulated study time per course.
Core Principles
No matter how you customize, a few principles are worth keeping:
- Keep Theme Tags consistent -- Tags are the foundation of all automatic indexing. Ensure your tag system is clear and consistent.
- Maintain Periodic Note rhythm -- The basic rhythm of daily and weekly notes is important for continuous recording. Content can be simplified, but don't break the rhythm.
- Keep review sections -- At minimum, keep
TaskRecordListByTimeandTaskDoneListByTimein weekly and monthly notes, letting the system summarize data for you. - Keep it simple -- Don't design an overly complex system. A simple system you're willing to open every day is better than a perfect system you're too lazy to use.
Related Topics
- Connection -- How Theme Tags connect the two systems
- Periodic Notes -- Default periodic note template reference
- Project Lifecycle -- Standard project management workflow
- Theme Notes -- Detailed explanation of the PARA classification method

