Skip to content
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

Feature Request: Customize template output on WordPress Post Types! #820

Open
DeadSuperHero opened this issue Jul 25, 2024 · 0 comments
Open

Comments

@DeadSuperHero
Copy link

What

Instead of having a singular catch-all for customizing ActivityPub output, allow admins to customize it by individual WordPress post types.

Why

We're increasingly looking into using our WordPress as our main hub for Fediverse interaction. It's super exciting, but we've found a bit of a snag: we would like to customize the output for the different WordPress post types we're using to better suit our Fediverse audience.

Right now, we use all of these:

  • Long-form Standard Articles
  • Short-form Notes, intended to act as statuses
  • Podcast Episodes
  • We're also considering integrating the Event type with a calendar.

Each post type has different requirements, which means that the catch-all can make one of the four look good, but can affect the other ones act in unexpected ways.

Being able to specify what fields get federated out will make the timeline look a lot nicer for people following us from all kinds of platforms.

How

What would be really useful is if each post type offered the same box for specifying markup, as well as whether there should be any attachments.

For our needs, this could look like the following:

  • Standard: Note type, customized body: Excerpt and HTML link, no attachments.
  • Status: Note type, customized body: full content with linked hashtags, 4 attachments.
  • Podcast: Note type, 1 attachment that's just an audio file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant