Logseq Template Graph
November 8, 2025 ยท View on GitHub
A comprehensive starter template for Logseq Database that brings Tana-style supertag functionality using Schema.org vocabulary. Import this template to instantly get structured classes and properties for organizing your knowledge.
Quick Links: Quick Start | Developer Guide | ๐ Documentation | Contributing
Table of Contents
- What This Project Does
- Quick Start
- What's Included
- For Template Developers
- Documentation
- Why Use This Template
- Contributing
- Roadmap
- License
๐ฏ What This Project Does
This template provides 47 pre-built classes and 129 properties that you can import into your Logseq DB graph to:
- โ
Tag notes with structured types (
#Person,#Organization,#Event, etc.) - โ Get automatic fields/properties on tagged pages
- โ Use industry-standard Schema.org naming conventions
- โ Build a structured knowledge graph like Tana, but in open-source Logseq
๐ Quick Start
For Users: Import Templates
Prerequisites:
- Logseq Database version installed (installation guide)
3-Step Setup:
-
Download the latest template from Releases
- Choose a variant: Full, CRM, or Research preset
-
Import into Logseq:
- Open Logseq โ Settings (โ๏ธ) โ Import โ EDN to DB Graph
- Select the downloaded
.ednfile
-
Start using structured types:
#Personโ email, jobTitle, birthDate, etc.#Organizationโ legalName, employee, member, etc.#Eventโ eventStatus, attendee, organizer, etc.
Detailed guide: QUICK_START.md
๐ฆ What's Included
Classes (Types)
- Thing - Base class for everything
- Person - People with contact info, relationships, occupations
- Organization - Companies, teams, institutions
- Event - Meetings, conferences, occasions
- EventSeries - Recurring events
- BusinessMeeting - Work meetings
- Place - Locations and addresses
- Occupation - Job roles and skills
- Schedule - Recurring time patterns
- Audience - Target groups
- Resource - Generic resources
Property Types
Properties support multiple types:
- Text - Free-form content
- Node - Links to other pages (relationships)
- Date - Calendar dates
- URL - Web links
- Number - Numeric values
- Choices - Pre-defined options (like event status)
Example: Person Class
When you tag a page with #Person, you automatically get these properties:
- jobTitle
- givenName (first name)
- familyName (last name)
- birthDate
- spouse (links to another Person)
- children (multiple Person links)
- worksFor (links to Organization)
- alumniOf (educational institution)
- knows (other people)
- skills
...and 15+ more Schema.org properties!
๐ ๏ธ For Template Developers
Want to contribute or customize templates?
Quick Setup
# 1. Clone repository
git clone https://github.com/C0ntr0lledCha0s/logseq-template-graph.git
cd logseq-template-graph
# 2. Install all dependencies (includes @logseq/cli, git hooks)
npm install
# This installs Logseq CLI and checks for Babashka (optional)
# 3. Install Babashka (for modular workflow - recommended)
# Mac: brew install borkdude/brew/babashka
# Windows: scoop install babashka
# Linux: bash < <(curl -s https://raw.githubusercontent.com/babashka/babashka/master/install)
# 4. Set your graph path
export LOGSEQ_GRAPH_PATH="$HOME/Logseq/template-dev" # Mac/Linux
# Or: $env:LOGSEQ_GRAPH_PATH = "C:\Users\...\template-dev" # Windows
# 5. Start developing!
npm run export
Development Workflow
# 1. Make changes in Logseq
# ... edit classes, properties ...
# 2. Export and auto-split into modules
npm run export
# 3. Build template variants (optional)
npm run build:full # Full template
npm run build:crm # CRM preset
npm run build:research # Research preset
# 4. Review modular source changes
git diff src/
# 5. Commit using conventional commits
git add .
git commit -m "feat(classes): add Recipe class with cookTime property"
# 6. Push to your fork
git push origin feat/add-recipe-class
Features:
- โ NPM-based workflow - No global installs needed
- โ Modular architecture - Split 15K+ line templates into manageable modules
- โ
Auto-split on export - Automatically splits into
src/modules - โ Template variants - Build full, CRM, research presets from modules
- โ Automated commit validation - Conventional commits format
- โ Auto-generated changelogs - From commit history
- โ CI/CD integration - Automated releases and validation
Complete guides:
- CONTRIBUTING.md - How to contribute (includes commit standards)
- QUICK_START.md - 5-minute developer setup
- Conventional Commits Guide - Commit message standards
- CI/CD Pipeline - Full automation workflow
- Modular Development - For large templates
๐ Documentation
๐ Organized Documentation: Documentation Portal - All guides organized by category in the docs/ folder.
Quick Index: DOCS_INDEX.md - Complete documentation map by task and audience.
Quick Access
| Guide | For | What's Inside |
|---|---|---|
| QUICK_START.md | Users & Developers | Installation, import instructions, dev setup |
| CI/CD Pipeline | Developers | Workflows, automation, modular development |
| Technical Reference | Developers & AI | EDN format, classes, best practices |
| Comprehensive Analysis | Everyone | Deep dive: Logseq DB, Tana, Schema.org |
| Modular Quickstart | Developers | For large templates (15K+ lines) |
Recommended Reading Order:
- Users: README โ QUICK_START
- Developers: QUICK_START โ CI/CD Pipeline โ Technical Reference
๐ Why Use This Template?
vs. Starting from Scratch
โ Without template:
- Blank slate, no structure
- Inconsistent property names
- Reinvent the wheel for common types
- Hours of setup work
โ With this template:
- Instant structure for common types
- Schema.org standard naming
- Ready to use in seconds
- Battle-tested vocabulary
vs. Tana
This template brings Tana's supertag experience to Logseq:
| Feature | Tana | This Template |
|---|---|---|
| Typed objects | โ Supertags | โ Classes |
| Auto fields | โ | โ Properties |
| Inheritance | โ | โ Class parents |
| Open source | โ Proprietary | โ MIT License |
| Local-first | โ Cloud | โ Local SQLite |
| Cost | ๐ฐ Paid | ๐ Free |
๐ค Contributing
Contributions welcome! We'd love your help expanding this template library.
How to Contribute
- Fork this repository
- Set up the development environment (guide)
- Make changes in your Logseq graph
- Export using
./scripts/export.sh - Submit a pull request
What to Contribute
- New Schema.org classes (Book, Article, Recipe, Product, etc.)
- Additional properties for existing classes
- Domain-specific templates (Research, CRM, Project Management)
- Documentation improvements
- Bug fixes and validation improvements
Contribution Guidelines
- Follow Schema.org naming conventions
- Include icons and descriptions for new classes/properties
- Test imports before submitting
- Update documentation as needed
See: CI/CD Pipeline for detailed development process
๐ Learn More
About the Technologies
-
Logseq Database - SQLite-based knowledge management (2025 alpha)
-
Schema.org - Structured vocabulary for the web
-
Tana - Inspiration for supertag paradigm
๐บ๏ธ Roadmap
Phase 1: Core Foundation โ
- Core classes (Person, Organization, Event, Place)
- Automated export workflow
- Comprehensive documentation
- CI/CD pipeline
Phase 2: Expansion ๐ง
- Add CreativeWork classes (Book, Article, Recipe)
- Add Product and Review classes
- Community sharing and feedback
Phase 3: Ecosystem ๐ฎ
- Multiple template variants (CRM, Research, Content)
- Query templates and examples
- Video tutorials
- Template marketplace
๐ License
MIT License - see LICENSE
๐ฌ Community & Support
Get Help
- GitHub Issues - Bug reports and feature requests
- Logseq Forums - General discussion
- Documentation - Comprehensive guides
Stay Updated
- Watch this repository for new releases
- Check the Roadmap for upcoming features
- Join discussions in issues and pull requests
๐ Acknowledgments
- Logseq Team - For building an amazing open-source knowledge tool
- Schema.org - For providing standardized vocabulary
- Tana - For pioneering the supertag paradigm
- Community - For feedback and contributions
Made with โค๏ธ for the Logseq community
Give Logseq Database the structure it deserves! โก
Quick Links: Quick Start | Developer Guide | ๐ Documentation | Contributing