discuss.flarum.org No paid content found

A community section on a digital art and wallpaper site is the part of the platform where popularity is decided by members rather than by editors alone. On Skinbase, that takes the form of named rails — Rising Now, Trending This Week, Fresh Uploads, Community Favorites, and Hall of Fame — each measuring a different signal over a different time window. If you want to know which work other members are actually rewarding right now, the community rails answer that; if you want a curated or chronological view, the same site offers other entry points.

How community signals work on Skinbase

Skinbase describes itself as a home for "digital art, wallpapers, skins, and photography from a global creator community," and the homepage is organized around that idea. The rails are not interchangeable — each one tracks a distinct input:

The key mechanic is the medal. Skinbase's own description of Community Favorites says it "highlights the strongest 30-day medal signal," and each entry shows a count such as "30d medals: 10" or "30d medals: 5." That means medals are awarded by community members, accumulated per artwork, and then ranked over a rolling 30-day period. A piece with 10 medals in 30 days outranks one with 5, regardless of total views.

This is why the same artwork can appear in several rails at once. In the current homepage data, "The Nautilus of Atlantis" by Gregor Klevže appears in Rising Now, Trending This Week, and Fresh Uploads — it is both new and drawing attention. "My Art" by bagelriver leads Community Favorites with 10 medals while also sitting in Rising Now and Trending This Week. Overlap is a signal, not a glitch.

Community picks vs. editorial or algorithmic feeds

The distinction matters when you are deciding where to look:

• Community-driven rails (Community Favorites, Hall of Fame) reflect accumulated member medals. They reward work that other creators and visitors chose to recognize.
• Momentum rails (Rising Now, Trending This Week) blend recency with engagement — newer work can surface faster than in an all-time list.
• Chronological rails (Fresh Uploads) apply no popularity filter at all. This is the only place where a brand-new upload with zero medals can appear alongside established names.

If you want to find underrated work before it accumulates medals, Fresh Uploads is the right entry point. If you want social proof, Community Favorites is the most direct measure, because the medal count is displayed next to each item.

How to browse the community sections

1. Start on the homepage and scan the rail headings in order: Rising Now, Trending This Week, Fresh Uploads, Community Favorites, Hall of Fame.
2. Use the "See all →" link on any rail to expand it beyond the preview items.
3. Read the medal count on Community Favorites entries — it is the clearest numeric signal of community approval.
4. Cross-check an artwork across rails. Appearing in both Fresh Uploads and a momentum rail suggests it is new and being received well.
5. Open the artwork page to see the creator handle, which is shown under each title (for example, "Gregor Klevže / gregor" or "Paul R. Herold / mitsubishiman").

A practical example: if you are looking for a wallpaper and want something proven, open Community Favorites and pick from the top medal counts. If you want something nobody has seen yet, open Fresh Uploads and work down the list. Both are community surfaces, but they serve opposite goals.

How creators gain visibility

Visibility on Skinbase is cumulative and multi-path. A creator's work can enter the community's view through three separate routes:

• Recency — a new upload lands in Fresh Uploads immediately, with no threshold to clear.
• Momentum — if it collects medals quickly, it can move into Rising Now or Trending This Week.
• Durability — sustained medal accumulation over 30 days feeds Community Favorites, and exceptional long-term performance feeds the Hall of Fame.

The homepage data shows this is not theoretical. Gregor Klevže holds the majority of slots across Rising Now, Trending This Week, and Fresh Uploads, while Paul R. Herold and Hythem Khalifa also appear repeatedly. bagelriver's "My Art" tops Community Favorites with 10 medals. These are creators whose work is being surfaced by member activity, not by a single editorial decision.

One caveat worth noting: the medal counts shown are 30-day figures, so Community Favorites is a moving list. An artwork that leads today can drop off as its medals age out of the window, even if its all-time total keeps growing — which is what the Hall of Fame captures instead.

What the community section does not tell you

The community rails show popularity, not suitability. A high medal count does not indicate resolution, file format, license terms, or whether a wallpaper fits your screen. Those details live on the individual artwork page, not in the rail preview. Similarly, the presence of a "Pricing" link under the site's academy section means some parts of Skinbase may involve paid content, but the homepage evidence does not specify which features are free and which are not — treat that as something to check directly rather than assume.

If your goal is simply to understand the term: on a digital art and wallpaper site, "community" refers to the member-driven layer of discovery — the medals, favorites, and ranked rails that sit alongside chronological and editorial feeds, and that let visitors see what other people are choosing rather than only what the platform is promoting.

Flarum is a next-generation, open-source forum platform for running online discussions. It is a reasonable choice if you want a self-hosted community forum with a modern interface and an extension ecosystem, and you are comfortable installing and maintaining PHP-based software. If you need a fully managed, zero-maintenance service, or you are not prepared to track release candidates and extension compatibility, Flarum will require more hands-on work than a hosted alternative.

What Flarum actually is

Flarum is forum software: you install it on a server, and it provides the discussion structure — categories, topics, posts, users, and moderation tools. Its own community describes it as "the next-generation forum software that makes online discussion fun," which signals where it positions itself: the discussion experience and interface come first, rather than a legacy admin-and-thread model.

The practical implication is that Flarum is a platform you deploy and extend, not a service you sign up for. That shapes everything below — releases, extensions, and support all assume you are running your own instance.

How it differs from traditional forum software

The distinction that matters most when choosing is not a feature checklist but where the effort goes.

The trade-off is consistent: Flarum gives you a cleaner starting point and a strong extension culture, but you take on version-compatibility management. Traditional software often asks less of you in that respect because more is bundled.

Current release status and compatibility

The official community's discussion list shows Flarum's release activity directly, and it is worth reading before you commit to a version:

• Flarum 2.0.0-rc.8 — a release candidate, with an accompanying community vote on whether it is ready to become 2.0 GA (general availability).
• Flarum 1.8.20 — a maintenance release on the 1.x line.
• "Friends of Flarum — 2.0 Compatibility Progress" — a thread tracking how extensions are keeping up with 2.0.

Two conclusions follow. First, if you need maximum stability today, the 1.x maintenance line is the safer bet, because 2.0 is still in release-candidate status. Second, before installing any extension, check whether it supports your chosen version — the existence of a dedicated compatibility-progress thread tells you this is a real, ongoing concern rather than a hypothetical one.

Getting started: installation and extensions

Flarum is self-hosted software, so getting started means deploying it on your own server rather than creating an account. The community's own framing — "get support using and extending Flarum" — confirms both activities are expected of users.

A workable sequence:

1. Pick a version. Choose the 1.x maintenance line for stability, or a 2.0 release candidate if you want the newer line and accept pre-GA risk.
2. Install Flarum on a server that meets its requirements. (Consult the official installation documentation for the exact environment and commands — do not rely on secondhand instructions.)
3. Verify the base forum works before adding anything: create a category, post a topic, reply to it, and confirm the discussion renders as expected.
4. Add extensions one at a time, checking each against your Flarum version. The community maintains an Official Extension Discovery (Beta) listing, which is the natural starting point for finding extensions.
5. Re-test after each addition, so that if something breaks you know which extension caused it.

The most common sticking point is step 4: installing an extension built for a different Flarum version. The compatibility thread exists precisely because this happens often.

Where to get support

The official Flarum Community at discuss.flarum.org is the support venue, and its "All Discussions" area is where releases, extension announcements, and help threads live. It is also where you will find the extension-discovery listing and the compatibility tracking.

One practical note from the site itself: it states it is best viewed in a modern browser with JavaScript enabled, and it can show a loading error that a hard refresh may fix. If the community appears broken, try a hard refresh before assuming the site is down.

Beyond browsing, the community is where you would post your own question — but check the existing release and compatibility threads first, since version questions are recurring there.

What to decide before you start

• Choose Flarum if you want a self-hosted, extensible forum with a modern interface and you are willing to manage versions and extension compatibility yourself.
• Wait on 2.0 if you need production stability — the release-candidate status and the active compatibility-tracking thread both point to 1.x for now.
• Look elsewhere if you want a hosted service with no server maintenance, or if you would rather not track which extensions match which release.

The single most useful habit with Flarum is checking version compatibility before installing anything — releases, extensions, and support discussions all revolve around that one variable.

Modern forum software is a discussion platform built for today's web: mobile-ready, easy to use, and designed to keep conversations organized on a site you control rather than inside a social network's feed. NodeBB, the platform described on nodebb.org, presents itself this way — "next generation community forum software" that is "powerful, mobile-ready and easy to use" — and offers three deployment paths: open source self-hosting, one-click cloud hosting, and enterprise solutions. Choosing among them comes down to how much technical work you want to own, how fast you need to launch, and whether you need custom integration with existing infrastructure.

What makes forum software "modern"

The pitch on NodeBB's homepage frames the problem directly: if you want to engage followers "away from the noise and chaos of today's 'social' sites," you need your own platform for real conversations. Modern forum software keeps the structure of classic online communities — threaded, persistent, searchable discussions — while updating the delivery:

• Mobile-ready by default, so the community works on phones without a separate app.
• Easy to use, lowering the barrier for members who have never posted on a traditional forum.
• Self-contained community, so your discussions aren't ranked, interrupted, or algorithmically buried by an external platform.

NodeBB says it "powers thousands of community forums," and its showcase lists sites including MAXON Developers, sketchucation, Cloudron, ironheart.co.uk, and Basenji Forums — useful reference points if you want to see the software running in different contexts.

The three deployment options

NodeBB lays out three paths on its homepage, each aimed at a different kind of operator.

Self-hosted open source

Choose this if you have Node.js experience or a developer on hand and want full control of the server, data, and customization. The trade-off is that installation, upgrades, security, and uptime become your responsibility. NodeBB points this audience to its GitHub repository as the starting point.

Managed cloud hosting

Choose this if you want to launch quickly and would rather pay monthly than run infrastructure. NodeBB describes it as getting your forum "going right away" with monthly plans, and the site offers a free trial as the entry point. This is the middle path: less control than self-hosting, far less operational work.

Enterprise

Choose this if you're a large organization that needs the forum to fit into existing systems — NodeBB describes it as custom-built, high-performance, and integrated with your infrastructure, arranged by contacting the company directly. This is a conversation-and-quote path rather than a self-serve signup.

What to weigh before deciding

• Technical effort vs. control. Self-hosting maximizes control and minimizes recurring platform cost, but consumes developer time. Hosting flips that trade.
• Time to launch. Hosting and the free trial get you live fastest; self-hosting adds setup and configuration before your first member arrives.
• Integration needs. If the forum must talk to internal systems, enterprise is the option NodeBB positions for that; self-hosting gives you the code to build integrations yourself.
• Migration from an existing platform. If you're replacing an old forum, ask about the migration process early. NodeBB publishes customer accounts that speak to this — Jim Thompson, CTO of Netgate, calls the migration "surprisingly simple," and Christina Patchell of Maxon describes "a surprisingly painless migration process" with a reasonable quote and a plan. Treat these as vendor-published testimonials and verify scope for your own data.

Features to look for in any forum platform

NodeBB's own framing suggests a checklist you can apply to any candidate:

1. Mobile readiness — does it work well on phones without extra work?
2. Ease of use — can a non-technical member post, search, and follow a thread?
3. Engagement outcomes — Arthur Matczak, Software Engineer at Opera, is quoted saying user engagement "skyrocketed" after switching to NodeBB. Ask vendors for comparable evidence from communities like yours.
4. Support and responsiveness — Netgate's CTO notes the support team "is available whenever we run into trouble," and Maxon's contact highlights quick responses to challenges. Support terms matter more as your community grows.
5. Performance — Netgate's quote cites "excellent" performance; load-test expectations against your projected member count.

Steps to launch your community

1. Decide your deployment path using the table above — self-hosted, cloud, or enterprise.
2. Start the matching entry point: the GitHub repo for self-hosting, the free trial for hosting, or a contact request for enterprise.
3. Plan your migration if you're moving from an existing forum; get a written scope and timeline, as Maxon's account describes doing.
4. Configure for mobile and ease of use before inviting members, since those are the platform's stated strengths.
5. Track engagement after launch and compare against your old platform, the way Opera's team reports doing.

The short version: pick self-hosting for control, cloud hosting for speed, and enterprise for integration — then judge any option on mobile readiness, usability, support, and migration support.

Flarum Community (discuss.flarum.org) is the official community support forum for Flarum, the open-source forum software. It's where you ask questions, report problems, and get help from other users and extension developers. It is not a product homepage, a download page, or a login portal, and it is not a ticketing system — support there is community-driven, so the quality of the answer you get depends heavily on how you frame the question. Use it when you have a Flarum usage, installation, or extension-development problem and you're willing to search first and post details.

What the Flarum Community forum is (and isn't)

The board's front page is a running list of discussions. Alongside support threads you'll see release and announcement topics — for example "Flarum 2.0.0-rc.8 released," "Flarum 1.8.20 Maintenance Release," and "Introducing the Official Extension Discovery (Beta)" — plus extension threads such as "FoF Bookmarks," "Verified - User verification," and "Rank Banner - Group rank badges under usernames." That mix matters: some of your answers already exist as announcements rather than as replies to a question.

Before you post: search and self-check

Most "it's broken" reports are already answered. Do these first:

1. Search the forum for your exact error text and your extension name. The board is indexed, and version-specific issues usually have a thread.
2. Check the release announcements for your version. If you're on a release candidate or an older maintenance line, a known issue may already be documented.
3. Check extension compatibility threads. Flarum 2.0-era discussions (for example "Friends of Flarum — 2.0 Compatibility Progress") exist precisely because extensions lag behind core releases. If your problem started after a core upgrade, an incompatible extension is a prime suspect.
4. Reproduce it on a clean install if you can. This tells you whether the cause is core, an extension, or your environment.

If the search turns up nothing, you now have a much better question to ask.

What to include in a support post

A post that gets answered quickly contains, in roughly this order:

• Flarum version — exact, including any -rc or patch number.
• PHP version and how Flarum is installed — Composer, a one-click installer, Docker, shared hosting, etc.
• Full extension list with versions. Extension conflicts are the single most common cause of odd behavior.
• The exact error — copy the message and the stack trace, not a paraphrase. Use a code block so it stays readable.
• Steps to reproduce — numbered, starting from a known state.
• What you already tried — including the clean-install test above.
• Expected vs. actual behavior — one sentence each.

A vague "my forum is broken, help" post usually gets either silence or a request for the information you should have included. A post with the list above often gets a diagnosis in the first reply.

Where different kinds of questions belong

• Using Flarum (permissions, tags, notifications, theming): general support discussions on the board.
• Installing, upgrading, or migrating: support discussions, but state your hosting environment and whether you have shell/Composer access — the answer differs completely between a VPS and shared hosting.
• Extension development (writing or debugging your own extension): the development-oriented discussions, where other developers and extension authors are active.
• A specific third-party extension: post in that extension's own discussion thread. The author is the person most likely to know, and other users of the same extension will see it.
• Bug reports against Flarum core: the community board is where you confirm whether others see it too; reproducible core bugs are what actually get fixed.

Community support vs. paid support

The Flarum Community forum is free, public, and best-effort. Nobody is obligated to answer, and response times vary with how many people are active and how well you've described the problem. There is no service-level agreement, no private channel, and no guarantee that a maintainer will see your thread.

If you need a guaranteed response, a private channel, or help with a customized production forum, that is a different arrangement than what the community board provides — treat the board as peer help, not as a contract. For anything involving credentials, private data, or a security issue, don't post it publicly; look for the project's designated private reporting route instead.

Common pitfalls

• Posting the same question in multiple threads. It fragments the answers and gets ignored. One clear thread is better.
• Bumping repeatedly. Give it a day; if there's no reply, add new information (a log, a test result) rather than just "anyone?"
• Assuming a release candidate is stable. If you're running an -rc build, say so — advice for a stable release may not apply.
• Leaving the thread unresolved. If you fix it yourself, post what worked. That's what makes the next person's search succeed.