-
Notifications
You must be signed in to change notification settings - Fork 466
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
Valid JSON feeds #11
Comments
patdryburgh
added a commit
that referenced
this issue
Oct 19, 2018
@bmann I've pushed a change that adds the missing curly bracket and commas in the JSON feed. You can see that the feed is now passing here: http://validator.jsonfeed.org/?url=https%3A%2F%2Fpatdryburgh.github.io%2Fhitchens%2Ffeed.json |
GhostofSky
pushed a commit
to GhostofSky/DPGATranslations
that referenced
this issue
Apr 21, 2023
GhostofSky
pushed a commit
to GhostofSky/DPGATranslations
that referenced
this issue
Apr 21, 2023
GhostofSky
added a commit
to GhostofSky/DPGATranslations
that referenced
this issue
Apr 21, 2023
GhostofSky
added a commit
to GhostofSky/DPGATranslations
that referenced
this issue
Apr 21, 2023
GhostofSky
pushed a commit
to GhostofSky/DPGATranslations
that referenced
this issue
Apr 21, 2023
GhostofSky
pushed a commit
to GhostofSky/DPGATranslations
that referenced
this issue
Apr 21, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pat, I used your JSON feeds as the basis for my own. Here are the gists I have for a
feed.json
(which has all the long form blog posts) and amicro.json
(which has short posts only):https://gist.github.com/bmann/38b54d893d506d2eb8bb8b325eafaccf
A note: right now, the micropub server I'm using defaults to setting category of short posts to "social", which I couldn't fix, so I just changed it in my Jekyll install.
Also, because of some of the rest of the Jekyll theme that I inherited, I purposefully don't include title in the micro feed.
Lastly, my theme / setup supports a date modified field, so I included that.
The validator for checking feeds is here: http://validator.jsonfeed.org/
(and apologies for not having a Pull Request for you, a lot of this stuff ends up being pretty blog specific)
The text was updated successfully, but these errors were encountered: