SpandToon

Groups that publish series either build every site from scratch or live within the limits of a ready-made theme. The reader side is little more than "stack the pages", the panel cannot handle bulk uploads, and ads, membership and community get patched on later.

I built the system from scratch: 24 modules toggle from the panel, and every install runs with its own brand and its own database.

SpandToon is not one site; it is the core that produces sites. Brand, theme, copy and modules come from settings, so a new manga or webtoon site is prepared from the same platform without writing code. A site built on it is live today; at its owner's request I do not share the address.

• A hundred reads, one write. Views are buffered in memory and written in batches; a popular chapter never chokes the database, and the same reader reopening a page is not counted twice.
• Protected yet fast images. Chapter pages are served through expiring signed links; signatures are generated per time window, so the CDN cache stays intact.
• Load test. The cached home page served about 30k requests per second from a single server, with zero errors at 4,000 concurrent connections.
• Real traffic. On a site running this platform, with 3,000 chapters published, 840 readers read at the same time; a single 4-core, 8 GB RAM server served them without lag or waiting.

Writing a site and writing the system that builds sites are different jobs. Once every feature is a module, a new install changes settings, not code, and maintenance stays in a single codebase.