question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Enhancement: Description/Help for metadata field definitions

See original GitHub issue

Is your feature request related to a problem? Please describe.

I’m working on a default frontmatter.json definition for users of my Hugo theme to be able to leverage because Front Matter seems like a tool that is absolutely going to help me give those users a more delightful experience. While trying to configure the metadata fields, I noticed that they don’t have something like an optional description key, which would help keep users from having to look things up.

Describe the solution you’d like

Ideally, there would be an optional description or help key (not fussed about the name) for metadata fields which would:

  • Display when a user hovers over that field name in the UI
  • Display in fainter text beside or below the field name

I think from a UX perspective, show-on-hover by default with an option to always display would be really stellar. If no description is provided, you get no hover text nor a description after the field name.

Describe alternatives you’ve considered

I could extend the title key for the metadata fields to include this information, but that could be distracting or confusing, I think.

Additional context

N/A

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
estruyfcommented, Sep 17, 2022

It just a simpel description line that is supported, but this gave me an idea.

Would a divider and header (which can include a description) make sense? That way, you can split the fields in sections.

1reaction
michaeltlombardicommented, Sep 16, 2022

Confirmed and it looks good! I tried using newlines which didn’t work, but I think that’s probably fine.

Screenshot of the updated view with per-field descriptions, the markdown file, and the frontmatter json

Read more comments on GitHub >

github_iconTop Results From Across the Web

Data Classification Metadata Fields - Salesforce Help
Data Classification Metadata Fields. Record the data owner, field usage, data sensitivity, and compliance categorization for any standard or custom object ...
Read more >
Proposal For Metadata Enhancement - LYRASIS Wiki
This proposal seeks to extend the definition of the DSpace Metadata Schema to include support of these features previously found only in the...
Read more >
MODS User Guidelines: Metadata Object Description Schema
Detailed Description of MODS Elements. Below is a detailed description of all of the valid MODS elements, attributes and values (revised to include...
Read more >
Using enhanced dataset metadata - Power BI - Microsoft Learn
With enhanced dataset metadata, metadata created by Power BI Desktop uses a format similar to what is used for Analysis Services tabular models ......
Read more >
Field properties - OCLC Support
CONTENTdm Administrators can view, define, and fully configure the list of collection metadata fields. These fields can be added, deleted, ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found