What Do You Build? Show Us Your Builder DNA
Welcome to Introductions → What I Build — the place to tell the community what kind of builder you are.
Not your job title.
Not your “professional personal brand statement” that sounds like it escaped from LinkedIn wearing expensive shoes.
Just the real answer:
What do you build?
What do you enjoy making?
What are you trying to get better at?
What kind of projects keep pulling you back in?
Some people build websites.
Some build apps.
Some build games.
Some build tools.
Some build brands.
Some build AI workflows.
Some build strange little side projects that started as “quick ideas” and are now demanding a domain name, logo, roadmap, and emotional support.
All welcome.
What this thread is for
Use this thread to share the kind of things you build.
Examples:
- Websites
- Landing pages
- Forums
- Apps
- SaaS tools
- AI workflows
- Automation systems
- Scripts
- Games
- Game worlds
- UI designs
- Logos
- Brands
- Digital products
- Content platforms
- Video platforms
- Music projects
- Open-source tools
- Templates
- Communities
- Weird experiments that may or may not become useful later
This is not a competition.
A tiny useful tool is still a build.
A small homepage is still a build.
A half-working prototype is still a build.
A project folder called:
new-idea-final-final-real
is concerning, but still probably a build.
Use this format
Copy this and fill it in:
I build:
My main project right now:
My favourite kind of thing to build:
Tools or platforms I use:
What I am learning:
What I want to build next:
What I need help with:
One builder habit I definitely have:
Example:
I build:
Websites, forums, tools, AI workflows, brands, and digital projects.
My main project right now:
Fyrbloc — a builder community for creators, coders, designers, indie developers, and digital makers.
My favourite kind of thing to build:
Useful online platforms with strong names, clear sections, and room to grow.
Tools or platforms I use:
Flarum, PHP, Laravel, CloudPanel, AI tools, SEO tools, design tools, and too many browser tabs.
What I am learning:
How to build better community structure and stronger starter content.
What I want to build next:
More useful resources, better templates, and cleaner member onboarding.
What I need help with:
Feedback, testing, useful links, and people sharing real build progress.
One builder habit I definitely have:
Saying “one last small change” and then starting a new side quest.
That is the kind of intro that helps people understand what you do.
Useful. Clear. Slightly suspicious. Perfect.
Builder types welcome here
The Website Builder
You make:
Homepages
Landing pages
Forums
Blogs
Directories
Communities
Business sites
Portfolio sites
You probably have strong opinions about spacing.
Possibly too strong.
The App Builder
You make:
Dashboards
Tools
SaaS ideas
Mobile apps
Web apps
User systems
Productivity things
You may have said:
I just need auth, settings, billing, profiles, notifications, uploads, admin, and maybe dark mode.
That is not “just.”
That is a small kingdom.
The Game Builder
You make:
Game mechanics
Maps
Characters
NPCs
Items
Lore
Combat systems
Worlds
You probably have one “small game idea” that secretly needs 400 systems and a soundtrack.
Respect.
Dangerous, but respect.
The AI Workflow Builder
You make:
Prompts
Agents
Automations
Research workflows
Writing systems
Image workflows
Code helper flows
Business processes
Your tabs probably include three AI tools, two docs pages, and one prompt called:
better-final-v2
Acceptable.
The Design & Branding Builder
You make:
Logos
Colour systems
UI ideas
Brand names
Typography
Mockups
Visual concepts
Landing page designs
You know the pain of changing a shade of orange by 3% and pretending it was essential.
Sometimes it was.
Probably.
The Script & Server Builder
You work with:
PHP
Laravel
Flarum
Node
MySQL
Nginx
CloudPanel
Composer
GitHub
APIs
Servers
Cron jobs
You have likely typed:
php artisan cache:clear
or:
php flarum cache:clear
with the energy of someone bargaining with a machine.
Not sure what you build yet?
That is fine.
You can say:
I am still figuring it out.
Or:
I want to build websites and learn better design.
Or:
I like tools, AI, and game ideas, but I am not sure where to focus yet.
That is a real answer.
Not everyone arrives with a finished direction.
Sometimes you find your builder identity by trying things, breaking things, fixing things, and realising:
Apparently I enjoy making complicated dashboards.
Life is strange.
Good replies to this thread
When someone shares what they build, reply with something useful.
Good replies:
That sounds interesting. What are you building first?
I use similar tools. Happy to compare notes.
That project idea sounds useful. Who is it for?
Nice stack. What part are you finding hardest?
I like the idea. Post a build log when you start.
Less useful replies:
That has already been done.
Wrong stack.
Nobody needs that.
Just use something else.
Those replies are not builder feedback.
They are tiny roadblocks wearing sunglasses.
What makes a good “What I Build” post?
A good post tells people:
What you make
Why you make it
What tools you use
What you are learning
What kind of help or connections you want
It does not need to be long.
Example short version:
I build:
Small websites, landing pages, and simple tools.
I use:
HTML, CSS, JavaScript, WordPress, and Figma.
I am learning:
Better UI design and basic backend development.
I want help with:
Feedback on layout, speed, and clearer homepage wording.
That is enough.
Clear posts make connection easier.
Mystery posts make people stare at the screen like it owes them an explanation.
Quick builder identity prompts
Use any of these:
I mostly build:
The project I always come back to:
The tool I use the most:
The thing I want to get better at:
The kind of project I want to launch one day:
The build I am most proud of:
The build I keep avoiding:
The builder problem I keep repeating:
Example:
The builder problem I keep repeating:
Making the logo before the project works.
Classic.
Painfully classic.
Keep it honest
You do not need to oversell yourself.
Good:
I am learning Laravel and building small practice apps.
Good:
I am new to design but trying to improve my landing pages.
Good:
I mostly use AI tools to help plan content and workflows, but I am still learning how to test outputs properly.
Not needed:
Visionary full-stack innovation architect disrupting the next generation of scalable digital ecosystems.
That sentence needs a chair and a glass of water.
Just say what you build.
Final note
This thread helps members find people with similar interests, tools, projects, and problems.
So share your builder DNA.
Big or small.
Beginner or experienced.
Polished or messy.
Website, app, game, AI workflow, script, brand, tool, or something strange with potential.
Tell us what you build.
Build. Share. Connect. Launch.
