Turning a story site into a self-running literary community

Overview

Fiction Factory (fictionfactory.org) is a literary community where members read, write, publish and sell fiction. We turned it from a publishing site into a self-sustaining, community-driven platform, and most recently added a purpose-built social Feed that lifted engagement within weeks of launch.

The challenge. A literary site only grows if readers come back and writers keep writing. That needs rewards for taking part, tools that make writing easy, moderation that keeps the community trusted, and an admin team that can run it without developers.

What we built. In the latest build phase (June 4 – September 18, 2026) the commit history shows 132 commits and about 72,000 lines added across 15 feature areas: gamification, a full Novel Studio, a moderation system, a unified social Feed, a reading library, author analytics, a help center and a complete brand refresh.

The result. After the Feed launched, average pages per visit rose from 3.1 to 7.9 and average visit length from about 3 to nearly 6 minutes, with daily visits roughly 2.7 times the pre-Feed level (details under Results).

Today the platform serves 14,053 members and 20,448 posts, with 582 new posts in the latest week (homepage figures, October 15, 2026).

The Fiction Factory homepage with its featured story, editors' picks and live community counts

Feature list

Every item below traces to a commit in the project history, grouped by what it does for the community.

The Help Center: guides to reading, writing and earning, searchable and organized by topic

The Help Center and the changelog keep members informed. The Help Center is a searchable knowledge base for members, organised into 15 topics, including getting started, the Feed, writing posts, books and Book Studio, web fiction, moderation, comments, voting, achievements and XP, earnings and withdrawals, notifications and how to report a problem. Search opens with a single key press. A "What's New" button on every page opens the changelog, where each release is written in plain language under New, Improved and Fixed. Between September 17 and October 6, 2026 it recorded 14 numbered releases, from v2.0.0 to v2.11.0. Admin-only changes are kept in a separate technical changelog.

The changelog: every release listed with its date and number of changes, and each change written in plain language under New and Improved

The development journey

The work happened in eight overlapping phases. Each one answered a specific problem the community or the team was facing.

1. Giving members a reason to return (June)

Challenge. Participation had no memory: nothing rewarded regular readers or writers, and long-time members had no visible record of what they had done.

Solution. We built achievements, streaks, events and an XP system with an admin UI, then wrote backfill jobs that replayed past activity (onboarding, loyalty, sales, milestones) so existing members were credited from day one instead of starting at zero. A follow system with events and mail came next.

2. Modernizing the foundation (late August)

Challenge. The admin panel and framework were aging, which slowed every later feature.

Solution. We migrated the admin from Backpack to Filament, upgraded to Laravel 13, Filament 5 and the permissions packages, and restored the editorial article workflow on the new stack. We also isolated the test suite from the real database and fixed stale-cache and config failures found on the way, so later releases were safer.

3. Protecting community trust (late August to mid-September)

Challenge. A growing community attracts spam, and heavy-handed moderation drives good writers away.

Solution. We added spam-user prevention and cleanup, content spam checks that store the reason for every flag, and notify the author. Admins got a review queue with action history and report detail pages. Notices to authors are anonymous, so reporters are not exposed, and penalties apply to confirmed spam.

4. Making votes and comments fair

Challenge. Instant, unmoderated votes and comments are easy to game.

Solution. Votes settle with a debounce in the style of StackOverflow, comments have a realistic cooldown and a two-minute edit window, and links are checked for safety. Both systems are documented for members.

5. Turning a post site into a Novel Studio (early September)

Challenge. Serialized novels lived as ordinary posts, with no structure for books, chapters, covers or sales.

Solution. We designed a book and chapter schema and migrated legacy chapters into it, then built the writer studio, public reader and showcase. The editor moved from Trix to TipTap and was shared with the post writer. Novels and chapters became purchasable through cart, checkout and earnings. Legacy URLs were redirected with 301s so existing links and search rankings were kept.

6. Findability and speed (September)

Challenge. A Bengali-language archive needs clean URLs, fast pages and working search.

Solution. We fixed Bengali slug collisions and drafts that never reached readers, improved transliteration, added a site-wide search modal and a novel sitemap, sped up the homepage cache rebuild, and added indexes and monthly rollups so the daily-views table stops growing without limit.

7. The Feed (September 11–18)

Challenge. Members had no place for everyday conversation, so activity stopped when they finished reading or posting.

Solution. We introduced usernames and @mentions, replaced the first microblog with a unified Feed, added auto-refresh and surfaced engagement on every item. Follows stay out of the public Feed. Presence tracking shows who is online, and guided tours (driver.js) teach new members the features. A reader/writer rework then added reading state, book follows, beta reads and a Reader Bounty.

8. One brand across everything

Challenge. Pages built at different times looked and behaved differently.

Solution. We moved the accent palette to amber and earth tones, applied a "paper" theme to public pages, rebuilt the member workspace on brand tokens, added mobile dark mode, and wrote a brand standard so new screens stay consistent.

Feature highlights

The Feed is the largest single piece of work. It replaced a simple microblog with one stream that mixes notes, posts and book activity. Members mention each other, see live engagement and get guided tours on first use. The later reader/writer rework gave it purpose for both sides: readers track what they are reading and follow books, writers can run beta reads and reward their first readers with a Reader Bounty paid from their own XP, which lifts their story to the front of the shelf.

The Feed: stories still waiting for a first reader, each with the XP a thoughtful first comment earns

Novel Studio gives writers a calm, distraction-free place to draft: autosaving drafts that survive a refresh, a mobile step-by-step wizard, a dark-mode editor, auto-generated covers, a live checklist and an AI hook generator. Readers get a clean public reader and showcase shelf, and writers can sell novels and chapters.

The book setup page: cover, title, synopsis, genres, web fiction and premium options before a writer enters the studio

The chapter editor: table of contents, distraction-free writing page, a ready-to-publish checklist, and beta reader and Reader Bounty actions

On a phone the studio becomes a three-step flow (book setup, write, publish), with chapter settings one tap away.

Writing a chapter	Chapter settings
The mobile chapter editor with the three-step progress bar and formatting toolbar	Chapter settings on mobile: publish checklist, publish status, beta readers and Reader Bounty

The Serials bookshelf: 44 books by 27 authors, browsable by genre, with a weekly front shelf

Moderation is built to protect good members first. Every flag stores its reason, authors are told why without learning who reported them, and admins work from a single review queue with a full action history.

The admin dashboard: a to-do panel with errata, reports, pending tasks, content quality and withdrawals, and a pulse row with members online, new signups and traffic

Content that trips the spam checks lands in one queue, with the reason it was flagged. An admin can mark it reviewed, clear it as not spam, unapprove it or delete it.

The pending moderation queue: auto-flagged stories with the reason each was flagged and four actions per item

Gamification connects the whole platform. XP and achievements reward reading, writing and helping, and XP can be spent on real perks such as featured posts, so activity feeds back into visibility.

The Achievements page: 30 honours across three tiers, each showing the XP it earns and how many members hold it

The member desk pulls it together for each person: XP and progress to the next level, drafts that need attention, and shortcuts to write, manage books, track orders and earnings.

A member's desk: level and XP progress, drafts needing attention, and totals for posts, views, spend and sales

The reading library and author analytics serve both sides of the community. Readers see the books they are in the middle of, with the next unread chapter, plus everything they have followed, saved, bought, liked or commented on. Writers can open any post and see views, comments, upvotes, sales and earnings over 7, 30 or 90 days.

The reading library: books in progress with the next unread chapter, and tabs for following, saved, purchased, liked and commented

Post analytics: views, comments, upvotes, sales and earnings for one post, with a views-per-day trend

Notifications keep members coming back. Replies, mentions, follows and unlocked achievements arrive in one place, with an unread filter.

The notifications page: replies to comments, unlocked achievements and new followers, with All and Unread filters

Results

Visitors now view more pages, stay longer and arrive in larger numbers than before the Feed launched. The table compares three windows from Google Analytics 4. The September 21–23 bot traffic (about 34,000 junk sessions from one datacenter) is excluded.

Engagement rate, the share of visits that last 10 seconds or more or view several pages, held near 57% at launch and eased to about 50% as traffic grew. Pages per session and session length kept rising. Over the longer term, average daily sessions climbed from about 260 in September 2025 to 540–580 since the Feed launch.

Source: Google Analytics 4, property Fiction Factory, pulled October 8, 2026.

Engineering by the numbers

Between June 4 and September 18, 2026 the project history records 132 commits that changed about 1,400 files, adding roughly 71,700 lines and removing 16,800. Adjusted to a common PHP-equivalent measure, the new code comes to about 62,700 lines, and the effort is estimated at about 82 working days.

The work was shipped in small, documented steps, with 14 numbered releases between September 17 and October 6, 2026: voting, commenting, view rollups and admin operations each have written docs, and every major system was introduced with tests that no longer touch the live database.

What it adds up to

Fiction Factory now rewards taking part, makes writing easy, protects its members, gives people a place to talk, and explains itself through a searchable Help Center and a public changelog. The Feed is the visible layer, and the traffic numbers show it working. Underneath it sits a modern, documented codebase the team can keep building on.