In Lemmy, the default object type for a Post is **Page**, which inherits its properties from **Document**.

[Jiwoon-Kim]

In Lemmy, the default object type for a Post is Page, which inherits its properties from Document.

"mediaType": "text/html" or "mediaType": "text/markdown"
Reference: [Lemmy Federation Docs](https://join-lemmy.org/docs/contributors/05-federation.html#post)

According to the ActivityStreams specification:
📄 [Page](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-page)
is a subtype of Document, just like Audio, Image, or Video.

In fact, Document objects such as PDFs are something WordPress can already manage quite well through the Media Library.
That’s why it seems natural to consider mapping the WordPress Media Library to a Document object controller within the ActivityPub context.

However, there’s a key complication:
since Lemmy uses the Page object as the default post type, directly mapping the WordPress Page post type to the ActivityPub Page object becomes quite tricky.

WordPress Pages are conceptually used for static content or hierarchical site structure, not for user-generated posts or discussions.
Therefore, using Page as the ActivityPub type for posts could introduce confusion — both semantically and structurally — especially when aligning with Lemmy’s federation model.

---

Would you like me to expand this into a proposal paragraph (e.g., suggesting an alternative mapping like Note or custom ObjectType meta for CPTs)?