Awesome
SiYuan plugin sample
Get started
- Make a copy of this repo as a template with the <kbd>Use this template</kbd> button, please note that the repo name
must be the same as the plugin name, the default branch must be
main
- Clone your repo to a local development folder. For convenience, you can place this folder in
your
{workspace}/data/plugins/
folder - Install NodeJS and pnpm, then run
pnpm i
in the command line under your repo folder - Execute
pnpm run dev
for real-time compilation - Open SiYuan marketplace and enable plugin in downloaded tab
Development
- i18n/*
- icon.png (160*160)
- index.css
- index.js
- plugin.json
- preview.png (1024*768)
- README*.md
- Fontend API
- Backend API
I18n
In terms of internationalization, our main consideration is to support multiple languages. Specifically, we need to complete the following tasks:
- Meta information about the plugin itself, such as plugin description and readme
description
andreadme
fields in plugin.json, and the corresponding README*.md file
- Text used in the plugin, such as button text and tooltips
- src/i18n/*.json language configuration files
- Use
this.i18.key
to get the text in the code
- Finally, declare the language supported by the plugin in the
i18n
field in plugin.json
It is recommended that the plugin supports at least English and Simplified Chinese, so that more people can use it more conveniently.
plugin.json
{
"name": "plugin-sample",
"author": "Vanessa",
"url": "https://github.com/siyuan-note/plugin-sample",
"version": "0.1.3",
"minAppVersion": "2.8.8",
"backends": ["windows", "linux", "darwin"],
"frontends": ["desktop"],
"displayName": {
"default": "Plugin Sample",
"zh_CN": "插件示例"
},
"description": {
"default": "This is a plugin sample",
"zh_CN": "这是一个插件示例"
},
"readme": {
"default": "README.md",
"zh_CN": "README_zh_CN.md"
},
"funding": {
"openCollective": "",
"patreon": "",
"github": "",
"custom": [
"https://ld246.com/sponsor"
]
},
"keywords": [
"sample", "示例"
]
}
name
: Plugin name, must be the same as the repo name, and must be unique globally (no duplicate plugin names in the marketplace)author
: Plugin author nameurl
: Plugin repo URLversion
: Plugin version number, it is recommended to follow the semver specificationminAppVersion
: Minimum version number of SiYuan required to use this pluginbackends
: Backend environment required by the plugin, optional values arewindows
,linux
,darwin
,docker
,android
,ios
andall
windows
: Windows desktoplinux
: Linux desktopdarwin
: macOS desktopdocker
: Dockerandroid
: Android APPios
: iOS APPall
: All environments
frontends
: Frontend environment required by the plugin, optional values aredesktop
,desktop-window
,mobile
,browser-desktop
,browser-mobile
andall
desktop
: Desktopdesktop-window
: Desktop window converted from tabmobile
: Mobile APPbrowser-desktop
: Desktop browserbrowser-mobile
: Mobile browserall
: All environments
displayName
: Template display name, mainly used for display in the marketplace list, supports multiple languagesdefault
: Default language, must existzh_CN
,en_US
and other languages: optional, it is recommended to provide at least Chinese and English
description
: Plugin description, mainly used for display in the marketplace list, supports multiple languagesdefault
: Default language, must existzh_CN
,en_US
and other languages: optional, it is recommended to provide at least Chinese and English
readme
: readme file name, mainly used to display in the marketplace details page, supports multiple languagesdefault
: Default language, must existzh_CN
,en_US
and other languages: optional, it is recommended to provide at least Chinese and English
funding
: Plugin sponsorship informationopenCollective
: Open Collective namepatreon
: Patreon namegithub
: GitHub login namecustom
: Custom sponsorship link list
keywords
: Search keyword list, used for marketplace search function
Package
No matter which method is used to compile and package, we finally need to generate a package.zip, which contains at least the following files:
- i18n/*
- icon.png (160*160)
- index.css
- index.js
- plugin.json
- preview.png (1024*768)
- README*.md
List on the marketplace
pnpm run build
to generate package.zip- Create a new GitHub release using your new version number as the "Tag version". See here for an example: https://github.com/siyuan-note/plugin-sample/releases
- Upload the file package.zip as binary attachments
- Publish the release
If it is the first release, please create a pull request to the Community Bazaar repository and modify the plugins.json file in it. This file is the index of all community plugin repositories, the format is:
{
"repos": [
"username/reponame"
]
}
After the PR is merged, the bazaar will automatically update the index and deploy through GitHub Actions. When releasing a new version of the plugin in the future, you only need to follow the above steps to create a new release, and you don't need to PR the community bazaar repo.
Under normal circumstances, the community bazaar repo will automatically update the index and deploy every hour, and you can check the deployment status at https://github.com/siyuan-note/bazaar/actions.
Developer's Guide
Developers need to pay attention to the following specifications.
1. File Reading and Writing Specifications
If plugins or external extensions require direct reading or writing of files under the data
directory, please use the kernel API to achieve this. Do not call fs
or other electron or nodejs APIs directly, as it may result in data loss during synchronization and cause damage to cloud data.
Related APIs can be found at: /api/file/*
(e.g., /api/file/getFile
).
2. Daily Note Attribute Specifications
When creating a daily note in SiYuan, a custom-dailynote-yyyymmdd attribute will be automatically added to the document to distinguish it from regular documents.
For more details, please refer to Github Issue #9807.
Developers should pay attention to the following when developing the functionality to manually create Daily Notes:
- If
/api/filetree/createDailyNote
is called to create a daily note, the attribute will be automatically added to the document, and developers do not need to handle it separately - If a document is created manually by developer's code (e.g., using the
createDocWithMd
API to create a daily note), please manually add this attribute to the document