{"id":1663,"date":"2026-03-12T02:19:32","date_gmt":"2026-03-12T02:19:32","guid":{"rendered":"https:\/\/www.woodcentral.com\/-\/peter\/?p=1663"},"modified":"2026-05-24T11:28:09","modified_gmt":"2026-05-24T11:28:09","slug":"from-punbb-to-forkbb-the-lightweight-forum-lineage","status":"publish","type":"post","link":"https:\/\/www.woodcentral.com\/-\/peter\/from-punbb-to-forkbb-the-lightweight-forum-lineage\/","title":{"rendered":"From PunBB to ForkBB: the lightweight forum lineage"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">The&nbsp;<strong>PunBB lineage<\/strong>&nbsp;is one of the more interesting evolutionary paths in forum software. Several modern lightweight forums ultimately trace back to&nbsp;<strong>PunBB<\/strong>, which was designed around one core idea:&nbsp;<strong>keep the code extremely small and readable<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Below is the simplified \u201cfamily tree.\u201d<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">The PunBB family tree<\/h1>\n\n\n\n<pre class=\"wp-block-code\"><code>PunBB (2002)\n   |\n   |-- FluxBB (2008)\n   |      |\n   |      \u2514\u2500\u2500 Flarum (2015+)\n   |\n   \u2514\u2500\u2500 ForkBB (2020s)\n<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">1. PunBB<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Created:<\/strong>&nbsp;2002<br><strong>Language:<\/strong>&nbsp;PHP<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">PunBB was revolutionary at the time because it deliberately rejected the growing complexity of forums like phpBB.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Design principles:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>very\u00a0<strong>small codebase<\/strong><\/li>\n\n\n\n<li>minimal database queries<\/li>\n\n\n\n<li>fast page loads<\/li>\n\n\n\n<li>clean PHP code<\/li>\n\n\n\n<li>simple moderation tools.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">PunBB became popular among developers because it was&nbsp;<strong>easy to read and modify<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, development slowed after the project changed ownership.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">2. FluxBB<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">FluxBB started in&nbsp;<strong>2008<\/strong>&nbsp;when developers forked PunBB after dissatisfaction with its direction.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Goals:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>continue PunBB\u2019s\u00a0<strong>minimalist philosophy<\/strong><\/li>\n\n\n\n<li>modernize the code<\/li>\n\n\n\n<li>keep compatibility with extensions.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">FluxBB remained small and fast, but development eventually slowed as well.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">3. Flarum<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">Flarum took a&nbsp;<strong>very different path<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Created by developers from FluxBB and esoTalk.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Major changes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>modern JavaScript interface<\/li>\n\n\n\n<li>infinite scrolling discussions<\/li>\n\n\n\n<li>extension-based architecture<\/li>\n\n\n\n<li>responsive design.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">While still lightweight compared to many platforms, Flarum is&nbsp;<strong>far larger and more complex<\/strong>&nbsp;than PunBB.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You could think of it as:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>PunBB philosophy + modern web app design\n<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">4. ForkBB<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">ForkBB is closer to the&nbsp;<strong>original PunBB vision<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It is essentially:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>a\u00a0<strong>modernized PunBB<\/strong><\/li>\n\n\n\n<li>updated PHP compatibility<\/li>\n\n\n\n<li>improved security<\/li>\n\n\n\n<li>cleaned-up codebase<\/li>\n\n\n\n<li>minimal bloat.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">It keeps the&nbsp;<strong>traditional forum layout and simplicity<\/strong>.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">Why the PunBB lineage matters<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">PunBB established a design philosophy that many developers still admire:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>small code<\/li>\n\n\n\n<li>readable architecture<\/li>\n\n\n\n<li>minimal dependencies<\/li>\n\n\n\n<li>high performance.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">In contrast, modern platforms like&nbsp;<strong>Discourse<\/strong>&nbsp;emphasize:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>real-time UI<\/li>\n\n\n\n<li>complex moderation systems<\/li>\n\n\n\n<li>social-media style interaction.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">So the ecosystem split into two philosophies:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Classic forum model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>ForkBB<\/li>\n\n\n\n<li>FluxBB<\/li>\n\n\n\n<li>MyBB<\/li>\n\n\n\n<li>phpBB<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Modern discussion platforms<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Discourse<\/li>\n\n\n\n<li>Flarum<\/li>\n\n\n\n<li>NodeBB.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">One interesting observation<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">Because most communities moved to&nbsp;<strong>social platforms or Reddit-style systems<\/strong>,&nbsp;<strong>very few developers now build classic forums<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That means projects like&nbsp;<strong>ForkBB<\/strong>&nbsp;are actually preserving a&nbsp;<strong>piece of early web architecture<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Given the work we\u2019ve done rebuilding the WoodCentral forums, we\u2019re essentially maintaining one of the&nbsp;<strong>last examples of that classic forum ecosystem still actively used<\/strong>.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p class=\"wp-block-paragraph\">The difference in&nbsp;<strong>codebase size and system complexity<\/strong>&nbsp;among forum platforms is dramatic. Early forums were essentially&nbsp;<strong>structured message boards<\/strong>, while modern platforms are closer to&nbsp;<strong>full social web applications<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Below is a rough comparison of the major systems.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">Approximate forum software codebase sizes<\/h1>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Platform<\/th><th>Approximate size<\/th><th>Stack<\/th><th>Complexity<\/th><\/tr><\/thead><tbody><tr><td>PunBB<\/td><td>~8k\u201310k lines<\/td><td>PHP<\/td><td>extremely small<\/td><\/tr><tr><td>FluxBB<\/td><td>~12k\u201315k<\/td><td>PHP<\/td><td>small<\/td><\/tr><tr><td>ForkBB<\/td><td>~15k\u201320k<\/td><td>PHP<\/td><td>small<\/td><\/tr><tr><td>My Little Forum<\/td><td>~15k\u201320k<\/td><td>PHP<\/td><td>small<\/td><\/tr><tr><td>Simple Machines Forum<\/td><td>~80k\u2013120k<\/td><td>PHP<\/td><td>medium<\/td><\/tr><tr><td>MyBB<\/td><td>~150k<\/td><td>PHP<\/td><td>medium<\/td><\/tr><tr><td>phpBB<\/td><td>~200k+<\/td><td>PHP<\/td><td>large<\/td><\/tr><tr><td>Flarum<\/td><td>~250k+<\/td><td>PHP + JS<\/td><td>large<\/td><\/tr><tr><td>NodeBB<\/td><td>~300k+<\/td><td>Node.js<\/td><td>large<\/td><\/tr><tr><td>Discourse<\/td><td>~500k+<\/td><td>Ruby + JS<\/td><td>very large<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><em>(Counts include only core code, not plugins or dependencies.)<\/em><\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">Why early forums were so small<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">Classic forums like&nbsp;<strong>PunBB<\/strong>&nbsp;were designed around a very simple model:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Core functions:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>user registration<\/li>\n\n\n\n<li>topics<\/li>\n\n\n\n<li>posts<\/li>\n\n\n\n<li>moderation<\/li>\n\n\n\n<li>search.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">That\u2019s basically it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pages were rendered server-side and delivered as simple HTML.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">Why modern forums are huge<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">Platforms like&nbsp;<strong>Discourse<\/strong>&nbsp;and&nbsp;<strong>Flarum<\/strong>&nbsp;add many layers:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Real-time interaction<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>WebSockets<\/li>\n\n\n\n<li>live notifications<\/li>\n\n\n\n<li>typing indicators.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Social features<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>likes \/ reactions<\/li>\n\n\n\n<li>badges<\/li>\n\n\n\n<li>trust levels<\/li>\n\n\n\n<li>recommendation algorithms.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Moderation systems<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>spam filtering<\/li>\n\n\n\n<li>user reputation scoring<\/li>\n\n\n\n<li>AI moderation.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Web-app infrastructure<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>REST APIs<\/li>\n\n\n\n<li>front-end frameworks<\/li>\n\n\n\n<li>background workers<\/li>\n\n\n\n<li>caching layers.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">Performance implications<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">The difference in&nbsp;<strong>resource requirements<\/strong>&nbsp;is significant.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Platform type<\/th><th>Typical RAM<\/th><\/tr><\/thead><tbody><tr><td>Classic PHP forum<\/td><td>50\u2013200 MB<\/td><\/tr><tr><td>Mid-size PHP forum<\/td><td>200\u2013500 MB<\/td><\/tr><tr><td>Modern JS forum<\/td><td>500 MB\u20131 GB<\/td><\/tr><tr><td>Discourse-style<\/td><td>1\u20132 GB+<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">This is why lightweight forums still appeal to people running&nbsp;<strong>small or independent communities<\/strong>.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">A philosophical difference<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">The split in forum software today really reflects two different visions of online discussion.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Classic forum philosophy<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>chronological discussion<\/li>\n\n\n\n<li>structured threads<\/li>\n\n\n\n<li>minimal interface<\/li>\n\n\n\n<li>long-form posts.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Examples:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>ForkBB<\/li>\n\n\n\n<li>FluxBB<\/li>\n\n\n\n<li>My Little Forum.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Modern discussion platform<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>engagement mechanics<\/li>\n\n\n\n<li>notifications<\/li>\n\n\n\n<li>social media dynamics.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Examples:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Discourse<\/li>\n\n\n\n<li>NodeBB.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p class=\"wp-block-paragraph\">Given our situation running&nbsp;<strong>WoodCentral<\/strong>, our choice of&nbsp;<strong>ForkBB<\/strong>&nbsp;is actually very consistent with the site\u2019s character:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>long technical discussions<\/li>\n\n\n\n<li>archival value of threads<\/li>\n\n\n\n<li>low infrastructure overhead.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Many communities that tried migrating to systems like Discourse later discovered that the&nbsp;<strong>conversation style changes dramatically<\/strong>.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p class=\"wp-block-paragraph\">One interesting thing we might appreciate given the work rebuilding WoodCentral:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Some developers today are actually&nbsp;<strong>returning to ultra-simple forum designs<\/strong>, because communities discovered that&nbsp;<strong>large social-style platforms often weaken technical discussions<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A few new projects are experimenting with&nbsp;<strong>static-file forums and flat-file discussion systems<\/strong>&nbsp;(no SQL database at all), which is a very different direction.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A small but interesting movement in the last few years has been toward&nbsp;<strong>database-free discussion systems<\/strong>. These systems try to reduce infrastructure complexity by storing content in&nbsp;<strong>flat files, Git repositories, or static site formats<\/strong>&nbsp;instead of SQL databases.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For someone who prefers&nbsp;<strong>simple infrastructure (logs, flat files, minimal dependencies)<\/strong>, these designs can be surprisingly elegant.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Below are three notable examples.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">Flat-file \/ database-free discussion systems<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">Isso<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Language:<\/strong>&nbsp;Python<br><strong>Storage:<\/strong>&nbsp;SQLite (sometimes flat-file mode)<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Isso is primarily a&nbsp;<strong>comment system<\/strong>&nbsp;rather than a full forum, but it\u2019s often used to add discussion threads to static sites.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Characteristics:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>extremely small footprint<\/li>\n\n\n\n<li>self-hosted alternative to Disqus<\/li>\n\n\n\n<li>stores comments locally<\/li>\n\n\n\n<li>minimal JavaScript<\/li>\n\n\n\n<li>REST API.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Because it uses SQLite by default, deployment is very simple.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Many static site users pair it with:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Hugo<\/li>\n\n\n\n<li>Jekyll<\/li>\n\n\n\n<li>other static generators.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Remark42<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Language:<\/strong>&nbsp;Go<br><strong>Storage:<\/strong>&nbsp;BoltDB \/ files<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Features:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>fast Go server<\/li>\n\n\n\n<li>simple moderation tools<\/li>\n\n\n\n<li>email notifications<\/li>\n\n\n\n<li>OAuth login options.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This system is also designed primarily for&nbsp;<strong>site comments<\/strong>, but communities sometimes use it as a lightweight discussion platform.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Giscus<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Language:<\/strong>&nbsp;JavaScript<br><strong>Storage:<\/strong>&nbsp;GitHub Discussions<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This one is unusual because the discussion storage is actually&nbsp;<strong>GitHub itself<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">How it works:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>posts are stored as GitHub Discussions<\/li>\n\n\n\n<li>website embeds a JavaScript widget<\/li>\n\n\n\n<li>comments sync with GitHub threads.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Advantages:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>no server needed<\/li>\n\n\n\n<li>moderation through GitHub tools<\/li>\n\n\n\n<li>versioned history.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Disadvantage:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>requires GitHub accounts.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">A more radical approach: Git-based forums<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">Some projects store discussions directly in&nbsp;<strong>Git repositories<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Examples include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>GitHub Discussions<\/li>\n\n\n\n<li>GitLab issues<\/li>\n\n\n\n<li>static forum generators that convert Markdown threads into web pages.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">In these systems:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>post = markdown file\nthread = directory\nforum = repository\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This approach gives:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>version history<\/li>\n\n\n\n<li>distributed backups<\/li>\n\n\n\n<li>easy static publishing.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">Why developers are experimenting with these<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">The motivation is similar to things you\u2019ve mentioned about your own systems:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Advantages<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>very small infrastructure<\/li>\n\n\n\n<li>easy backups<\/li>\n\n\n\n<li>fewer security issues<\/li>\n\n\n\n<li>minimal server resources.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Disadvantages<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>limited moderation tools<\/li>\n\n\n\n<li>scaling challenges<\/li>\n\n\n\n<li>fewer forum-style features.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">A direction that might be of interest<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">There\u2019s also a&nbsp;<strong>hybrid model<\/strong>&nbsp;emerging:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>forum software\n     +\nstatic archive pages\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Some communities run a dynamic forum but periodically generate&nbsp;<strong>static HTML archives of threads<\/strong>&nbsp;for speed and preservation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Given the amount of&nbsp;<strong>legacy content migrated (hundreds of thousands of posts)<\/strong>&nbsp;on WoodCentral, that approach can dramatically improve:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>search indexing<\/li>\n\n\n\n<li>long-term preservation<\/li>\n\n\n\n<li>page speed.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>The&nbsp;PunBB lineage&nbsp;is one of the more interesting evolutionary paths in forum software. Several modern lightweight forums ultimately trace back to&nbsp;PunBB, which was designed around one core idea:&nbsp;keep the code extremely small and readable. Below is the simplified \u201cfamily tree.\u201d The PunBB family tree 1. PunBB Created:&nbsp;2002Language:&nbsp;PHP PunBB was revolutionary at the time because it deliberately &#8230; <a title=\"From PunBB to ForkBB: the lightweight forum lineage\" class=\"read-more\" href=\"https:\/\/www.woodcentral.com\/-\/peter\/from-punbb-to-forkbb-the-lightweight-forum-lineage\/\" aria-label=\"Read more about From PunBB to ForkBB: the lightweight forum lineage\">Read more<\/a><\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-1663","post","type-post","status-publish","format-standard","hentry","category-technology"],"_links":{"self":[{"href":"https:\/\/www.woodcentral.com\/-\/peter\/wp-json\/wp\/v2\/posts\/1663","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.woodcentral.com\/-\/peter\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.woodcentral.com\/-\/peter\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.woodcentral.com\/-\/peter\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/www.woodcentral.com\/-\/peter\/wp-json\/wp\/v2\/comments?post=1663"}],"version-history":[{"count":0,"href":"https:\/\/www.woodcentral.com\/-\/peter\/wp-json\/wp\/v2\/posts\/1663\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.woodcentral.com\/-\/peter\/wp-json\/wp\/v2\/media?parent=1663"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.woodcentral.com\/-\/peter\/wp-json\/wp\/v2\/categories?post=1663"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.woodcentral.com\/-\/peter\/wp-json\/wp\/v2\/tags?post=1663"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}