Add plugin: Hexo Publisher

[zhenlohuang]

I am submitting a new Community Plugin

Repo URL

Link to my plugin: https://github.com/zhenlohuang/obsidian-hexo-publisher

Release Checklist

• I have tested the plugin on
  • Windows
  • macOS
  • Linux
  • Android (if applicable)
  • iOS (if applicable)
• My GitHub release contains all required files
  • main.js
  • manifest.json
  • styles.css (optional)
• GitHub release name matches the exact version number specified in my manifest.json (Note: Use the exact version number, don't include a prefix v)
• The id in my manifest.json matches the id in the community-plugins.json file.
• My README.md describes the plugin's purpose and provides clear usage instructions.
• I have read the developer policies at https://docs.obsidian.md/Developer+policies, and have assessed my plugins's adherence to these policies.
• I have read the tips in https://docs.obsidian.md/Plugins/Releasing/Plugin+guidelines and have self-reviewed my plugin to avoid these common pitfalls.
• I have added a license in the LICENSE file.
• My project respects and is compatible with the original license of any code from other plugins that I'm using.
  I have given proper attribution to these other projects in my README.md.

[github-actions]

Hello!

I found the following issues in your plugin submission

Errors:

❌ Please don't use the word obsidian in the plugin ID. The ID is used for your plugin's folder so keeping it short and simple avoids clutter and helps with sorting.
❌ Please don't use the word Obsidian in your plugin name since it's redundant and adds clutter to the plugin list.

---

^{This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it.}

[github-actions]

Hello!

I found the following issues in your plugin submission

Errors:

❌ Plugin ID mismatch, the ID in this PR (hexo-publisher) is not the same as the one in your repo (obsidian-hexo-publisher). If you just changed your plugin ID, remember to change it in the manifest.json in your repo and your latest GitHub release.
❌ Plugin name mismatch, the name in this PR (Hexo Publisher) is not the same as the one in your repo (Obsidian Hexo Publisher). If you just changed your plugin name, remember to change it in the manifest.json in your repo and your latest GitHub release.

---

^{This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it.}

[ObsidianReviewBot]

The automated review has not found any issues with your code, assigning human for additional review.

[joethei]

Remove the styles.css file from your release, since it's empty it's just unnecessary bloat.

"description": "Publish your Obsidian notes to Hexo",
Don't include "Obsidian" in the description.

"fundingUrl": "",
This is meant for links to services like Buy me a coffee, GitHub sponsors and so on, if you don't have such a link remove this line.

name: 'Publish Posts',,

console.log(Found ${publishedPosts.length} published posts);, console.log(Found ${images.length} images in ${mdFile.name});, console.log(Found ${markdownFiles.length} markdown files);

public getFileByPath(name: string): TFile | undefined {
[Avoid iterating all files to find a file by its path]https://docs.obsidian.md/Plugins/Releasing/Plugin+guidelines#Avoid+iterating+all+files+to+find+a+file+by+its+path

import * as path from 'path';
You should be using the vault API instead of the Node fs/path API.

containerEl.createEl('h1', { text: 'Hexo Publilsher - Settings' });
Don't include a header with the plugin name in the settings

containerEl.createEl('h2', { text: 'Hexo Site Settings' });
Only use headings under settings if you have more than one section.

[zhenlohuang]

Thanks for your review. For this comment, I need to access the file outside Obsidian, which API should I use?

[import * as path from 'path';](https://github.com/zhenlohuang/obsidian-hexo-publisher/blob/531a592aa3cccc8358d203b96bd34db419e82646/src/hexo.ts#L1-L73)
You should be using the vault API instead of the Node fs/path API.