Skip to content
This repository was archived by the owner on Aug 29, 2025. It is now read-only.

Commit e837845

Browse files
authored
Update README.md
1 parent 5e30db1 commit e837845

File tree

1 file changed

+26
-80
lines changed

1 file changed

+26
-80
lines changed

README.md

Lines changed: 26 additions & 80 deletions
Original file line numberDiff line numberDiff line change
@@ -1,94 +1,40 @@
1-
# Obsidian Sample Plugin
1+
# Obsidian Markdown Flip
22

3-
This is a sample plugin for Obsidian (https://obsidian.md).
3+
**Obsidian Markdown Flip** is a plugin that helps you quickly convert markdown block types (like `-`, `>`, `1.`, `#`) by typing them at the start of a line. You can even clear any applied block format using `~`.
44

5-
This project uses TypeScript to provide type checking and documentation.
6-
The repo depends on the latest plugin API (obsidian.d.ts) in TypeScript Definition format, which contains TSDoc comments describing what it does.
5+
![demo](https://github.com/user-attachments/assets/91e5f1f7-b75c-4d4b-b0bc-809f7038cfc1)
76

8-
This sample plugin demonstrates some of the basic functionality the plugin API can do.
9-
- Adds a ribbon icon, which shows a Notice when clicked.
10-
- Adds a command "Open Sample Modal" which opens a Modal.
11-
- Adds a plugin setting tab to the settings page.
12-
- Registers a global click event and output 'click' to the console.
13-
- Registers a global interval which logs 'setInterval' to the console.
7+
---
148

15-
## First time developing plugins?
9+
## ✨ Features
1610

17-
Quick starting guide for new plugin devs:
11+
- Toggle between different Markdown block types by typing at the beginning of a line:
12+
- `-` → Bullet list
13+
- `1.` → Numbered list
14+
- `>` → Blockquote
15+
- `#`, `##`, `###` → Headings (H1 ~ H6)
16+
- Remove existing block markers by typing `~` after a block marker
17+
- Works when you press `Space` after the marker
1818

19-
- Check if [someone already developed a plugin for what you want](https://obsidian.md/plugins)! There might be an existing plugin similar enough that you can partner up with.
20-
- Make a copy of this repo as a template with the "Use this template" button (login to GitHub if you don't see it).
21-
- Clone your repo to a local development folder. For convenience, you can place this folder in your `.obsidian/plugins/your-plugin-name` folder.
22-
- Install NodeJS, then run `npm i` in the command line under your repo folder.
23-
- Run `npm run dev` to compile your plugin from `main.ts` to `main.js`.
24-
- Make changes to `main.ts` (or create new `.ts` files). Those changes should be automatically compiled into `main.js`.
25-
- Reload Obsidian to load the new version of your plugin.
26-
- Enable plugin in settings window.
27-
- For updates to the Obsidian API run `npm update` in the command line under your repo folder.
19+
---
2820

29-
## Releasing new releases
21+
## 📦 Installation
3022

31-
- Update your `manifest.json` with your new version number, such as `1.0.1`, and the minimum Obsidian version required for your latest release.
32-
- Update your `versions.json` file with `"new-plugin-version": "minimum-obsidian-version"` so older versions of Obsidian can download an older version of your plugin that's compatible.
33-
- Create new GitHub release using your new version number as the "Tag version". Use the exact version number, don't include a prefix `v`. See here for an example: https://github.com/obsidianmd/obsidian-sample-plugin/releases
34-
- Upload the files `manifest.json`, `main.js`, `styles.css` as binary attachments. Note: The manifest.json file must be in two places, first the root path of your repository and also in the release.
35-
- Publish the release.
23+
### Via Community Plugins (BRAT)
3624

37-
> You can simplify the version bump process by running `npm version patch`, `npm version minor` or `npm version major` after updating `minAppVersion` manually in `manifest.json`.
38-
> The command will bump version in `manifest.json` and `package.json`, and add the entry for the new version to `versions.json`
25+
You can use [BRAT (Beta Reviewer's Auto-update Tool)](https://github.com/TfTHacker/obsidian42-brat) to install this plugin before it becomes publicly listed:
3926

40-
## Adding your plugin to the community plugin list
27+
1. Install the **BRAT** plugin from Obsidian's Community Plugins.
28+
2. Go to `BRAT` settings → Click **"Add a beta plugin"**.
29+
3. Paste the following GitHub repo URL: https://github.com/JinmuGo/obsidian-markdown-flip
30+
4. Click **Install** and **Enable** the plugin!
4131

42-
- Check the [plugin guidelines](https://docs.obsidian.md/Plugins/Releasing/Plugin+guidelines).
43-
- Publish an initial version.
44-
- Make sure you have a `README.md` file in the root of your repo.
45-
- Make a pull request at https://github.com/obsidianmd/obsidian-releases to add your plugin.
32+
## 🤝 Contributing
4633

47-
## How to use
34+
Contributions, issues and feature requests are welcome!
35+
Feel free to open an issue or submit a pull request 🙌
4836

49-
- Clone this repo.
50-
- Make sure your NodeJS is at least v16 (`node --version`).
51-
- `npm i` or `yarn` to install dependencies.
52-
- `npm run dev` to start compilation in watch mode.
37+
## 💬 Contact
5338

54-
## Manually installing the plugin
55-
56-
- Copy over `main.js`, `styles.css`, `manifest.json` to your vault `VaultFolder/.obsidian/plugins/your-plugin-id/`.
57-
58-
## Improve code quality with eslint (optional)
59-
- [ESLint](https://eslint.org/) is a tool that analyzes your code to quickly find problems. You can run ESLint against your plugin to find common bugs and ways to improve your code.
60-
- To use eslint with this project, make sure to install eslint from terminal:
61-
- `npm install -g eslint`
62-
- To use eslint to analyze this project use this command:
63-
- `eslint main.ts`
64-
- eslint will then create a report with suggestions for code improvement by file and line number.
65-
- If your source code is in a folder, such as `src`, you can use eslint with this command to analyze all files in that folder:
66-
- `eslint .\src\`
67-
68-
## Funding URL
69-
70-
You can include funding URLs where people who use your plugin can financially support it.
71-
72-
The simple way is to set the `fundingUrl` field to your link in your `manifest.json` file:
73-
74-
```json
75-
{
76-
"fundingUrl": "https://buymeacoffee.com"
77-
}
78-
```
79-
80-
If you have multiple URLs, you can also do:
81-
82-
```json
83-
{
84-
"fundingUrl": {
85-
"Buy Me a Coffee": "https://buymeacoffee.com",
86-
"GitHub Sponsor": "https://github.com/sponsors",
87-
"Patreon": "https://www.patreon.com/"
88-
}
89-
}
90-
```
91-
92-
## API Documentation
93-
94-
See https://github.com/obsidianmd/obsidian-api
39+
Maintained by [@JinmuGo](https://github.com/JinmuGo).
40+
If you find this plugin useful, feel free to ⭐️ the repo or share feedback!

0 commit comments

Comments
 (0)