Add P.A.R.A. methodology documentation and restructure Personal folder

- Created Methodology.md to outline the P.A.R.A. system and its components. - Added Outline.md for a structured overview of P.A.R.A. content. - Documented PKM content organization decisions in PKM-Consolidation-Decision.md. - Introduced Workflows.md to explain practical applications of P.A.R.A. in work scenarios. - Moved sensitive information to security-sensitive folder and restructured the Personal folder to align with P.A.R.A. principles. - Archived backup files including Matrix Me.md and TTG Cookies.md. - Implemented a comprehensive refactor of the Personal folder to improve organization and security.
2025-12-29 15:37:17 +08:00
parent c9d757d973
commit daf4aa3dfa
106 changed files with 268 additions and 37 deletions
@@ -0,0 +1,3 @@
+
+
+变量隐藏 [[Scope and Shadowing - Rust By Example]]
@@ -0,0 +1,38 @@
+
+Hi Amin,
+
+Thanks for posting in the community. We are happy to help you.
+
+According to your description, the situation on your end is likely caused by your organization's settings/policies (e.g. conditional access policy).
+
+You can try the following steps, and then check if it still happens or not.
+
+1. Please sign out your accounts from Office applications, then close all Office applications.
+
+2. Open File Explorer, paste the following path, and delete all files and folders.
+
+%localappdata%\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy
+
+3. In the Windows search bar, search for "Access Work or School".
+
+4. Check if you can see your business account in "Access Work or School".
+
+- If you don't see it, please select Connect and add your business account.
+    
+
+- If you can see it, please select it and select Disconnect. After that, please click "Connect" and log into your account again to register the device.
+    
+
+5. Run one Office application, such as Word, sign into your account, and check again.
+
+If the error message still appears after trying the above steps, I recommend you report the situation to your organization admin or IT department.
+
+We look forward to your response. Thanks for your cooperation.
+
+Sincerely,
+
+George | Microsoft Community Moderator
+
+[Updated by George Jiang MSFT 04:33 AM 08/10 2024 UTC + 8]
+
+• Beware of Scammers posting fake Support Numbers here.
@@ -0,0 +1,5 @@
+亲，以下是您购买的商品信息。
+MobaXterm Professional 便携版
+下载地址https://wwxs.lanzoum.com/ieYNw0s21tab
+备用地址https://www.987123.xyz/oss/lovemei9/MobaXterm/MobaXterm_Portable_v23.1.zip
+说明：复制以上地址进行下载，软件包中已经集成授权文件，下载后解压即用。
@@ -0,0 +1,3 @@
+
+api:
+secret_WggiGblW3PayQXirTeOCrS9FTsQ5EWGWHjInmNcvJdv
@@ -0,0 +1,86 @@
+
+Here is the **definitive, consolidated guide** for setting up Playwright on **Arch Linux (WSL)**.
+
+This summary skips the trial-and-error we just went through and provides the "Happy Path" to get everything working in one go.
+
+---
+
+### 📋 Prerequisites
+*   **WSL 2** (Recommended).
+*   **Proxy (Optional):** If you are behind a proxy, remember to use `sudo -E` to preserve environment variables.
+
+---
+
+### 🚀 Step 1: System Prep & Node.js
+First, ensure your package database is fresh (fixes 404 errors) and install Node.js.
+
+```bash
+# Update system and install Node.js/npm
+# Use -E if you have https_proxy set in your shell
+sudo -E pacman -Syu nodejs npm
+```
+
+### 📦 Step 2: Install System Dependencies (The Critical Step)
+**Do not** use `npx playwright install-deps` (it fails on Arch). Instead, install these packages manually. This list includes all the X11, Graphics, and Network libraries required by Chromium, Firefox, and WebKit.
+
+```bash
+sudo -E pacman -S --needed \
+    git \
+    nss \
+    nspr \
+    libdrm \
+    alsa-lib \
+    mesa \
+    gtk3 \
+    at-spi2-core \
+    pango \
+    cairo \
+    gdk-pixbuf2 \
+    libx11 \
+    libxcomposite \
+    libxdamage \
+    libxext \
+    libxfixes \
+    libxrandr \
+    libxcursor \
+    libxi \
+    libxrender \
+    libxcb \
+    freetype2 \
+    fontconfig \
+    ffmpeg
+```
+
+### 🛠️ Step 3: Initialize Playwright
+Set up your project and download the browser binaries (these are separate from the system libs above).
+
+```bash
+# Create project directory
+mkdir my-tests && cd my-tests
+
+# Initialize (Select TypeScript/JavaScript as preferred)
+npm init playwright@latest
+
+# If prompted to "Install Playwright browsers", select True.
+# If you need to install them manually later:
+npx playwright install
+```
+
+### ✅ Step 4: Run Tests
+You are now ready to run.
+
+```bash
+npx playwright test
+```
+
+---
+
+### 💡 Troubleshooting Cheat Sheet
+
+| Issue                     | Solution                                                                          |
+| :------------------------ | :-------------------------------------------------------------------------------- |
+| **`install-deps` fails**  | **Ignore it.** It only supports Ubuntu. Use the `pacman` command in Step 2.       |
+| **`libxxx.so not found`** | You are missing a package. Use `pkgfile libxxx.so` to find the Arch package name. |
+| **404 Errors (Pacman)**   | Your mirrors are out of sync. Run `sudo pacman -Syu` to refresh.                  |
+| **Browser won't launch**  | Ensure `nspr` and `nss` are installed (included in Step 2).                       |
+| **GUI/Headless issues**   | If visual mode fails, try `xvfb-run npx playwright test`.                         |
@@ -0,0 +1,173 @@
+
+To set up **Oh My Posh** with **Zsh** on **Debian 12**, follow these steps to install the necessary components and configure your terminal prompt.
+
+## Installation Steps
+
+### 1. Download the Oh My Posh Binary
+First, you need to download the Oh My Posh binary suitable for Linux. Open your terminal and run the following command:
+
+```bash
+sudo wget https://github.com/JanDeDobbeleer/oh-my-posh/releases/latest/download/posh-linux-amd64 -O /usr/local/bin/oh-my-posh
+```
+
+### 2. Set Executable Permissions
+Make the downloaded binary executable:
+
+```bash
+sudo chmod +x /usr/local/bin/oh-my-posh
+```
+
+### 3. Create a Directory for Themes
+You need a directory to store your themes. Create it using:
+
+```bash
+mkdir -p ~/.poshthemes
+```
+
+### 4. Download Themes
+You can download predefined themes from the Oh My Posh repository. For example, to download the latest themes, run:
+
+```bash
+wget https://github.com/JanDeDobbeleer/oh-my-posh/releases/latest/download/themes.zip -O ~/.poshthemes/themes.zip
+```
+
+Unzip the downloaded file:
+
+```bash
+unzip ~/.poshthemes/themes.zip -d ~/.poshthemes
+```
+
+Then, clean up by removing the zip file:
+
+```bash
+rm ~/.poshthemes/themes.zip
+```
+
+### 5. Update Your Zsh Configuration
+Now, you need to configure your Zsh shell to use Oh My Posh. Open your `.zshrc` file in a text editor:
+
+```bash
+nano ~/.zshrc
+```
+
+Add the following line at the end of the file to initialize Oh My Posh with a specific theme (replace `alien` with your preferred theme name):
+
+```bash
+eval "$(oh-my-posh --init --shell zsh --config ~/.poshthemes/alien.omp.json)"
+```
+
+### 6. Apply Changes
+After saving and closing the `.zshrc` file, apply the changes by running:
+
+```bash
+source ~/.zshrc
+```
+
+## Additional Configuration
+
+### Install a Nerd Font (Optional)
+For better aesthetics, install a Nerd Font that supports icons used by Oh My Posh. You can download fonts like **Meslo** or **Fira Code** from their respective repositories and install them on your system.
+
+### Set Terminal Font
+Finally, ensure that your terminal emulator is configured to use the newly installed Nerd Font for optimal display of icons and symbols.
+
+By following these steps, you will have successfully set up Oh My Posh with Zsh on Debian 12, enhancing your terminal's appearance and functionality.
+
+Citations:
+[1] https://dev.to/karleeov/wsl-arch-setup-for-oh-my-posh-51pa
+[2] https://www.reddit.com/r/NixOS/comments/1ge1gwn/how_to_set_ohmyposh_settings/
+[3] https://ohmyposh.dev/docs/installation/linux
+[4] https://www.librebyte.net/en/cli-en/oh-my-posh-a-beatifull-prompt-for-your-shell/
+[5] https://www.youtube.com/watch?v=nGHgyPLi7UM
+[6] https://calebschoepp.com/blog/2021/how-to-setup-oh-my-posh-on-ubuntu/
+[7] https://www.linux.org/threads/need-help-finalizing-oh-my-posh-bash-terminal.52617/
+
+
+
+.zshrc
+```
+#go lang
+export GOROOT=/usr/local/go
+export GOPATH=/home/windy/go-lang
+export PATH=$PATH:$GOROOT/bin:$GOPATH/bin
+
+eval "$(oh-my-posh --init --shell zsh --config ~/.poshthemes/powerlevel10k_modern.omp.json)"
+
+
+[ -f ~/.fzf.zsh ] && source ~/.fzf.zsh
+
+
+# Zinit setup and plugin management
+ZINIT_HOME="${XDG_DATA_HOME:-${HOME}/.local/share}/zinit/zinit.git"
+[ ! -d $ZINIT_HOME ] && mkdir -p "$(dirname $ZINIT_HOME)"
+[ ! -d $ZINIT_HOME/.git ] && git clone https://github.com/zdharma-continuum/zinit.git "$ZINIT_HOME"
+source "${ZINIT_HOME}/zinit.zsh"
+
+# Load essential annexes (non-turbo mode for annex functionality)
+zinit light-mode for \
+    zdharma-continuum/zinit-annex-as-monitor \
+    zdharma-continuum/zinit-annex-bin-gem-node \
+    zdharma-continuum/zinit-annex-patch-dl \
+    zdharma-continuum/zinit-annex-rust
+
+# Load Zeno plugin with keybindings
+zinit ice lucid depth"1" blockf
+zinit light yuki-yano/zeno.zsh
+
+if [[ -n $ZENO_LOADED ]]; then
+  bindkey ' '  zeno-auto-snippet
+  bindkey '^m' accept-line
+  bindkey '^i' zeno-completion
+  bindkey '^g' zeno-ghq-cd
+  bindkey '^r' zeno-history-selection
+  bindkey '^x' zeno-insert-snippet
+fi
+
+# Load additional Zsh plugins
+zinit ice wait"0"; zinit light zsh-users/zsh-completions
+autoload -Uz compinit && compinit
+zstyle ':completion:*' matcher-list 'm:{a-z}={A-Z}'
+zstyle ':completion:*:default' menu select=1
+
+zinit light zsh-users/zsh-syntax-highlighting
+zinit light zsh-users/zsh-autosuggestions
+zinit light Aloxaf/fzf-tab
+
+# FZF configuration
+zi ice from"gh-r" as"program"
+zi light junegunn/fzf
+
+# Auto-suggestions styling
+ZSH_AUTOSUGGEST_HIGHLIGHT_STYLE="fg=244"
+
+# History settings
+HISTFILE=~/.zsh-history
+HISTSIZE=100000
+SAVEHIST=1000000
+HISTDUP=erase
+setopt appendhistory sharehistory hist_ignore_space hist_ignore_all_dups
+setopt hist_save_no_dups hist_ignore_dups hist_find_no_dups
+setopt inc_append_history share_history
+
+# Zsh options for usability
+setopt AUTO_CD
+setopt AUTO_PARAM_KEYS
+
+# Completion and FZF styling
+zstyle ':completion:*' matcher-list 'm:{a-z}={A-Za-z}'
+zstyle ':completion:*' list-colors "${(s.:.)LS_COLORS}"
+zstyle ':completion:*' menu no
+zstyle ':fzf-tab:complete:cd:*' fzf-preview 'ls --color $realpath'
+
+# Load additional plugins with default keys
+zinit pack"default+keys" for fzf
+
+# Ensure Zinit autocompletion
+autoload -Uz _zinit
+(( ${+_comps} )) && _comps[zinit]=_zinit
+
+# Consolidate PATH with deduplication
+export PATH=$(echo "/run/current-system/sw/bin:/usr/local/bin:/usr/local/sbin:$PATH" | tr ':' '\n' | awk '!seen[$0]++' | tr '\n' ':' | sed 's/:$//')
+
+
+```
@@ -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,16 @@
+## Start here
+- General how-this-work
+- What to expect
+- How to start
+## Definition 
+- ![[PARA Notes#Definitions]]
+## Methodology
+- Actionnability
+- Fluidity
+- Project based
+- Constraint
+## Workflow
+- ![[PARA Notes#Workflow]]
+## Next steps
+- Tiago's blog
+- Discord
@@ -0,0 +1,39 @@
+# PKM Content Organization - Decision Note
+
+## Analysis (2025-12-29)
+
+After reviewing both locations containing PARA methodology content:
+- **[300-resources/Personal Knowledge Management](300-resources/Personal Knowledge Management)** - 8 files (course notes, references, essays)
+- **[100-project/Personal/PKM/PARA](100-project/Personal/PKM/PARA)** - 3 files (implementation guide)
+
+## Decision: Keep Current Structure
+
+**Rationale:**
+1. **Different purposes, complementary content:**
+   - `300-resources/PKM/` contains **source material** from BASB courses, external essays, and learning references
+   - `100-project/PKM/PARA/` contains **implementation documentation** specific to this vault's setup
+
+2. **PARA principle alignment:**
+   - Resources = generally useful reference material (course notes, methodology explanations)
+   - Projects = active work on implementing/customizing the system
+
+3. **Content breakdown:**
+   - **300-resources/PKM/** (Reference material):
+     - BASB Class 7 & 8 notes (course content)
+     - PARA Notes.md & PARA Notes from class.md (methodology reference)
+     - Gregory Gundersen essay (writing philosophy)
+     - Dickens deep work (anecdote)
+     - Images.md (visual references)
+   
+   - **100-project/PKM/PARA/** (Implementation):
+     - Methodology.md (how to apply in Obsidian)
+     - Workflows.md (practical examples for this vault)
+     - Outline.md (project plan)
+
+## Cleanup Actions Taken
+
+✅ Moved arc42 from `300-resources/PKM/` to `300-resources/Development/Architecture/` (was misplaced)
+
+## Recommendation
+
+No merge needed. The two locations serve distinct purposes and should remain separate. If PKM project becomes inactive, move implementation docs to `200-area/Personal Development/` (ongoing learning responsibility) and keep course references in `300-resources/`.
@@ -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/)
				`@@ -0,0 +1,3 @@`


				`变量隐藏 [[Scope and Shadowing - Rust By Example]]`