feat: index JSON #249
Labels
No Label
in progress
kind/bug
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/security
kind/testing
kind/translation
kind/ui
lgtm/done
lgtm/need 1
lgtm/need 2
priority/critical
priority/low
priority/maybe
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
status/blocked
status/needs-feedback
status/wip
No Milestone
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/blog#249
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "jolheiser/blog:feats"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This will expose a JSON endpoint with all the pages and some meta.
It would allow us to, for example, filter posts by
tag
and maybe link to them from our main docs.e.g. a follow-up PR to tag any "feature preview"-style posts and then link to them from our docs.
Website preview: http://preview-gitea-org-blog-blog-249.s3-website.eu-central-1.amazonaws.com/
New endpoint: http://preview-gitea-org-blog-blog-249.s3-website.eu-central-1.amazonaws.com/index.json
@ -22,0 +23,4 @@
home:
- HTML
- RSS
- JSON
Will that still work when we switch to Docusaurus?
afaik the blog isn't switching to docusaurus, or at least not that I know of currently
Ah. You're absolutely right.
I confused it with
docs.gitea.io
.fwiw I'm not entirely sure we want all of each page's content, it would come in handy for searching but otherwise may just blow up the JSON payload.
We can use anything in the page variable, so I'm open to ideas. Perhaps
Summary
? Or just omitting content altogether.