How to Start Using LifeOS

Tip

Already purchased Pro? Go directly to installation and activation.

If this is your first time using LifeOS, start with Start LifeOS in 10 Minutes and practice with the example vault first. This page is better used after the example works, when you want to understand folder structure, plugin installation, and manual setup.

Directory Structure Description

It is recommended to read through the directory structure once, as it helps to deepen your understanding!

The directory below is interactive and clickable. Click the + sign to expand!

-1. Capture // Used to practice the CODE model's Capture step
README.md// Capture index file
0. PeriodicNotes// Periodic notes system, each year has its own folder
README.md// Usage instructions for periodic notes
2023
Daily// Diary directory, each month has its own folder
06
2023-06-01.md// Diary note
2023-06-02.md
2023-06-03.md
Weekly// Weekly note directory
2023-21.md// Weekly note
2023-W22.md
Monthly// Monthly note directory
2023-06.md// Monthly note
2023-07.md
Quarterly// Quarterly note directory
2023-Q1.md// Quarterly note
2023-Q2.md
2023.md// Annual log
Templates// Template files for periodic notes, use corresponding templates when creating daily notes, weekly logs, monthly logs, quarterly logs, and annual logs
Daily.md
Monthly.md
Quarterly.md
Weekly.md
Yearly.md
1. Projects// PARA notes' Project category
README.md// Project usage instructions
Template.md// Project template file, used when creating a project
personal-brand-wot-sharing-meeting// Project example
Attachments
PPT materials
bit-logo.svg
warning.svg
ChatGPT
Why Frontend Engineering.md
What is Frontend Engineering.md
The Contents of Frontend Engineering.md
PPT Outline.md
2023-WOT-Share Session.README.md// Project index file, filename format requirement like XXX.README.md
Architecture Diagrams
Monorepo.svg
Polyrepo.svg
Rehearsal
Transcript.md
Existing Problems.md
Rehearsal Notes.md
Potential Audience Questions.md
Live Presentation Tips.md
Main Outline.md
Previous Themes.md
x company's Practice in Frontend Engineering.pdf
2. Areas// PARA notes' Area category
README.md// Area usage instructions
Template.md// Area template file, used when creating a project
personal-brand// Area example
personal-brand.README.md// Area index file, filename format requirement like XXX.README.md
work
work.README.md
marriage-relationship
marriage-relationship.README.md
parental-relationship
parental-relationship.README.md
parenting
parenting.README.md
3. Resources// PARA notes' Resource category
README.md// Resource usage instructions
Template.md// Resource template file, used when creating a project
knowledge-management// Resource example
knowledge-management.README.md
photography
photography.README.md
4. Archives// PARA notes' Archive category
README.md// Archive usage instructions
Template.md// Archive template file, used when creating a project
parenting-take-a-name// Archive example
program
README.md
index.js
nameCandidateList.md
package.json
Five Elements
Earth.md
Wood.md
Water.md
Fire.md
Metal.md
Single Characters.md
Rules.md
Lin Yiru.png
parenting-take-a-name.README.md
Candidates List.md
Programmed Naming.md
Five Elements and Meaning Lookup.md
5. Express// Used to practice the CODE model's Express step
README.md// Express index file
README.md
Home.canvas
Tasks.md

Setting Up a Repository from Scratch

Installing the LifeOS Plugin

Choose one of the following

Basic

Click here to open Obsidian and install the LifeOS plugin

If you purchased LifeOS Pro, follow this section. You do not need to buy or install DeepAsk. DeepAsk is an optional AI plugin with a separate license and activation code.

Back up your existing vault first. On a computer, download the stable LifeOS Pro plugin from Feishu, or use the download link in your purchase email. Extract it and copy the lifeos-pro folder containing main.js, manifest.json, and styles.css into the current vault's .obsidian/plugins/ directory. Create the folders if needed.

Alternatively, use these website backup downloads. Choose “Save Link As…” and keep the exact filenames without adding .txt:

The installed files must be directly inside:

Your vault/.obsidian/plugins/lifeos-pro/
├── main.js
├── manifest.json
└── styles.css

Do not add an extra Plugin or lifeos-pro folder level, or replace your entire vault with the download. Keep personal configuration files such as data.json when updating an existing installation.

Hidden folder

.obsidian is hidden by default. In macOS Finder, press Command + Shift + .; in Windows File Explorer, choose “View → Show → Hidden items.” If you use a custom Obsidian configuration directory, use that directory for the current vault instead.

Enable and activate LifeOS Pro
  1. Reload or restart Obsidian and open “Settings → Community plugins.” Allow community plugins if Restricted mode is still on, then enable LifeOS Pro. Disable the community LifeOS plugin first if it is running, to avoid duplicate functionality.
  2. Select LifeOS Pro in Settings and open “Activation & Upgrade.” Enter your purchase email in “Account” and paste the complete LifeOS Pro activation code from the email into “Activation Code,” without explanatory text or extra spaces.
  3. Wait for settings to save and verification to finish automatically. You do not need to select “Upgrade Now” to activate. Checking for or downloading updates is a separate operation. Keep your network connection available during verification.
  4. Confirm that the page shows “Already activated!”, then open the LifeOS Pro Home or Calendar view and check that it works without an activation error. A version number, enabled switch, or ribbon icon alone does not prove activation succeeded.

This workflow was checked against the stable 3.1.7 release artifact. If an older package has a different interface, follow the update guide to install the stable version. Do not purchase again to find a button shown in an old guide.

Activation troubleshooting
SymptomCheck first
LifeOS Pro is missing from Community pluginsConfirm the current vault, the three files directly inside .obsidian/plugins/lifeos-pro/, and restart after copying
Email or code mismatchUse the purchase email and complete LifeOS Pro code, not a DeepAsk, Aino, or Calendar Pro code
No activated state after entering detailsWait and reopen Settings; if needed, restart once and check Home or Calendar for the specific error
Network or time errorCheck connectivity and the system date and time, then reopen the plugin
File integrity errorDownload all three files from the same stable source; do not mix versions or edit main.js
Device limit or unresolved activation errorKeep the error message and contact the author for help checking the license and devices

If the activation email is missing, check the purchase mailbox and spam folder. If you still need help, contact the author privately with the purchase channel, order number, purchase email, plugin version, and error message. Hide the activation code in screenshots; never post it in public groups or comments. You do not need to purchase again.

Installing Third-Party Plugins

The Dataview, Templater, and template setup below applies to the older manual structure shown above. It is not a prerequisite for activating LifeOS Pro. Follow the dependencies of your chosen vault or template.

Refer to the image below, enable "Trigger Templater on new file creation" in Templater

Configuring Periodic Notes

Refer to the image below, configure your periodic notes directory and the titles for each module

Refer to the image below, configure your template files for periodic notes. Each time you create a periodic note, it will use the corresponding template to create a new note

Configuring Theme Notes

Refer to the image below, configure your theme notes directory and the titles for each module

Refer to the image below, configure your template files for theme notes. Each time you create a theme note, it will use the corresponding template to create a new note

Using a Ready-Made Example Repository

Refer to: "Scenario 2"