Posting Standards: Clear Posts Get Better Replies
Fyrbloc works best when posts are clear, useful, and easy to understand.
That does not mean every post needs to be perfect.
It means members should give enough context so other builders can actually help, reply, review, suggest, fix, or point things in the right direction without needing a crystal ball, detective hat, and three coffees.
This post explains how to write better posts on Fyrbloc.
The short version:
Clear title.
Right tag.
Useful context.
No secrets.
No spam.
Simple.
Annoyingly effective.
1. Use a clear title
A good title tells people what the post is about before they open it.
Good titles:
Need help fixing Flarum cache after extension install
Looking for feedback on my landing page layout
Useful free tools for checking website speed
My Laravel contact form is not sending emails
Not useful titles:
Help
Question
Broken
Please read
URGENT!!!
A vague title makes people guess.
Guessing is not a workflow.
It is a punishment.
2. Pick the closest tag
Use the tag that best matches your post.
Quick guide:
General → Quick Help:
Small problems, fast questions, sanity checks.
General → Community Chat:
Casual builder conversation.
General → Off Topic:
Random chat not directly about projects.
Build Logs:
Ongoing project progress.
Launches:
Live or finished projects.
Site Reviews:
Feedback on websites, apps, pages, and products.
Resources:
Useful tools, links, guides, templates, and references.
Marketplace:
Services, products, scripts, templates, and paid/free offers.
Support:
Help with Fyrbloc itself.
Announcements:
Official Fyrbloc updates, rules, and policies.
If the tag is slightly wrong, moderators may move it.
That is not a disaster.
That is tidying.
Digital sweeping.
3. Add enough context
The best posts explain:
What you are doing
What happened
What you expected
What you tried
What you need
Bad post:
My site broke. Any ideas?
Better post:
I installed a Flarum extension, then my admin page stopped loading.
What I changed:
Installed an extension using Composer.
What happened:
Admin page shows a blank screen.
What I expected:
Admin page should load normally.
What I tried:
Cleared cache and published assets.
Error:
Added screenshot below.
That gives people something useful to work with.
A good post saves everyone time.
Including you.
4. Include screenshots when useful
Screenshots help with:
- Layout problems
- Design feedback
- Error messages
- Mobile issues
- Broken images
- Weird spacing
- Button/menu problems
- Admin settings
- Anything visual
Good screenshot:
Shows the full issue
Includes enough page context
Does not expose private information
Is readable
Bad screenshot:
One tiny corner of the screen
No context
Blurry
Contains private keys
Somehow taken at a dramatic angle
Screenshots should help people understand the problem.
Not begin a treasure hunt.
5. Paste errors properly
If you have an error, include the exact error.
Good:
Error:
SQLSTATE[HY000] [1045] Access denied for user
Good:
Browser console:
Uncaught TypeError: Cannot read properties of undefined
Good:
Composer:
Your requirements could not be resolved to an installable set of packages.
Not good:
It said something about access or undefined or maybe cache.
That is not an error report.
That is a weather forecast for confusion.
6. Do not post private information
Never post:
- Passwords
- API keys
- SMTP passwords
- Database credentials
- Private tokens
- Payment details
- Customer data
- Server login details
- Private documents
- Full
.env files
- Full config files with secrets visible
Safe example:
DB_DATABASE=fyrbloc
DB_USERNAME=hidden
DB_PASSWORD=hidden
MAIL_PASSWORD=removed
API_KEY=redacted
Unsafe example:
Here is my full config with passwords included.
Do not do that.
The internet has teeth.
7. Explain links
If you share a link, explain what it is.
Good:
This is a free website speed testing tool. It shows load time, page size, waterfall requests, and Core Web Vitals.
Not good:
Check this
https://example.com
A mystery link is not helpful.
It is just a door with no label.
On the internet, unlabelled doors are suspicious by default.
8. No spam or low-effort promotion
Fyrbloc allows members to share work, tools, services, resources, and projects in the right areas.
But posts should be clear and useful.
Do not post:
- Repeated links
- Duplicate promotions
- Fake reviews
- Misleading offers
- Random affiliate spam
- Suspicious downloads
- “DM me” posts with no details
- AI-generated filler posts
- Marketplace posts with no price or explanation
Good promotion:
I made a Laravel starter template for small SaaS projects.
Includes:
Auth, dashboard, billing placeholder, settings page.
Price:
Free / Paid
Link:
...
Who it helps:
People starting Laravel projects quickly.
Bad promotion:
Best service guaranteed 100% success DM now.
That belongs in the bin.
Possibly two bins.
9. Use templates when possible
Templates make posts easier to read.
Quick Help template
What I am trying to do:
What happened:
What I expected:
What changed recently:
Error message:
Screenshot/link:
What I already tried:
Site Review template
Website/link:
What it is:
Who it is for:
What I want feedback on:
Desktop/mobile:
Known problems:
Build Log template
Project name:
What it does:
What changed:
What broke:
What I learned:
Next step:
Resource template
Resource name:
Link:
What it does:
Who it helps:
Free or paid:
Why it is useful:
Any warnings:
Marketplace template
What I am offering:
Price:
What is included:
What is not included:
Delivery method:
Support:
Refunds if relevant:
Contact method:
Templates are not strict homework.
They are shortcuts.
Useful shortcuts.
Not the suspicious kind that opens the wrong folder.
10. Reply with value
Good replies help the original poster move forward.
Useful replies:
Try clearing cache and publishing assets.
The issue looks like a missing permission on the storage folder.
The homepage is clear, but the main button needs stronger wording.
This tool is useful, but the free plan has limits.
Not useful replies:
Google it.
Bad idea.
This is easy.
Bro.
A reply should add something.
Even a short reply can be useful if it points in the right direction.
11. Be honest about your level
It is fine to say:
I am new to this.
I do not understand the error.
I copied the command but I am not sure what it does.
I need beginner-friendly advice.
That helps people answer at the right level.
Pretending to know everything usually creates more problems.
Especially with servers.
Servers can smell confidence.
Then they punish it.
12. Do not hijack threads
If someone posts about one issue, do not turn it into a different issue.
Example:
Original post:
Need help with Flarum email setup.
Thread hijack:
Also, what is the best laptop and should I use Laravel?
Start a new post instead.
Threads should stay readable.
One topic per thread keeps Fyrbloc cleaner.
Quick checklist before posting
Before posting, ask:
Is my title clear?
Did I choose the closest tag?
Did I explain the problem or idea?
Did I include the exact error if there is one?
Did I add screenshots if useful?
Did I remove private information?
Did I explain any links?
Is this useful for other people to read?
If yes, post it.
If no, fix the missing bit first.
Tiny improvement.
Big difference.
Examples of good Fyrbloc posts
Title:
Need help with Flarum thumbnail images not showing
Body:
I installed FoF Discussion Thumbnail and added an image at the top of my post, but the discussion list still shows the avatar.
What I tried:
Cleared cache, published assets, hard refreshed.
Question:
Does the image need to be uploaded locally, or can it use an external URL?
Title:
Feedback wanted on my SaaS landing page hero section
Body:
This is a landing page for a small booking tool.
I want feedback on:
Headline clarity
Button wording
Mobile layout
Trust signals
Known issue:
The pricing section is not finished yet.
Title:
Free tools for checking website speed before launch
Body:
Here are a few tools I use before launching a site, with notes on what each one is best for.
These are clear.
They invite useful replies.
They do not make members perform archaeology.
Final note
Fyrbloc should be easy to post in, but not messy.
You do not need to write perfect posts.
You just need to write posts that other people can understand and respond to.
Clear beats clever.
Context beats panic.
Useful beats loud.
Build. Explain. Post Clearly. Launch.
