Support events without microformats2 markup in RSVP post-type
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, node.js
Research direction
Start by reading the RSVP post-type plugin and the Web UI component that renders its publishing fields. Trace how fetched microformats2 references become the generated front matter, then add optional event name, start, and end inputs alongside the existing RSVP options. Done means an RSVP post can supply event metadata even when the linked page has no type=event, and the resulting front matter records type = "event" with the requested values.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem?
Is it possible to add some optional input fields in Indiekit's Web UI for RSVP posts for event links without microformats2 event markup?
For example, I tested Eventbrite.com and Meetup.com event links as the inReplyTo URL and although it was able to fetch the name and summary of the event, it doesn't realize the type=event, so it labels it as `type = "entry" in both cases.
And the following are missing (start, end or location data) in the front matter:
[references."$url"]
type = "entry" # should be "event"
name = "Fetched correct event name but sometimes includes too much (date, venue, publication name)"
summary = "Fetched correct event summary."
featured ="URL of image fetched"
publication = "Eventbrite"
start = # missing
end = # missing
[references."$url".location]
type = "card"
name = "venue address"
Describe the solution you’d like
Is it possibel to provide optional override Web UI input fields to markup the event metadata correctly when there is lack of microformats markup on an event page provider:
- Event name
- Start datetime
- End datetime
And ensure all posts created by the RSVP post-type plugin has type = event.
P.S. I am aware the post-type-event plugin provides the three fields I'm looking for, but I don't want to create my own duplicate of the event on my site just so I could RSVP to it with the correct metadata.
Thanks in advance!
Describe alternatives you’ve considered
No response
Additional context
No response
- Dominant language
- JavaScript
- Stars
- 392
- Forks
- 39
- Avg merge
- 22h 29m
- Merged PRs (30d)
- 25
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from getindiekit/indiekit
-
Docs: no path for someone who just wants to try IndiekitPossibly taken @rmdes claimed this 14 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
getindiekit/indiekit#1028 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
getindiekit/indiekit#1027 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
getindiekit/indiekit#1026 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 1-2 days Newbie friendliness 48/100
getindiekit/indiekit#1025 ·
Maintainers usually reply within 1 day
-
plugin-syndicator
Difficulty 4/5 3-5 days Newbie friendliness 48/100
getindiekit/indiekit#1022 · 1 reaction ·
Maintainers usually reply within 1 day
All issues in getindiekit/indiekit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ImranR98/apps.obtainium.imranr.dev#2000 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
microsoft/monaco-editor#5577 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
obsidianmd/obsidian-help#1169 ·
Maintainers usually reply within 2 days
-
[docs] RELEASE.md: wrong branch name, no check that the prepare PR merged with the right subject, manual publish stepPossibly taken @albertteoh claimed this today. Opendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
jaegertracing/jaeger-ui#4739 ·
Maintainers usually reply within 1 day