Obsidian and Markdown¶

Obsidian is optional.

Songcards supports a structured Markdown format because a useful song record should not become unreadable just because you are outside the app.

The files are ordinary Markdown text with structured frontmatter for Songcard data. You can open them in Obsidian, another Markdown editor, or a normal text editor.

No Songcards-specific Obsidian plugin is required.

Why use Markdown?¶

Markdown is useful when you want to:

• keep a Songcard in a plain-text workflow;
• edit song notes or lyrics in Obsidian;
• move a Songcard between Songcards and a Markdown vault;
• keep a readable version outside the desktop interface.

It is a portability option, not a second database you are required to maintain.

Export a Songcard to Markdown¶

Use Songcards' Markdown export for the Songcard you want to work with.

The exported file contains structured Songcard information plus readable Markdown content.

Open that file in Obsidian if you use it, or in another editor if you do not.

Import Markdown into Songcards¶

Songcards can import its supported Markdown structure back into the application.

For reliable round-tripping, keep the Songcards frontmatter structure intact. You can edit the values and the Markdown content, but avoid casually renaming structural keys if you intend to import the file again.

Current Songcards Markdown supports the current Song identity model, including catalogue number, status information, multiple languages, genres, duration and work type alongside the rest of the Songcard information.

The template¶

Songcards can provide the current Songcards Markdown/Obsidian template through its export tools. That makes it possible to start a record in Markdown and bring it into Songcards later.

The template is still useful without the desktop app: it is ordinary text, not a proprietary Obsidian plugin format.

A practical workflow¶

One simple workflow is:

1. Start with a Songcard in Songcards or with the Songcards Markdown template.
2. Edit the Markdown in Obsidian when that is the more comfortable writing environment.
3. Import the supported Markdown file into Songcards when you want it back in the structured library.
4. Continue working in Songcards and export again when needed.
5. Keep a full Songcards backup separately for actual library recovery.

What Songcards does not require¶

You do not need:

• an Obsidian account for Songcards;
• an Obsidian plugin made by HugByte;
• Obsidian itself;
• cloud sync.

If your editor can open Markdown, the file remains readable.

See Import & export for the other supported data flows.

Next: SongCards FAQ.