PhoenixKitPosts

Social posts module for PhoenixKit — user-generated posts with threaded comments, likes/dislikes, tags, Pinterest-style boards, media galleries, @mentions, view tracking, and scheduled publishing.

Not a blog/CMS. For long-form articles — Markdown/.phk content, slugged pages, versioned and multilingual publishing — use PhoenixKit's built-in Publishing module. PhoenixKitPosts is for social, feed-style posting: posts, likes, boards, mentions, and threaded comments.

Requirements

• Elixir ~> 1.18
• PhoenixKit ~> 1.7 (host application)
• Phoenix LiveView ~> 1.1

Installation

Add to your parent PhoenixKit app's mix.exs:

{:phoenix_kit_posts, "~> 0.2"}

Run mix deps.get. The module appears in the admin panel automatically via PhoenixKit's auto-discovery — no additional configuration required.

Features

• Post management — Create, update, delete, publish posts with draft/public/unlisted/scheduled status
• Threaded comments — Nested comments with unlimited depth, plus like/dislike tracking per comment
• Like and dislike system — One-per-user enforcement with denormalized counter caches
• Tag system — Hashtag parsing and auto-slugification
• Group collections — Pinterest-style boards for organizing posts with ordering
• Media attachments — Multiple files per post with position-based ordering and featured image support
• User mentions — Track @mentions within posts
• View tracking — Track post views with denormalized counters
• Scheduled publishing — Automatic publishing at a specified time via Oban workers
• Admin UI — LiveView-based admin pages for posts, groups, and settings

Usage

# Create a post
{:ok, post} = PhoenixKitPosts.create_post(user_uuid, %{
  title: "My First Post",
  content: "Hello world!",
  type: "post",
  status: "draft"
})

# Publish a post
{:ok, post} = PhoenixKitPosts.publish_post(post)

# Schedule a post for later
{:ok, post} = PhoenixKitPosts.schedule_post(post, ~U[2026-04-01 12:00:00Z])

# Like a post (one per user, enforced by unique constraint)
{:ok, like} = PhoenixKitPosts.like_post(post.uuid, user_uuid)

# Tag a post
PhoenixKitPosts.add_tags_to_post(post, ["elixir", "phoenix"])

# Create a group and organize posts
{:ok, group} = PhoenixKitPosts.create_group(user_uuid, %{
  name: "Travel Photos",
  description: "My adventures"
})
PhoenixKitPosts.add_post_to_group(post.uuid, group.uuid)

# Attach media
PhoenixKitPosts.attach_media(post.uuid, file_uuid, position: 1)

# Mention a user
PhoenixKitPosts.add_mention_to_post(post.uuid, mentioned_user_uuid)

# Query posts
posts = PhoenixKitPosts.list_public_posts(page: 1, per_page: 20)
post = PhoenixKitPosts.get_post_by_slug("my-first-post")

Configuration

Settings are managed through the PhoenixKit Settings API and can be configured via the admin UI at /admin/settings/posts.

Removing this module

There is deliberately no automated uninstall. PhoenixKitPosts.Migrations.down/1 never drops any of the 13 phoenix_kit_post*/phoenix_kit_comment_* tables or a row in them, for any target version — a host that merely removes this dependency from mix.exs has not consented to deleting every user's posts, likes, tags, groups, media, mentions, views and legacy comments, and a migration whose result depended on which packages happen to be compiled in would be nondeterministic (it would break core's manifest, chain hash, and squash verification). Removing the data is therefore a deliberate, manual operator step, in FK-safe order (children before parents):

-- Only after removing :phoenix_kit_posts from mix.exs, and only if you
-- actually want every post and everything attached to it gone for good.
DROP TABLE phoenix_kit_comment_likes;
DROP TABLE phoenix_kit_comment_dislikes;
DROP TABLE phoenix_kit_post_comments;
DROP TABLE phoenix_kit_post_media;
DROP TABLE phoenix_kit_post_mentions;
DROP TABLE phoenix_kit_post_views;
DROP TABLE phoenix_kit_post_likes;
DROP TABLE phoenix_kit_post_dislikes;
DROP TABLE phoenix_kit_post_tag_assignments;
DROP TABLE phoenix_kit_post_tags;
DROP TABLE phoenix_kit_post_group_assignments;
DROP TABLE phoenix_kit_post_groups;
DROP TABLE phoenix_kit_posts;

Dropping phoenix_kit_posts last also removes the pkpo_schema:<N> version marker, which is a COMMENT on that table — no separate step is needed.

If you want to keep the tables (e.g. you plan to reinstall the module later) but stop this chain from tracking them, clear the version marker instead:

COMMENT ON TABLE phoenix_kit_posts IS NULL;

Documentation

Generate docs locally with:

mix docs

Development

mix deps.get        # Install dependencies
mix test            # Run tests
mix format          # Format code
mix credo --strict  # Static analysis
mix dialyzer        # Type checking
mix precommit       # All of the above

License

MIT — see LICENSE for details.

Links

• GitHub
• PhoenixKit