Foundation and webapp reboot
September-December 2024
AngryPages began as a webapp repository, then restarted around a clearer website codebase, login/logout, user-system basics, forms, and product direction.
Webapp Changelog
Full AngryPages webapp history, shaped from git into tidy release notes without exposing private or sensitive commit wording.
A future CEO, engineer, or AI should be able to see the product arc first: foundation, launch, billing, media, safety, AI, publishing, and polish.
September-December 2024
AngryPages began as a webapp repository, then restarted around a clearer website codebase, login/logout, user-system basics, forms, and product direction.
January-June 2025
The early public product formed around static assets, ads, marketplace work, story images, legal/privacy intake, OpenAI experiments, launch prep, editor tooling, censor workflows, SPA behavior, profiles, dark mode, and AI panel work.
July-August 2025
The app gained journal structure, token balances, token billing, per-view billing foundations, pricing tiers, image moderation, image descriptions, secure upload rules, AI chat billing, localization, and paid visibility checks.
September-October 2025
The product hardened around profile controls, analytics, ads, reporting, video, R2/media storage, local/production media separation, legal/contact form fixes, Stripe data, email reset, server startup tooling, SSRF safety, SEO, and mobile stability.
November-December 2025
The product added AI checker/review services, UTC timing, journal/admin improvements, page-view logging, paid email verification, overlays, FAQ, sitemap, hreflang, translation work, image descriptions, entity extraction, and public-body pipeline tooling.
January-May 2026
AngryPages evolved into a broader publishing system with Elle, paywall tooling, translation workflows, AVIF/WebP media, Tailwind migration, article frontpages, moderation review, badge safety, passphrases, press pages, gift cards, messages, landing pages, reader controls, maintenance notices, and Product Updates itself.
May tightened the public review notice, Pages navigation, image assets, reader prompts, and database/runtime stability.
April moved authentication, press pages, media recovery, admin performance, analytics, and Elle/tasking forward together.
March concentrated on the tagging stack, badge display safety, game systems, and local git hygiene.
February was the largest frontend and platform cleanup month, covering signup, tokens, layout migration, moderation review, article surfaces, CSP, and image behavior.
January opened 2026 with Elle/game experiments, story/paywall tooling, translation workflow, uptime/bugs SEO, and image variant repair.
December broadened the journal/product surface, overlays, translations, SEO, homepage design, image descriptions, and safer publication pipeline tooling.
November focused on token fulfillment, AI checker/review services, analytics middleware, journal/admin usability, resume intake, and UTC time handling.
October hardened login, legal/contact forms, billing, video playback, SSRF safety, email reset, server startup, CSS, SEO, and mobile layout.
September carried major public-profile, analytics, ad, storage, media, image, and card-design work.
August added early AI tagging and image-description systems while hardening forms, uploads, billing, localization, ads, and moderation.
July pushed the app toward launch with SPA/editor repairs, profile work, geo/IP setup, journal structure, token billing, and per-view billing foundations.
June was the first intense launch month: editor experiments, censor tools, SPA conversion, 2FA attempts, AI panel, dark mode, profile design, and Inker integration.
May added public intake basics and early product systems around privacy/legal forms, DMCA readiness, summaries, pricing, news, and AI panel work.
April moved the site from early working state into story images, OpenAI API experiments, and moderation false-positive fixes.
March contains a single checkpoint-style update in git history.
January added static assets and early app surfaces for ads, marketplace work, and story launch preparation.
December restarted the website code and established the early user, auth, and form direction.
September is the first recorded git month for the AngryPages webapp.