Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement: Extend requirement for content #473

Closed
DennisL68 opened this issue Nov 30, 2022 · 2 comments
Closed

Enhancement: Extend requirement for content #473

DennisL68 opened this issue Nov 30, 2022 · 2 comments

Comments

@DennisL68
Copy link

Is your feature request related to a problem? Please describe.
Currently, a markdown file has too contain the following front matter to be considered a content file

---  
title: ""  
description: ""  
---  

This mean that Title: "" won't qualify.

Describe the solution you'd like
Approve a file as content if using

---  
Title: ""  
Description: ""  
---  

as well, if the framework selected supports it.

Additional context
Add any other context or screenshots about the feature request here.

@DennisL68 DennisL68 added the enhancement New feature or request label Nov 30, 2022
@estruyf
Copy link
Owner

estruyf commented Feb 4, 2023

Thanks, @DennisL68, for the description, the solution is simple. You can configure the frontMatter.taxonomy.seoDescriptionField setting by setting the value to Description. That will allow you to use the Description field. Make sure to also change the name of the field in your content type.

For the title, the setting will have to be created so it will be enhanced in the upcoming version.

@estruyf
Copy link
Owner

estruyf commented Feb 4, 2023

A new setting just got added: frontMatter.taxonomy.seoTitleField, with this setting, you are able to set the default title value to Title and will make sure your content cards are rendered correctly and that the SEO status works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants