|
1 |
| -# Obsidian Sample Plugin |
| 1 | +# Obsidian BibTeX Adder |
2 | 2 |
|
3 |
| -This is a sample plugin for Obsidian (https://obsidian.md). |
| 3 | +Add BibTeX entries from DOIs using the [Crossref REST API](https://www.crossref.org/documentation/retrieve-metadata/rest-api/). |
4 | 4 |
|
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 | +## Usage |
7 | 6 |
|
8 |
| -**Note:** The Obsidian API is still in early alpha and is subject to change at any time! |
| 7 | +Ideally, this plugin should be paired with the [Citation](https://github.com/hans/obsidian-citation-plugin) plugin when an external reference manage (e.g., Mendeley, EndNote, Zotero, etc.) is not being used. |
| 8 | +This plugin essentially acts as a reference importer by providing an simple way to add BibTeX entries from DOIs. |
9 | 9 |
|
10 |
| -This sample plugin demonstrates some of the basic functionality the plugin API can do. |
11 |
| -- Changes the default font color to red using `styles.css`. |
12 |
| -- Adds a ribbon icon, which shows a Notice when clicked. |
13 |
| -- Adds a command "Open Sample Modal" which opens a Modal. |
14 |
| -- Adds a plugin setting tab to the settings page. |
15 |
| -- Registers a global click event and output 'click' to the console. |
16 |
| -- Registers a global interval which logs 'setInterval' to the console. |
| 10 | +- Adds a command, ``"Add BibTeX entry from DOI"``, that prompts the user for a DOI and proceeds to lookup and add the BibTeX entry. |
17 | 11 |
|
18 |
| -## First time developing plugins? |
| 12 | +## Installation |
19 | 13 |
|
20 |
| -Quick starting guide for new plugin devs: |
| 14 | +- Clone this repo (``git clone github.com/aalexmmaldonado/obsidian-bibtex-adder``). |
| 15 | +- `npm i` or `yarn` to install dependencies. |
| 16 | +- `npm run dev` to compile. |
| 17 | +- Copy `main.js` and `manifest.json` into your vault in `.obsidian/plugins/obsidian-bibtex-adder`. |
21 | 18 |
|
22 |
| -- 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. |
23 |
| -- Make a copy of this repo as a template with the "Use this template" button (login to GitHub if you don't see it). |
24 |
| -- Clone your repo to a local development folder. For convenience, you can place this folder in your `.obsidian/plugins/your-plugin-name` folder. |
25 |
| -- Install NodeJS, then run `npm i` in the command line under your repo folder. |
26 |
| -- Run `npm run dev` to compile your plugin from `main.ts` to `main.js`. |
27 |
| -- Make changes to `main.ts` (or create new `.ts` files). Those changes should be automatically compiled into `main.js`. |
28 |
| -- Reload Obsidian to load the new version of your plugin. |
29 |
| -- Enable plugin in settings window. |
30 |
| -- For updates to the Obsidian API run `npm update` in the command line under your repo folder. |
| 19 | +## License |
31 | 20 |
|
32 |
| -## Releasing new releases |
33 |
| - |
34 |
| -- Update your `manifest.json` with your new version number, such as `1.0.1`, and the minimum Obsidian version required for your latest release. |
35 |
| -- 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. |
36 |
| -- 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 |
37 |
| -- 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. |
38 |
| -- Publish the release. |
39 |
| - |
40 |
| -> 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`. |
41 |
| -> The command will bump version in `manifest.json` and `package.json`, and add the entry for the new version to `versions.json` |
42 |
| -
|
43 |
| -## Adding your plugin to the community plugin list |
44 |
| - |
45 |
| -- Check https://github.com/obsidianmd/obsidian-releases/blob/master/plugin-review.md |
46 |
| -- Publish an initial version. |
47 |
| -- Make sure you have a `README.md` file in the root of your repo. |
48 |
| -- Make a pull request at https://github.com/obsidianmd/obsidian-releases to add your plugin. |
49 |
| - |
50 |
| -## How to use |
51 |
| - |
52 |
| -- Clone this repo. |
53 |
| -- `npm i` or `yarn` to install dependencies |
54 |
| -- `npm run dev` to start compilation in watch mode. |
55 |
| - |
56 |
| -## Manually installing the plugin |
57 |
| - |
58 |
| -- Copy over `main.js`, `styles.css`, `manifest.json` to your vault `VaultFolder/.obsidian/plugins/your-plugin-id/`. |
59 |
| - |
60 |
| -## Improve code quality with eslint (optional) |
61 |
| -- [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. |
62 |
| -- To use eslint with this project, make sure to install eslint from terminal: |
63 |
| - - `npm install -g eslint` |
64 |
| -- To use eslint to analyze this project use this command: |
65 |
| - - `eslint main.ts` |
66 |
| - - eslint will then create a report with suggestions for code improvement by file and line number. |
67 |
| -- 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: |
68 |
| - - `eslint .\src\` |
69 |
| - |
70 |
| - |
71 |
| -## API Documentation |
72 |
| - |
73 |
| -See https://github.com/obsidianmd/obsidian-api |
| 21 | +Distributed under the MIT License. See `LICENSE` for more information. |
0 commit comments