You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've talked a little on the forum, in issue #13 and elsewhere about this need. Basically, Front Matter is supported out of the box with gatsby-transformer-remark, which I have already installed and am using to transform all our markdown into pages. It's really a matter of deciding on some consistent variables (as I've said elsewhere, I think title, date and slug are good variables to start with), add those variables to the GraphQL queries in the template and the createPages hook, and finally use those variables them for generating paths, rendering layouts, adding SEO metadata, etc.
The text was updated successfully, but these errors were encountered:
I added this to the beta milestone, but frankly, if a specific need for it doesn't arise in the course of adding other repos (#17) and migrating content from the old site (#12), then this shouldn't be a blocker.
I've talked a little on the forum, in issue #13 and elsewhere about this need. Basically, Front Matter is supported out of the box with
gatsby-transformer-remark
, which I have already installed and am using to transform all our markdown into pages. It's really a matter of deciding on some consistent variables (as I've said elsewhere, I thinktitle
,date
andslug
are good variables to start with), add those variables to the GraphQL queries in the template and thecreatePages
hook, and finally use those variables them for generating paths, rendering layouts, adding SEO metadata, etc.The text was updated successfully, but these errors were encountered: