obsidian-plugin/jalad25_contact-note
1
0
Fork 0
mirror of https://github.com/jalad25/contact-note.git synced 2026-07-22 06:53:06 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update ROADMAP.md

Browse source
This commit is contained in:
Jalad 2026-06-13 00:45:27 -05:00 committed by GitHub
parent e8c53a86da
commit 9e2595c373
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 6 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
ROADMAP.md
View file

@ -1,5 +1,5 @@
# Roadmap
> **Last updated: 2026-05-28**
> **Last updated: 2026-06-12**
High-level direction for this plugin.
@ -11,15 +11,18 @@ See [Milestones](https://github.com/Jalad25/contact-note/milestones) for current
Planned for upcoming releases. Order is approximate and may change.
> Nothing specifically planned yet. See currently scheduled for what's being worked on.
- **Frontmatter property usage toggle** — let users toggle if specific built-in frontmatter properties are used by the Contact Note plugin within contact cards and new contact note templates. Will be set in the settings tab. `firstName`, `middleName`, and `lastName` will always be included (not able to be toggled).
- **Contact Card details view toggle** — add option in settings tab to toggle contact card details view to render all values in the details section of the contact card as collapsable lists.
- **New built-in property: `addresses`** — a property containing EITHER an array of OR a map of named address entries (e.g. home, work) for a contact. Each address entry contains `streetLineOne`, `streetLineTwo`, `city`, `state`, `zip`, and `country`, with the array version requiring an additional `addressName` property in the frontmatter to allow for the usage of the optional icon and label defined in the settings tab. Available alongside the existing built-in fields and respecting the same frontmatter customization (rename, icon, toggle usage). The `addresses` key itself can be renamed and a list of address names, along with optional icon and label, can be defined within the settings tab. User can add as many named entries as they'd like. The user will also be able to define the default icon to be used if no named address entries are present in the settings tab. Will appear to the right of (or after in collapsible list) phone numbers in contact card.
- **Add `emails` and `phoneNumbers` support for mapped, named entries** - *REQUIRES MIGRATION* similar to `addresses`, the `emails` and `phoneNumbers` properties will allow a map of named entries (e.g. home, work) to be set in the property, in addition to allowing arrays. For array versions an additional `emailName` for `emails` and `phoneNumberName` for `phoneNumbers` properties will be required if the user wishes to use the optional icon and label defined in the settings tab. User can add as many named entries as they'd like. The user will also be able to define the default icon for each parent property to be used if no named entries are present in the settings tab.
## Wishlist
Features being considered, but would like more feedback before pursuing. Order is not priority and some of these may never happen. See [CONTRIBUTING.md](CONTRIBUTING.md) on how to provide feedback!
- **VCF importing support** — bring contacts from another address book (phone, Google Contacts, iCloud, etc.) into the vault by importing a .vcf file. Each card lands as a standard contact note with the plugin's frontmatter shape, so imported contacts behave identically to ones created in-vault.
- **Custom frontmatter properties** — let users define their own contact properties beyond the built-in set (e.g., relationship, nickname, pronouns), with the same first-class treatment built-ins get: appear in the new-contact template, render on the contact card, and respect the same renaming and icon customization.
- **Templates** - let users define what properties (including possibly custom if done first) the template created by the New button populate.
- **VCF importing support** — bring contacts from another address book (phone, Google Contacts, iCloud, etc.) into the vault by importing a .vcf file. Each card lands as a standard contact note with the plugin's frontmatter shape, so imported contacts behave identically to ones created in-vault.
## Recently Shipped