-
-
Notifications
You must be signed in to change notification settings - Fork 123
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
Migrate links.yaml to Netlify CMS Collections #155
Comments
The slug configuration might be useful as well, specially if a timestamp is, somewhat, useful for sorting |
Looks like we're still using links.yaml in netlify-cms too, #156 just part of it? What do we do next? |
…to a folder collection - added integrated terminal as option for debug
This PR should fix all broken thingies. Sorry about that. I might have been using a cached version and was focused on having the admin working. |
Split links.yaml into a NetlifyCMS collection
It would be easier to treat case by case, instead of having a
massive file that gets changed in every change under netlify-cms.
For instructions on setting this up in Gatsby, they've got a tutorial: https://www.gatsbyjs.org/docs/sourcing-from-netlify-cms/#setup
The text was updated successfully, but these errors were encountered: