Introduce the plugin Joplin Publisher - Plugins - Joplin Forum
](https://discourse.joplinapp.org/)
Introduce the plugin Joplin Publisher
](https://discourse.joplinapp.org/u/rxliuli “rxliuli”)
](https://discourse.joplinapp.org/u/jamiebear “jamiebear”)
](https://discourse.joplinapp.org/u/hyruo “hyruo”)
](https://discourse.joplinapp.org/u/narF “narF”)
](https://discourse.joplinapp.org/u/navilg “navilg”)
1 / 16
1 Jun
](https://discourse.joplinapp.org/u/rxliuli)
Introduce a recently completed plugin, which publishes some of Joplin’s notes as a web blog. It is based on the previous mark-magic implementation but only requires a Joplin and GitHub account, without the need to use any command line.
Download jpl
Release Joplin Publisher · rxliuli/joplin-utils
Publish Joplin notes to GitHub and automate build deployment through GitHub Actions. Document
Introduction for details.
Introduction
Publish Joplin notes to GitHub and automate build deployment through GitHub Actions.
Usage
GitHub
If you haven’t already, register for a GitHub account.
Use the template project joplin-blog-template as a template to create a new repository named
<github username>.github.io
\
\ 
Modify Settings > Pages > Build and deployment, select GitHub Actions

Create a GitHub token, at least select content and
<github username>.github.iorepository permissions, copy the token after creation
Joplin
Install the plugin
Open Joplin > Settings > Plugins > Publisher, and set GitHub token/username/repo respectively

Select a note and add the blog tag

Click Tools > Publish to GitHub to publish

Wait for two minutes, then you can go to <github username>.github.io to see your published note.
You can continue to add the blog tag to notes you want to publish and rerun Publish to GitHub to update the notes on the website.
14
](https://discourse.joplinapp.org/u/rxliuli “rxliuli”)
](https://discourse.joplinapp.org/u/jamiebear “jamiebear”)
](https://discourse.joplinapp.org/u/hyruo “hyruo”)
](https://discourse.joplinapp.org/u/narF “narF”)
](https://discourse.joplinapp.org/u/navilg “navilg”)
](https://discourse.joplinapp.org/u/navilg)
Do you have document on how to update landing page, theme and other tab links (like About section) ?
](https://discourse.joplinapp.org/u/rxliuli)
Since the rendering is done using Hexo, you can configure it in the forked GitHub repository. The current theme in use is Fluid, and you can also modify the corresponding theme configuration.
For example, to change the title of the site, you can modify the title in _config.yml.
If you want to update the background image of the homepage, you can modify index.banner_img in _config.fluid.yml.
References:
- Hexo Documentation: https://hexo.io/
- Fluid theme documentation: https://hexo.fluid-dev.com/docs/en/guide/
1
This is the first time jamiebear has posted — let’s welcome them to our community!
](https://discourse.joplinapp.org/u/jamiebear)
Thanks for this plugin! I’ve been looking for an easy way to seamlessly integrate my notes into a blog.
I managed to get the site running, following your instructions. However, I can’t figure out how I can edit the theme config file because _config.fluid.yml as shown in your screenshot does not exist anywhere in my repository. I’ve tried manually creating a new _config.fluid.yml and copying over the contents as per theme documentation, but this only results in a blank page and a couple of permission related errors (see my screeshot). Sorry, if I’m missing something obvious, I have no experience with git/github. Any help would be greatly appreciated.

joplin-publisher-error1245×745 27.4 KB
](https://discourse.joplinapp.org/u/rxliuli)
Could you please share your GitHub repository address? I will go check it out.
1
](https://discourse.joplinapp.org/u/jamiebear)
I fear I might’ve screwed with things I didn’t understand properly, so I created a new repo. Still having the same issue though:
https://github.com/jamie-bear/jamie-bear.github.io
Thanks you for your effort!
](https://discourse.joplinapp.org/u/jamiebear)
rxliuli
The problem just resolved itself, actually. I recreated _config.fluid.yml from the source / theme doc and now it seems to work just fine. I must’ve made a mistake when I originally copied & saved the code for _config.fluid.yml and accidentally carried that over to the new repo. So, I guess it was user error (as usual) ![]()
This is the first time hyruo has posted — let’s welcome them to our community!
](https://discourse.joplinapp.org/u/hyruo)
How to custom the fluid theme , I can’t see the _config.fluid.yml file.
](https://discourse.joplinapp.org/u/jamiebear)
As I understand it right now, you need to create _config.fluid.yml manually in the main directory and copy this code as referenced in the theme documentation :
If your Hexo version >= 5.0.0(hexo -v), please create _config.fluid.yml in the blog directory and copy the content of our theme’s_config.yml into it.
This wasn’t specified in the plugin instructions, but it worked for me.
](https://discourse.joplinapp.org/u/hyruo)
Thank you . I will try it later. I’m testing this method compare with the Pages Publisher Plugin.
I’m contemplating if I can switch to a more streamlined Hexo theme, yet not as rudimentary as the default theme offered by Pages Publisher.
Since I am currently using a Hugo blog, I don’t want to make the excerpts from Joplin notes appear as formal as a serious blog.
](https://discourse.joplinapp.org/u/rxliuli)
hyruo:
How to custom the fluid theme , I can’t see the _config.fluid.yml file.
@jamiebear @hyruo Sorry, my mistake, I didn’t copy the default configuration file _config.fluid.yml. But I just fixed it. If you re-fork the repository or merge the upstream updates, this configuration file will appear!
joplin-utils/joplin-blog-template/blob/main/_config.fluid.yml
1 | |
This file has been truncated. show original
1
last visit
](https://discourse.joplinapp.org/u/hyruo)
Well done! This is by far the quickest and most convenient method I’ve seen for publishing a Hexo blog. After trying this method, I immediately used another Hexo theme to set up a notes website. Thank you for your work! Additionally, I referenced your plugin documentation to write a blog post introducing this plugin.

Hexo site created by this plugin1934×1455 344 KB
1
25 days later
](https://discourse.joplinapp.org/u/narF)
Really cool idea!
I don’t really like Github though (owned by Microsoft). Do you think you could support exporting to files so we can self-host them? Or maybe publish using FTP?
1
](https://discourse.joplinapp.org/u/rxliuli)
Certainly, I can support other git-based cloud services such as GitLab if given the opportunity, but it is unlikely that I would be able to support FTP.
1
1 month later
](https://discourse.joplinapp.org/u/rxliuli)
Release 1.1.0, publish to official plugin store.
ref: Release joplin-publisher@v1.1.0 · rxliuli/joplin-utils · GitHub
Official plugin store page: https://joplinapp.org/plugins/plugin/rxliuli.joplin-publisher/

image1920×1525 67.8 KB](https://global.discourse-cdn.com/flex028/uploads/cozic/original/3X/4/1/41aa0f3bcf6a148edfeda5dfb8dbe82764e3e865.jpeg “image”)
1
3 months later
](https://discourse.joplinapp.org/u/rxliuli)
Release 1.1.5, Support hash links in Joplin notes, such as [test 1](https://discourse.joplinapp.org/t/introduce-the-plugin-joplin-publisher/:/test2#hash). ref isssue: https://github.com/mark-magic/mark-magic/issues/8
Tracking
You will see a count of new replies because you read this topic.
Topic list, column headers with buttons are sortable.
| Category | Replies | Views | Activity |
| — | — | — | — | — |
| Plugin: Rich Markdown 3 | Plugins | | 38.5k | 6d |
| Security Privacy exporting from Android 1 | Support | | 69 | 8d |
| Desktop app: Opening/editing multiple notes 1 | Features | | 10.2k | 26d |
| Background sync in android 2 | Features | | 2.4k | 1 Oct |
| The style in userchrome.css stopped working as it should | Support | | 19 | 21h |


