Releases: PtiCalin/temp_repo-obsidian-plugin
Plugin Template Refactor: Obsidian Standard
🧱 v0.2.0 — Plugin Template Refactor: Obsidian Standard
🛠️ Plugin structure realigned with the Obsidian Sample Plugin spec
Ready for building, bundling, and community publishing
✅ What's New?
This release restructures the repository to match the official Obsidian plugin architecture, improving maintainability, compatibility, and contributor experience.
📦 Structural Updates
- ✅ Adopted
src/ → dist/build pipeline withmain.tsas entry point - ✅ Added
manifest.jsonandversions.jsonusing community plugin schema - ✅ Added required
tsconfig.json,rollup.config.js, andpackage.jsonfiles - ✅ Cleaned up plugin root for clarity and future automation support
🚀 Why It Matters
- 📦 Easier to build and publish via GitHub Actions
- 🧩 Ready to be submitted to the Obsidian Community Plugins Directory
- 🛠️ Developer-friendly setup with predictable file structure and plugin metadata
- 💬 Better onboarding for contributors and collaborators
🧪 Next Steps
- Add a README explaining how to build, test, and publish your plugin
- Customize plugin metadata (name, ID, description, author)
- Begin development on your plugin logic inside
src/main.ts
This repo is now a clean foundation for Obsidian plugin development 💜
🙌 Acknowledgements
Thanks to the Obsidian dev community for maintaining excellent tooling and sample codebases.
Let’s build something magical ✨
Template Update: Plugin-Specific Forms
🔧 v0.1.1 — Template Update: Plugin-Specific Forms
✍️ A small but mighty update to improve how contributors interact with this repo.
✨ What’s Changed?
- 🔄 Refined PR & Issue Templates
The contribution workflow has been updated to reflect this repo’s plugin-specific nature, instead of the broader VaultOS structure.
🔍 Changes include:
- Updated issue form titles and prompts to refer directly to “plugin” instead of “vault”
- Clarified bug report and feature request guidance for single-purpose plugin contexts
- Improved readability and flow for contributors submitting PRs
🚀 Why it Matters
Better templates = better contributions.
By tailoring the wording and structure to fit plugin development, we ensure clarity for devs, collaborators, and curious users alike.
📬 Got Suggestions?
Open an issue using the new forms and let’s make these templates even more awesome!
🧩 Modular tools, clean workflows — one plugin at a time.
v1.0.0 – VaultOS Obsidian Plugin Template
✨ v1.0.0 – VaultOS Obsidian Plugin Template
🛠 A modular launchpad for crafting Obsidian plugins with VaultOS structure, clarity, and care.
🌟 Features
| Feature | Description |
|---|---|
| 📦 Plugin Manifest | Preloaded manifest.json with VaultOS naming conventions |
| ⚙️ Build System | TypeScript + Rollup configured out of the box |
| 📁 Folder Layout | Modular folder structure (src/, ops/, config/, dist/) |
| 🧪 GitHub Actions | CI-ready workflows and custom issue/PR templates |
| 💬 Discussions Enabled | Built-in support for GitHub Discussions |
| 💖 Friendly Docs | Styled README, CONTRIBUTING, LICENSE, and CODE_OF_CONDUCT |
📂 Included Files
📂 .github/
├── workflows/
├── ISSUE_TEMPLATE/
└── PULL_REQUEST_TEMPLATE.md
📂 src/ → Plugin logic in TypeScript
📂 dist/ → Compiled output for Obsidian
📂 config/ → Metadata and VaultOS module config
📂 ops/ → Logic orchestrators or transformers (VaultOS-aligned)
📄 manifest.json
📄 README.md
📄 CONTRIBUTING.md
📄 CODE_OF_CONDUCT.md
📄 LICENSE
📄 change-log.md
📄 config.yaml
🚀 How to Use
- Click “Use this template” on the repo page
- Rename your plugin and set up
manifest.json+config.yaml - Run:
npm install npm run build
- Drop the
/distfolder into your Obsidian vault’s.obsidian/plugins/directory - Enable it from the Obsidian plugin settings panel 🪄
🌱 Perfect For…
- VaultOS plugin developers
- Modular tool builders
- Plugin authors who care about structure and clarity
- Anyone who loves Obsidian and wants to build something thoughtful
💬 Feedback & Collaboration
Got ideas?
Open an issue
Or join us in GitHub Discussions to spark some magic ✨
With care and clarity,
PtiCalin