Headbase is in active development and not yet ready for use. This roadmap is currently focused on the technical development efforts, however over time should hopefully become more user facing.
- IN PROGRESS Refactor base application like file explorer, content type manager etc to also use plugin system
- Iinitial work tested on desktop and mobile
- ensure txt files can still be edited, seems to be regression
- Next step is allowing plugins to be opened with data, for example so the file explorer could be opened with a filePath
- Possible refactor file editor to just be another workspace plugin, to remove the special handling of this single case.
- Content Types
- Store content types in
/.headbase/config/content-types.json. One file allows for better performance.
- Content type data includes:
- id - added to markdown file frontmatter as
$type to identify content type of files
- name, description
- create rules:
- folder pattern
- filename pattern
- Templates - allow creating content with template content, for example a note with tags applied etc
- Allow overwriting create rules
- File creation
- Allow creating any file via dialog by typing file type
- Add warning for files which don't have any editors, or editors that are only read-only
- Allow creating markdown files using content types and templates
- Dynamic Fields
- Functionality used by plugin settings, content types, and content type based editing
- Define fields, use this to display fields, get output of data fields
- Content Type Based Editing
- Use
$type frontmatter property to load custom editing interface based on content type fields
- View Editing
- Add ability to edit/preview views including adding sources, displays etc
- Plugin Management
- Add ability to view and manage plugins including editing settings
- Other (TBC)
- Displaying of files in views based on content types?
- Inline editing of files in views (via popup/inline fields etc)?
- Add vault settings, device settings
Headbase is in active development and not yet ready for use. This roadmap is currently focused on the technical development efforts, however over time should hopefully become more user facing.
/.headbase/config/content-types.json. One file allows for better performance.$typeto identify content type of files$typefrontmatter property to load custom editing interface based on content type fields