Fyrbloc Starter Guide: Where New Members Should Begin
Welcome to Fyrbloc — a builder community for people making websites, apps, tools, games, scripts, AI workflows, brands, communities, and digital projects.
This guide is here to help new members understand where to start, what to post, and how to get useful replies without wandering around the forum like someone looking for the right cable in a drawer full of lies.
Fyrbloc is built around a simple idea:
Build. Break. Fix. Launch.
That means you do not need to arrive with a perfect project.
You can arrive with an idea, a half-built thing, a bug, a question, a messy homepage, a launch plan, a useful tool, or a project that currently looks at you with disrespect.
That is allowed.
Start here
If you are new, these are the best places to begin.
1. Introduce yourself
Use Introductions if you want to say who you are, what you build, what you are learning, and what kind of projects you are working on.
Good intro format:
Name:
What I build:
Current project:
Skills:
What I want help with:
One thing I am learning:
You do not need a perfect intro.
A simple one is fine.
Nobody is expecting a TED Talk with lighting and a dramatic walk-on.
2. Ask quick questions
Use General → Quick Help when you need a fast answer, sanity check, or small bit of help.
Good for:
- Small bugs
- Setup problems
- “Is this normal?” questions
- CSS issues
- Hosting questions
- Flarum, Laravel, PHP, JavaScript, DNS, email, or CloudPanel help
- Tool recommendations
- Error messages
- Quick checks before you break something important
Good quick-help format:
What I am trying to do:
What happened:
What I expected:
What changed recently:
Error message:
Screenshot/link:
What I already tried:
The more context you give, the faster people can help.
A post that says:
help site broke
is technically a message.
But it is also a fog machine.
Share what you are building
3. Use Build Logs for progress
Use Build Logs when you want to show progress on a project over time.
Good for:
- Websites
- Apps
- Games
- Forums
- Tools
- Scripts
- Brands
- AI workflows
- Digital products
- Side projects
Build log format:
Project name:
What it does:
What I worked on:
What changed:
What broke:
What I need help with:
Next step:
Build logs do not need to be polished.
They are for progress.
A real build log might look like:
Today I fixed signup, changed the homepage, broke the menu, fixed the menu, and now I trust nothing.
That is valid.
That is building.
4. Use Launches when something is ready
Use Launches when your project is live, released, published, or ready for people to see.
Good launch post format:
Project name:
Link:
What it does:
Who it is for:
What is finished:
What feedback I want:
What is next:
A launch does not need to be perfect.
It should be clear enough for people to understand what it is and what kind of feedback you want.
Perfect launches are rare.
Most launches are held together by effort, hope, and one final cache clear.
Get feedback
5. Use Site Reviews for websites and project pages
Use Site Reviews if you want feedback on:
- Homepages
- Landing pages
- Forums
- Apps
- Tool pages
- Portfolio pages
- Product pages
- Community pages
- Game pages
Good review request format:
Website/link:
What it is:
Who it is for:
What I want feedback on:
Desktop/mobile:
Known problems:
Useful feedback is specific.
Better than:
Thoughts?
Try:
Can you check if the homepage explains the project clearly and whether the call-to-action makes sense on mobile?
That gives people a target.
Without a target, feedback becomes vague fog with opinions in it.
Share useful stuff
6. Use Resources for tools, links, guides, and references
Use Resources when sharing something useful for other builders.
Good resources include:
- Developer tools
- SEO tools
- AI tools
- Design tools
- Hosting tools
- Video tools
- Free assets
- Useful websites
- Learning links
- Templates
- Checklists
- Scripts
- Guides
Good resource format:
Resource name:
Link:
What it does:
Who it helps:
Free or paid:
Why it is useful:
Any warnings:
Please explain why the resource is useful.
A random link with no context is just digital confetti.
Nobody wants to clean that up.
Chat with the community
7. Use Community Chat for casual builder talk
Use General → Community Chat for relaxed posts about building, progress, small wins, funny bugs, project thoughts, motivation, and builder life.
Good for:
- Tiny wins
- Builder confessions
- Open tab chaos
- Almost-launched projects
- Random builder chat
- Things you are working on today
- Funny project moments
Example:
Today I fixed:
Today I broke:
Today I learned:
Tomorrow I will:
Community Chat is the less formal side of building.
Still useful.
Just with more jokes about CSS.
CSS deserves it.
8. Use Off Topic for everything else
Use General → Off Topic for casual topics that are not really about projects.
Good for:
- Films
- Shows
- Games
- Music
- Snacks
- Desk setups
- Nostalgia
- Random recommendations
- Side quests
- Weird internet discoveries
Off Topic is the side room.
Not everything needs to be a bug report.
Sometimes people just need to say:
I opened my laptop to work and somehow watched three videos about chair ergonomics.
Understandable.
Basic posting rules
To keep Fyrbloc useful, try to:
- Add context
- Use the closest tag
- Keep titles clear
- Share screenshots when useful
- Explain what you already tried
- Be respectful
- Give useful replies
- Avoid spam
- Hide private information
- Do not post passwords, API keys, tokens, or private customer data
Good posts help people help you.
Bad posts make everyone guess.
Guessing is expensive and usually wrong.
Before posting technical info
Never post private details like:
Passwords
API keys
SMTP passwords
Database credentials
Private tokens
Server login details
Customer/user data
Full private config files
Safe example:
DB_PASSWORD=hidden
MAIL_PASSWORD=removed
API_KEY=redacted
Good builders redact.
The internet does not need your secrets.
The internet already has enough problems.
Best first steps for new members
If you are new, do this:
1. Read the Community Guidelines
2. Update your profile
3. Introduce yourself
4. Reply to one Community Chat thread
5. Share a project, question, resource, or tiny win
That is enough.
You do not need to understand every section on day one.
Start small.
Post clearly.
Build from there.
Quick map of Fyrbloc
Announcements:
Official Fyrbloc updates and news.
Introductions:
New member intros and builder profiles.
Build Logs:
Ongoing project progress.
Launches:
Finished or live projects.
General:
Quick help, community chat, and off-topic talk.
Resources:
Useful tools, links, guides, and references.
Site Reviews:
Feedback on websites, apps, pages, and products.
Web Dev:
Code, hosting, servers, bugs, frameworks, and setup.
AI Tools:
AI workflows, prompts, APIs, and automation.
Game Dev:
Games, mechanics, worlds, engines, and dev progress.
Design & Branding:
Logos, UI, UX, colours, typography, and visuals.
GitHub Scripts:
Repos, installs, open-source scripts, and setup help.
Marketplace:
Services, templates, scripts, assets, and digital products.
Support:
Help with Fyrbloc itself.
Final note
Fyrbloc is here for builders who are actually making things.
Not everything has to be finished.
Not every question has to be advanced.
Not every project has to be huge.
Not every update has to sound like a press release.
Show the work.
Ask clearly.
Share useful things.
Help when you can.
Keep building.
Build. Break. Fix. Launch.
