Pro-Con Decisions

Weigh the pros and cons of a decision right inside your notes. You write a plain Markdown table of arguments with weights. Obsidian shows it as editable cards and a bar that shows which side wins.

Source code: github.com/haderlka/obsidian-procon-decisions. Issues and ideas are welcome.

Features

• Plain Markdown underneath. Your data is an ordinary Markdown table inside a code block. It stays readable in any editor, even without the plugin.
• Edit in the rendered view. Add, rename, re-weight, move and delete arguments without touching the table syntax. This works in Live Preview and in Reading view.
• Weights as symbols. Click (or tap) a star to set how much an argument counts. You can choose stars, hearts, dots, diamonds, flames or bolts.
• Result bar. A green/red bar shows how the total weight splits between pro and con.
• Two designs. Colored, with color and subtle animations, or Plain, which is quiet, low-color and has no animation.
• Works on phones and tablets. Touch-sized controls, and a layout that stacks on narrow screens.

Screenshots

Colored design, dark theme	Plain design, dots as weight symbol

On a phone: columns stack and the controls are always visible

Usage

Run Insert pro/con decision from the command palette, or type a procon code block yourself:

```procon
| Side | Argument                  | Weight |
| ---- | ------------------------- | ------ |
| pro  | Much better job market    | 5      |
| pro  | Friends already live there | 3     |
| con  | Rent is getting expensive | 4      |
| con  | Far away from family      | 3      |
```

You can put a decision anywhere in a note, between normal text, and have as many as you like.

Syntax

• The header row and separator row are optional. Rows with an unknown side are ignored.
• An optional first line such as # My question is kept in the file but not displayed.

Editing in the rendered view

On desktop the buttons appear when you hover over a card. On touch devices they're always visible.

Every edit rewrites the table inside your note, so the Markdown always matches what you see. Undo (Ctrl/Cmd+Z in the editor) works as usual.

Settings

Installation

From Obsidian (recommended)

Once the plugin is listed in the community plugin directory:

1. Open Settings → Community plugins. If needed, click Turn on community plugins.
2. Click Browse and search for Pro-Con Decisions.
3. Click Install, then Enable.

Manual installation by downloading

Use this before the plugin is listed, or to install a specific version.

1. Open the latest release of this repository.
2. Under Assets, download these three files:
   • main.js
   • manifest.json
   • styles.css
3. In your vault, open the hidden folder .obsidian/plugins/. Create a folder named procon-decisions inside it. The folder name must match the plugin id.
   • Windows: in File Explorer, turn on View → Show → Hidden items.
   • macOS: in Finder, press Cmd+Shift+. to show hidden files.
4. Put the three files into that folder:

   <your vault>/.obsidian/plugins/procon-decisions/
   ├── main.js
   ├── manifest.json
   └── styles.css
   

5. In Obsidian, open Settings → Community plugins. Click the reload icon next to Installed plugins, then enable Pro-Con Decisions.

Updating a manual install: download the three files from the newer release, replace the old ones, then turn the plugin off and on again (or restart Obsidian).

Phones and tablets: Obsidian mobile can't easily reach the hidden .obsidian folder. The simplest way is to install on desktop and let your sync carry the plugin over. With Obsidian Sync, turn on Installed community plugins and Active community plugin list under Settings → Sync. iCloud, Syncthing and similar tools sync the folder automatically. Then enable the plugin on the phone.

Compatibility

• Obsidian 1.4.0 or newer.
• Desktop (Windows, macOS, Linux) and mobile (iOS, Android).

Privacy

This plugin makes no network requests and collects no data. It only reads and writes the procon code blocks in the notes you edit.

Development

npm ci            # install dependencies
npm run dev       # rebuild main.js on every change
npm run build     # type-check and create a production build
npm run lint      # Obsidian's official review rules (eslint-plugin-obsidianmd)
npm test          # unit tests for the parser/serializer (Node ≥ 22.18)
npm run screenshots  # regenerate the README images in docs/ (needs Chrome or Edge)

To try changes, link or copy the project folder into <vault>/.obsidian/plugins/procon-decisions/. Reload the plugin after each build.

Releasing

1. Run npm version patch (or minor / major). This updates package.json, manifest.json and versions.json, and creates a git tag.
2. Run git push --follow-tags.
3. The Release GitHub Action builds the plugin and creates a draft release with the three files. Review the draft on GitHub and publish it.

Tags have no v prefix: 1.0.1, not v1.0.1.

Support

If this plugin helps you make better decisions, you can support its development:

License

MIT