vault backup: 2026-02-25 16:53:37

This commit is contained in:
windyboy
2026-02-25 16:53:37 +08:00
parent 40330ac90d
commit 1e3905d304
266 changed files with 699 additions and 103 deletions
@@ -0,0 +1,4 @@
List:
- New application features and menu
- Focus mode for the current line
- Focus UI for writing
@@ -0,0 +1,365 @@
/* Special Font */
body, p {
font-family: "Dank Mono",'Inter', -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Microsoft YaHei Light", sans-serif;
}
.cm-s-obsidian {
font-family: "Dank Mono",'Inter', -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Microsoft YaHei Light", sans-serif;
font-size: 16px;
}
.editor {
font-family: "Dank Mono",'Inter', -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Microsoft YaHei Light", sans-serif;
font-size: 16px;
}
.markdown-preview-view code {
font-family: "Dank Mono",'Inter', -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Microsoft YaHei Light", sans-serif;
font-size: 16px;
}
.preview {
font-family: "Dank Mono",'Inter', -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Microsoft YaHei Light", sans-serif;
font-size: 16px;
}
/* Scrollbar */
::-webkit-scrollbar {
background-color: transparent;
}
/**/
/* Editor Section */
/**/
/* Line size */
.cm-s-obsidian pre.HyperMD-header {
line-height: 1!important;
}
/* Selection */
.theme-light {
--text-selection: rgba(112, 93, 207, 0.5);
}
.theme-dark {
--text-selection: rgba(112, 93, 207, 0.5);
}
::selection {
background-color: #705dcf;
color: white;
}
/* Title */
/* Current main pane */
.view-header-title {
color: #705dcf;
text-align: center;
}
.workspace-leaf.mod-active .view-header {
text-align: center;
}
/* Other pane */
.workspace-leaf-header-title-container {
text-align: center;
}
/* Headers */
span.cm-formatting.cm-formatting-header.cm-formatting-header-1.cm-header.cm-header-1 {
color: #705dcf;
}
span.cm-formatting.cm-formatting-header.cm-formatting-header-2.cm-header.cm-header-2 {
color: #705dcf;
}
span.cm-formatting.cm-formatting-header.cm-formatting-header-3.cm-header.cm-header-3 {
color: #705dcf;
}
span.cm-formatting.cm-formatting-header.cm-formatting-header-4.cm-header.cm-header-4 {
color: #705dcf;
}
span.cm-formatting.cm-formatting-header.cm-formatting-header-5.cm-header.cm-header-5 {
color: #705dcf;
}
span.cm-formatting.cm-formatting-header.cm-formatting-header-6.cm-header.cm-header-6 {
color: #705dcf;
}
/* Header folder icon */
.CodeMirror-foldgutter-open, .CodeMirror-foldgutter-folded {
color: #3e3471;
}
.CodeMirror-foldgutter-open, .CodeMirror-foldgutter-folded {
color: #705dcf;
}
/* Cursor */
.cm-fat-cursor .CodeMirror-cursor {
background: #3e3471;
}
.cm-animate-fat-cursor {
background-color: #3e3471;
}
/* Selection in popup ([[]] autocomplete)*/
.suggestion-item.is-selected {
background-color: #3e3471;
color: white;
}
.theme-light .suggestion-shortcut {
color: var(--text-normal);
}
/* Inner and Outer links */
.cm-url {
color: lightblue!important;
}
.markdown-highlighting .internal-link .cl-underlined-text {
color: var(--text-accent)!important;
}
.markdown-highlighting .link .cl-underlined-text {
color: lightblue!important;
}
/* Blockquote */
.preview blockquote {
background-color: var(--background-modifier-border);
border: 1px solid var(--text-muted);
}
/* Highlights and Bold */
strong {
font-size: larger;
color: var(--text-normal);
}
mark {
background-color: darkgoldenrod;
}
.markdown-highlighting .tag {
color: var(--text-accent)!important;
}
/* Tables */
.markdown-preview-view th {
background-color: #3e3471;
color: white
}
.cm-s-obsidian pre.HyperMD-table-row span.cm-hmd-table-sep {
color: unset;
}
.cm-s-obsidian pre.HyperMD-table-row-1 > span {
color: unset;
}
/* Status bar */
.theme-dark .status-bar-item {
color: white;
}
.theme-light .status-bar-item {
color: black;
}
/**/
/* Preview section */
/**/
/* Centered preview */
.markdown-preview-view
{
padding-left: 10% !important;
padding-right: 10% !important;
}
.markdown-embed-title {
color: #705dcf;
}
.markdown-preview-view .markdown-embed {
background-color: var(--background-primary-alt);
margin-top: 0.5rem;
margin-bottom: 0.5rem;
}
.markdown-preview-view .internal-link {
color: #705dcf;
}
.markdown-preview-view a {
color: lightblue;
}
/**/
/* Side panel section */
/**/
/* Plugin Title and Description */
.plugin-name {
color: var(--text-normal);
}
.plugin-description {
color: var(--text-normal)
}
/* Files title and Buttons */
.nav-file-title-content, .nav-folder-title-content {
color: var(--text-normal);
}
.nav-action-button {
color: var(--text-normal);
}
/* File explorer navigation selection */
.nav-file.is-active > .nav-file-title, .nav-file.is-active > .nav-folder-title, .nav-file.is-active > .nav-folder-collapse-indicator, .nav-folder.is-active > .nav-file-title, .nav-folder.is-active > .nav-folder-title, .nav-folder.is-active > .nav-folder-collapse-indicator {
background-color: #3e3471;
color: white;
}
body:not(.is-grabbing) .nav-file-title:hover, body:not(.is-grabbing) .nav-folder-title:hover {
background-color: #3e3471;
color: white;
}
.nav-file-title-content, .nav-folder-title-content {
color:unset;
}
.nav-folder.mod-root > .nav-file-title:hover, .nav-folder.mod-root > .nav-folder-title:hover {
color: var(--text-normal);
}
body:not(.is-grabbing) .nav-file-title:hover .nav-folder-collapse-indicator, body:not(.is-grabbing) .nav-folder-title:hover .nav-folder-collapse-indicator {
background-color: #3e3471;
color: white;
}
.nav-file-title, .nav-folder-title, .nav-folder-collapse-indicator {
color: var(--text-normal);
}
/* File explorer menu*/
.menu-item:hover {
background-color: #3e3471;
color: white;
}
/* Backlinks Color and Text */
.search-result-file-matched-text {
background-color: #3e3471;
color: white;
}
.search-result-file-title {
color: #705dcf;
}
.search-result-file-matches {
color: var(--text-normal);
}
.search-result-file-title:hover {
background-color: #3e3471;
color: white;
}
.search-result-file-match:hover {
background-color: #3e3471;
color: white;
}
/* Folder arrow */
.nav-folder.is-collapsed .nav-folder-collapse-indicator {
color: #705dcf;
}
.nav-folder-collapse-indicator {
color: #705dcf;
}
/* Tag Selection */
.tag-pane-tag:hover {
background-color: #3e3471;
color: white;
}
.theme-light .tag-pane-tag-count {
color: var(--text-normal)
}
/* Title */
.side-dock-title {
color: #705dcf;
}
/* Ribon */
.side-dock-ribbon {
background-color: #3e3471!important;
color: var(--text-muted)
}
.side-dock-ribbon-tab, .side-dock-ribbon-action {
color: white;
}
.theme-dark .side-dock-ribbon-tab.is-active {
color: white;
}
.theme-dark .side-dock-ribbon-tab.is-before-active {
color: white;
}
.theme-light .side-dock-ribbon-tab.is-active {
color: var(--text-normal);
}
.theme-light .side-dock-ribbon-tab.is-before-active {
color: white;
}
.side-dock-ribbon-tab-inner {
color: unset;
}
.side-dock-ribbon-before.is-before-active .side-dock-ribbon-tab-inner, .side-dock-ribbon-after.is-after-active .side-dock-ribbon-tab-inner, .side-dock-ribbon-tab.is-before-active .side-dock-ribbon-tab-inner, .side-dock-ribbon-tab.is-after-active .side-dock-ribbon-tab-inner {
background-color: #3e3471;
}
.side-dock-ribbon-tab, .side-dock-ribbon-before, .side-dock-ribbon-after, .side-dock-ribbon-tab-inner {
transition: none;
}
/**/
/* Settings panel Section */
/**/
.vertical-tab-nav-item.is-active {
background-color: #3e3471;
color:white;
}
.horizontal-tab-nav-item:hover, .vertical-tab-nav-item:hover {
background-color: #3e3471;
color: white;
}
.vertical-tab-nav-item.is-active {
background-color: #3e3471;
}
.vertical-tab-nav-item.is-active {
border-left-color: #3e3471;
}
@@ -0,0 +1,41 @@
# The Methodology
The P.A.R.A system is surprisingly simple at first glance but very powerful when applied. At its core, it's just a four folder wide hierarchy with four-layer deeps, starting with those four root folders:
1. Projects
2. Areas
3. Resources
4. Archive
From there, each of the roots is allowed one sub-folder level and then notes. That's how the four levels deep work: App (1) -> `1. Projects` (2) -> P.A.R.A. Demo Vault (3) -> Methodology (4). The reason for this is to keep it manageable and easy to remember and navigate. That restriction was initially because of Evernote limitation, but it turns out to have some serendipity potential. By putting all your notes from similar "zone" and actionability together, you end up with many serendipitous findings of new related notes and ideas.
Just those root folders and their children, the system can contain everything most people needs for their notes and files. This taxonomy works because you don't split things based on categories but actionability and areas of your life. So now, let's define those roots to help see how it works.
## Definition
1. Projects: *Every current project that is actionable with its notes, files, artifacts*
- If you have a project that requires notes or files, it should have a folder in 1. Projects.
- Since this folder is for projects you are working on _right now_, it's the most actionable and probably where you will spend most of your time.
2. Areas: *Zone of responsibility with standard to uphold over long periods*, parent, animals, management, coding, house.
- Areas are **the personal** bucket of your life for important things that don't have an end date. You won't ever "stop" working on your health; for example, it's a constant ongoing thing.
- While areas can (and often do) generate projects, they are not linked since it's already intuitive which areas a project comes from, so there's no need to create an explicit link between, for example, the "Server maintenance" project and the "Sysadmin" area.
- Finally, because they are personal, areas contain information you wrote for _yourself only_ about those areas in your life. Which is opposite to 3. Resources.
3. Resources: *Zone of interest for various topics that don't require standard/responsibility*, game, cooking, productivity, technology.
- Resources are **generally helpful for others**, not just you. For example, if someone was to ask you for information about cooking, you could zip that folder and send it to them.
- The folders in there will very often reflect your various interests, what you're curious about and want to learn more about.
- They are not necessarily actual "resources" as in PDF, Pictures, etc. they can also be notes about those subjects
4. Archives: *Where stuff from all the other category become unused*, finished project, change of responsibility, etc.
- This folder will be where you put things you won't need for a while, as the name suggests. For the most part, something in there won't be seen for a time, and that's why it has the lowest actionability, but sometimes a new project could use things in there, or a change of areas might mean you need to get stuff out of there.
- For example, you have lots of notes on living with a pet in a small apartment, and then you move to a new bigger one. You could move all those to the archive if one day you have to go back to a small apartment again take them out.
## Setup
The setup for it is pretty simple, create root folders for each category, like in this sandbox. From there, move all of your current notes into `4. Archives` as is with the same existing hierarchy (remember it's not deleted 😉). Then create one folder for each of your current projects you're working on in `1. Projects` (remember only one sub-folder to stay four levels deep). For `2. Areas`, if you already know some of them, you can create the folders already, but try not to have too many empty folders. Finally, `3. Resources`, you want to stay empty for now unless you already captured things that could go in it. The idea is that each time you go into `4. Archives` to take one of the "old" notes or files, you then move it to the right spot in the new taxonomy. Doing it this way will highlight the most used notes, and what's left behind can stay in Archive until it's finally used (or not).
Once you have the folder hierarchy done, you want to copy it across all your other systems; that is where P.A.R.A. starts to shine. You want to have the same hierarchy for your local files on your computer, in your notes, in your Dropbox/Google Drive/iCloud, and everywhere else you have to keep information. Doing that will make it very quick and easy to find things you might need for work or something in the same zone across all your apps. For this reason, the more system you integrate the taxonomy into, the easier finding things will be.
### Setup tips:
- If a note (or a file) can go into two different folders, you put it in the folder where you will **_most likely need it next_** since folders are based on actionability, and it will get moved anyway in the flow of things.
- You can also have the "same" folder in 2 different roots. For example, `2. Areas/Health` and `3. Resources/Health` the first one is **_your_** health notes and the other **general** health-related notes.
- Remember, you do **_not_** want to sort all your current notes and files and put them in the new folder, put them all in the Archive as is, and then move them out as you use them.
- You do **_not_** have to do every single folder for your local files and cloud service; create the sub-folders are you need them, **_but_** you need to have one complete setup, most likely in your notes, to act as the primary reference for the others.
# Next stop [[Workflows]]
@@ -0,0 +1,22 @@
## Start here
- General how-this-work
- What to expect
- How to start
## Definition
- Projects: Short-term efforts with a clear outcome
- Areas: Long-term responsibilities to maintain
- Resources: Topics or interests useful in the future
- Archives: Inactive items from other categories
## Methodology
- Actionnability
- Fluidity
- Project based
- Constraint
## Workflow
- Capture: Collect everything in Inbox
- Clarify: Determine if it's a Project, Area, Resource, or Archive
- Organize: Move to appropriate PARA folder
- Review: Regular reviews to maintain system
## Next steps
- Tiago's blog
- Discord
@@ -0,0 +1,25 @@
# How to use this for work
The workflow of P.A.R.A. is based on projects, as they are the most actionable information, but the information also flows in other ways. Most of the flowing and moving in the system will happen when you use the notes or when you are done with a project; that's why starting and finishing projects are crucial moments. As notes can flow to/from each part of the P.A.R.A, it's best to show with examples:
## Example 1 - Project
This example is the "normal" workflow for most things. First, you start with a project, something like writing this starter kit.
You first create the folder for the project once you're ready. Then you go around `2. Areas` and `3. Resources` to find the information possibly useful for the project; in this case, I would look in my `Second Brain` folder and my `Personal Knowledge Management` folder. From there starts the first flow, you take those notes, pictures, etc., and put them in the folder. At this point, you use them to create the product and complete the project.
Once the project is over, the 2nd flow can start; it's time to look at all the notes and artifacts you created and used. For each of them, see if they would still be helpful later if they could be turned into a template or formatted more generically. The idea is to keep those around for use in other projects later, so put them in the correct `2. Areas` folder. The remainder goes into `4. Archives`.
## Example 2 - Areas change
You decided to change your job and launch your own business in a completely different field. That would mean most of the information in your job-related `2. Areas` would not be actionable anymore. So now you can look if some things in that area could still be helpful and move the rest to `4. Archives`.
If a couple of months later something comes up and it forces you to get back into that first field, take the folder out of `4. Archives` and put it back into `2. Areas`, and you're back into business just like before.
## Example 3 - Resource change
Since things in `3. Resources` interest you to learn more about it can be that it changes at some point. A resource folder on `Marketing`, for example, could turn into a freelance job in marketing.
When that happens, you now have a standard to uphold (freelance standard), so you create a new folder in `2. Areas` for "Marketing" and move all the notes you wrote yourself from `3. Resources` into that new one (since `2. Areas` is for things you wrote yourself)
# Next step Explore!
You're officially done with the explanation now; you can proceed to try it for yourself or explore more around. If you have questions, don't hesitate to ask on the forum thread or read the [P.A.R.A. complete article](https://fortelabs.co/blog/para/) for a deeper dive into all the details.
If you want to look at more demo vaults like this, I also have my own system, a fork of P.A.R.A. for my use over [here](https://forum.obsidian.md/t/paan-starter-kit/21782). Finally, for more general writing, I have my blog where I will often write about that system or others at [maximecote.me](https://maximecote.me/)