▸case-01 I'm configuring frontmatter for my Obsidian notes to set up alternative titles so quick switcher can find them. A teammate suggested using `aka: [Project A, ProjA]` or `alt_title: ProjA` in the YAML header. What is the standard frontmatter key recognized natively by Obsidian for page aliases? | pass→pass | 3,861 | 4,086 | +6% | 1 | 1 | 0% | 750 | 705 | -6% | 0 | 0 | — |
▸case-02 I want to apply custom CSS styling to a specific note in Obsidian using theme snippets. I was planning to put `style: dark-card` or `theme: compact` in the frontmatter. Which standard frontmatter property key does Obsidian read to apply custom CSS classes to a note? | pass→pass | 4,130 | 3,595 | -13% | 1 | 1 | 0% | 663 | 662 | -0% | 0 | 0 | — |
▸case-03 I am publishing markdown notes with Hugo. I want to mark work-in-progress notes so the static site builder skips them during production builds. Should I use `status: draft` or `state: wip` in the YAML frontmatter header? | pass→pass | 8,115 | 7,501 | -8% | 1 | 1 | 0% | 1,540 | 1,339 | -13% | 0 | 0 | — |
▸case-04 In my Obsidian vault, I want to add inline metadata fields directly within the body paragraph of a note so Dataview can query them. I tried using single colon format like `Priority: High` or `Status: Active` inline inside my text sentences. How should inline metadata fields be syntax-formatted so Dataview parses key-value pairs inside text paragraphs? | pass→pass | 8,777 | 8,626 | -2% | 1 | 1 | 0% | 1,729 | 1,564 | -10% | 0 | 0 | — |
▸case-05 I am using Dataview inline fields in Obsidian body text, but I want the field value to render visually in reading mode as a styled key-value badge, hiding the key or highlighting the value. Should I wrap the field in standard parentheses `(status:: complete)` or brackets `[status:: complete]`? | pass→pass | 6,656 | 7,234 | +9% | 1 | 1 | 0% | 1,338 | 1,564 | +17% | 0 | 0 | — |
▸case-06 When generating summary cards for my notes on a Hugo site, I want to manually override the automatic text truncation excerpt. I was going to add `abstract: Short summary here` or `excerpt: Short summary here` to the YAML metadata. What is the official Hugo frontmatter field name for manual note summaries? | pass→pass | 5,154 | 5,299 | +3% | 1 | 1 | 0% | 962 | 981 | +2% | 0 | 0 | — |
▸case-07 I have a collection of markdown notes processed by Jekyll. I want to specify a non-default HTML template file for a specific note. Should I set `theme: documentation` or `template: document` in the YAML header? | pass→pass | 5,376 | 4,742 | -12% | 1 | 1 | 0% | 1,013 | 904 | -11% | 0 | 0 | — |
▸case-08 I have a draft note in a Docusaurus docs site that I want accessible via direct link but excluded from the sidebar navigation and search index. A developer suggested setting `hidden: true` or `no_index: true` in the frontmatter. What frontmatter property key does Docusaurus use to hide a doc from sidebars and search while keeping the page published? | pass→pass | 6,925 | 4,882 | -30% | 1 | 1 | 0% | 1,313 | 1,053 | -20% | 0 | 0 | — |
▸case-09 I am republishing notes on my personal site that were originally posted on Medium. To prevent SEO duplicate content penalties, I need to specify the original URL in the markdown header. Should I add `original_url: https://...` or `source_link: https://...` in the YAML metadata for standard static site generators like Hugo or Jekyll? | pass→pass | 9,171 | 8,775 | -4% | 1 | 1 | 0% | 1,802 | 1,688 | -6% | 0 | 0 | — |
▸case-10 I want to override the default URL path generated from a note's filename in my static site generator (Hugo/Jekyll). My team suggested using `path: /my-custom-url` or `url_path: /my-custom-url` in the frontmatter. What standard YAML frontmatter attribute is universally used to set a custom URL segment? | pass→pass | 9,081 | 7,493 | -17% | 1 | 1 | 0% | 1,868 | 1,547 | -17% | 0 | 0 | — |
▸case-11 I am assigning thumbnail images to notes in Hugo for social media preview cards. Should I use `thumbnail: header.png` or `banner: header.png` in the YAML frontmatter? | pass→pass | 10,312 | 9,048 | -12% | 1 | 1 | 0% | 1,825 | 1,710 | -6% | 0 | 0 | — |
▸case-12 In my Zettelkasten knowledge base, I want to classify notes by structural level (e.g., fleeting, literature, permanent). Should I invent separate YAML headers like `is_fleeting: true` or use a standard taxonomy field in the frontmatter? | pass→pass | 10,480 | 10,288 | -2% | 1 | 1 | 0% | 1,908 | 2,011 | +5% | 0 | 0 | — |
▸case-13 I am setting tags in my Obsidian note YAML frontmatter. A colleague recommended writing tags as a comma-separated string `tags: idea, project, urgent`. What is the recommended YAML format for tags in Obsidian to prevent single multi-word tag parsing errors? | pass→pass | 8,934 | 8,416 | -6% | 1 | 1 | 0% | 1,691 | 1,639 | -3% | 0 | 0 | — |
▸case-14 When using Obsidian Publish to selectively publish notes to the web, I want to mark specific notes for publishing. Should I write `status: published` or `web: true` in the frontmatter? | pass→pass | 7,464 | 11,179 | +50% | 1 | 1 | 0% | 1,424 | 1,810 | +27% | 0 | 0 | — |
▸case-15 I am configuring creation date fields in note frontmatter for automated sorting in Dataview and static site generators. A contributor suggested writing dates like `date: October 24, 2023` or `created: 10/24/2023`. What ISO standard format should be used in frontmatter to ensure reliable lexicographical and chronological sorting? | pass→pass | 9,714 | 10,153 | +5% | 1 | 1 | 0% | 1,879 | 2,067 | +10% | 0 | 0 | — |
▸case-16 I want to reference other notes inside a YAML frontmatter field in Obsidian, such as `related: [[Project Beta]]`. When writing wiki-links inside YAML metadata header, why does unquoted `related: [[Project Beta]]` cause a parsing error, and how should it be formatted? | pass→pass | 9,162 | 8,088 | -12% | 1 | 1 | 0% | 1,682 | 1,563 | -7% | 0 | 0 | — |
▸case-17 I am ordering Markdown documentation pages in Docusaurus. Instead of prefixing filenames with numbers, I want to set explicit ordering inside the YAML frontmatter. Should I use `order: 5` or `index: 5` in the YAML header? | pass→pass | 6,049 | 3,849 | -36% | 1 | 1 | 0% | 1,130 | 866 | -23% | 0 | 0 | — |
▸case-18 When defining note properties in Obsidian, if a property value is an array of strings versus a checkbox boolean property, how are these formatted in raw YAML frontmatter? | pass→pass | 6,959 | 7,864 | +13% | 1 | 1 | 0% | 1,354 | 1,449 | +7% | 0 | 0 | — |
▸case-19 In Hugo notes, I want to group notes under broad topics separate from tags. Should I define custom fields like `topic_group: Tech` or use Hugo's default taxonomy field alongside tags? | fail→pass | 10,617 | 9,749 | -8% | 1 | 1 | 0% | 2,085 | 1,770 | -15% | 0 | 0 | — |
▸case-20 I am writing a research note in Markdown and need to add an inline footnote reference and the matching bottom footnote text. How do I construct standard extended Markdown footnotes in body text? | pass→pass | 6,684 | 3,873 | -42% | 1 | 1 | 0% | 1,226 | 739 | -40% | 0 | 0 | — |
▸case-21 I need to construct a comparison table inside the body of my Markdown note comparing three software tools across features. How do I format a standard Markdown table using pipes and dashes? | pass→pass | 6,302 | 4,010 | -36% | 1 | 1 | 0% | 1,319 | 763 | -42% | 0 | 0 | — |
▸case-22 I am committing updates to my PKM markdown notes repository using Git command line. What is the standard Git command to record a commit with a descriptive message? | pass→pass | 3,299 | 2,330 | -29% | 1 | 1 | 0% | 533 | 437 | -18% | 0 | 0 | — |