r/ai_website_builder

Hey folks,

I recently bought a domain for my small business and now I want to set up professional email addresses for the team. I also want a simple website using the same domain.

We’re a small team of around 6 people, with two of us handling things like marketing and sales while the others handle operations and other areas.

I’m not very technical so I’m mainly looking for something that’s pretty straightforward.

For a team this small, which email hosting would you recommend? Is there a provider that’s particular easy to set up with an existing domain?

From beginning till end, how many steps are there and what are those? Someone please guide me.

I'm creating a website it completely confused :-)

I've seen people starting up websites and they think that the design and features are the main things. However there are a few other things that should really be sorted out first.

The most important factors from my point of view would be the goal of the website, target group, essential functionalities, budget, mobile compatible, SEO, safety measures, and how the site will be maintained after it is published.

It also appears crucial to establish the scope of the project from the outset, since extending the requirements later on will result in higher costs and longer development.

What do you consider the most significant thing to plan before embarking on a website project? Have you ever been involved with a website that failed due to a lack of planning?

I have developed a tool that exports complete framer website with all the assets animations and everything intact. No breakage. Everything runs as exactly as you made it on framer. You can download it and then host it wherever you want and that too for FREE.

If you want any framer website just DM me i will provide you with 1 ENTIRE FRAMER SITE for free, and if you would want more i will do that as well but it will be paid.

As i want to launch it online for everyone and i do not have money to host it.

So try for free and check for yourself. Its COMPLETLY FREE FOR THE FIRST DOWNLOAD JUST DM ME THE LINK AND I WILL GIVE YOU THE ENTIRE WEBSITE.

I'm a college student planning to build a portfolio website for myself, but I'm confused about how I should approach it.

Should I build it completely by myself, or should I use AI to build it for me?

Using AI would definitely save me a lot of time and could help me create a more polished website. But building it myself would give me more hands-on practice and a better understanding of how everything works.

So I'm stuck between:

AI → Faster development + better results
Build it myself → More practice + deeper understanding

What would be the better approach for a student who is still learning?

Should I build everything from scratch, use AI only for assistance, or take a hybrid approach? 🤔

Hey folks,

I’m starting a fashion boutique as a side business and want to keep things simple.

For now, I’ll mainly be taking orders through Instagram, with B2B inquiries coming in via LinkedIn and email. I’m currently using my personal Gmail, but I need two separate mailboxes, one for my side business and one for my main business.

I also want to secure my domain before someone else does and set up a professional business email instead of continuing to use my personal Gmail.

The problem is, I’m not very technical and have no idea where to start. I’m looking for something that’s affordable and easy to set up. Is this something I can do myself or is it worth hiring an IT person?

Hi is there a fast and cheap way to make websites using AI? I’m looking a cheap and effective way to make multiple websites.

https://preview.redd.it/t0i2jkmpktih1.png?width=1440&format=png&auto=webp&s=bd18e6e7fedd72f08e8e5abe1a340deb2d032dbf

I got the same Manus notice today as everyone else.

I actually like Manus a lot and don’t want to stop using it.

But I also never wanted Manus — or any AI builder — to become the only place where one of my production sites could actually live.

So alongside the official backup, I’m doing something I’ve already been doing with all of my vibe-coded projects:

building a clean, portable GitHub repository that another developer, AI platform, or future owner could actually understand and deploy.

There’s a big difference between:

“My project syncs to GitHub.”

and

“My GitHub repo is the documented source of truth for the project.”

A repo can technically exist in GitHub and still be a mess.

It might not explain:

• what the project actually does
• how the architecture is structured
• what depends on what
• which environment variables matter
• where the database lives
• what third-party services are connected
• what breaks if you change hosts
• how DNS is configured
• how to rebuild or deploy it elsewhere
• what SEO structure needs to stay intact

That is not real portability.

That is just code sitting somewhere else.

Years ago, getting a proper production repo, technical handoff package, architecture documentation, deployment notes, environment setup, dependency mapping and migration plan built correctly could easily become a serious five-figure development project.

AI makes that dramatically easier now.

But only if you know what standard to ask it to build toward.

This is the prompt I use.

One note before the prompt:

I intentionally use the phrase “potential acquisition.”

I’m not necessarily selling the project.

That wording is there because it changes how the AI approaches the task.

“Make me a README” gets you one level of documentation.

“Prepare this project for potential acquisition, migration and independent operation” tends to make the AI think much more seriously about:

due diligence, transferability, undocumented dependencies, ownership handoff, credentials, external accounts, technical debt, deployment continuity, operational risk and future maintainability.

That is the standard I want (modify if you already have a GitHub repository).

Here’s the prompt:

"It doesn’t appear that this project currently has a dedicated GitHub repository.
Please help me create a high-quality, expert-level PRD and a well-structured, portable GitHub repository that fully documents the project.
The goal is to make the project easy for another developer, technical team, or future owner to understand, maintain, migrate, and continue building without relying on undocumented knowledge.
The documentation and repository should clearly capture:
What has been built and the purpose of each major component
The current architecture, technology stack, dependencies, and integrations
Repository structure and how the codebase is organized
Environment variables, configuration requirements, and external services
Build, deployment, hosting, and DNS requirements
Data flows, APIs, databases, authentication, and third-party connections where applicable
Known limitations, technical debt, assumptions, and areas that may need future improvement
Recommended conventions for maintaining and scaling the project
Clear setup and handoff instructions for another developer or owner
This project is being prepared for potential acquisition, so portability and migration readiness are especially important.
Please thoroughly identify and document anything that could affect transferring the project to a new owner or environment, including hosting dependencies, domain and DNS configuration, deployment settings, credentials or secrets that must be recreated, external accounts, integrations, databases, storage, analytics, automation, APIs, and any platform-specific dependencies.
The final result should function as both a professional technical handoff package and a reliable blueprint for rebuilding, migrating, maintaining, or scaling the project independently."

Then I would have Manus build or clean the repo based on the current working project, not just assume an old GitHub sync captured everything correctly.

If you already have a GitHub sync, great.

But I’d still ask:

Could another AI system or developer open this repo tomorrow and actually understand how to run the project without guessing?

If not, I’d improve it now.

And obviously:

still run the official Manus backup.

This is not a replacement for that.

The difference is:

Backup = preserve what Manus gives you.

Portable repo = preserve your ability to leave Manus if you ever need to.

That distinction matters.

I’ve already been moving some of my own sites into another environment because I wanted a failsafe before this situation ever happened.

I’m currently using Lovable for that, but the specific destination is not really the point.

The point is that if your repo is clean and portable, another platform can understand what it is supposed to build.

That is what I mean by vibe architecture.

Vibe coding is:

>Build me a seo website.

Vibe architecture is:

>Here is the business model, entity structure, URL architecture, content model, integrations, SEO requirements, technical constraints, and portability requirements. Build the system around that.

That difference is why migration becomes much easier.

And for anyone who cares about SEO, there’s one more layer:

Google generally doesn’t care which hosting/build platform publishes the site; it cares about what remains crawlable, indexable, and consistent after the migration.

So if you move environments, the goal should not be:

“rebuild something that looks similar.”

The goal should be:

preserve the existing search architecture as close to 1:1 as possible.

Same URLs where appropriate.
Same content intent.
Same canonicals.
Same schema.
Same metadata.
Same redirects.
Same internal relationships.
Same important business facts.

A GitHub sync is not the same as a portable GitHub repository.

A backup protects your files.

A portable architecture protects your ability to operate.

Hope this helps at least a few people who woke up panicking today.

PS: Take advantage of Manus 1.6 been free credit wise.

Thinking of starting a series where I document building a web agency from scratch — finding clients, building websites, the failures, everything.
Would you guys actually be interested in watching something like this? Or is it too boring? 😅
Would love some honest opinions.
It will be a 90 day series on youtube
I am based in india

I think people are mixing up two very different things right now:

cheap production
and
cheap expertise

They are not the same.

I’ve been working in search for 15+ years, building websites for a long time, and working deeply with AI for the last several years.

At this point, with the workflows I’ve built, I can sometimes take a business from nothing to a functional website in 5–10 minutes.

And I don’t mean a generic AI template.

I mean a site with things like:

• clean architecture
• proper service targeting
• entity relationships
• metadata
• schema
• internal linking
• forms
• analytics foundations
• image naming
• existing asset reuse
• crawlable business facts
• external entity references
• a structure that can actually scale

If there’s an existing site, I can usually pull down the assets, rename and organize them, preserve what has value, and rebuild the architecture without starting from zero.

That speed is real.

But the mistake is assuming:

>

That’s not how expertise works.

AI compressed the execution time.

It did not compress the 15 years it took to learn:

• what pages should exist
• what pages should not exist
• how entities should relate
• what search intent belongs where
• how users should move through the site
• what technical mistakes will cause problems later
• what needs to be measurable
• and what “good” actually looks like

This is where I think the conversation around vibe coding is missing something.

Vibe coding is:

>

What I’m more interested in is vibe architecture.

That’s when you already understand the system:

the entity model, page hierarchy, service relationships, conversion paths, search intent, measurement, and business constraints

…and then you use AI to execute that system quickly.

That is a completely different skill.

The Picasso analogy gets used a lot, but it fits.

If someone can create something valuable in five minutes because they spent decades learning how to do it, the value didn’t disappear because the production time got shorter.

The same thing is happening with websites.

A good operator can now compress work that used to require:

a developer
a designer
a copywriter
a technical search specialist
an analytics person

into a much faster workflow.

That should make good websites more accessible.

But it doesn’t mean the expertise behind them became worthless.

The real question for a business owner is no longer:

“Who can build me the cheapest site?”

It’s:

“Who already knows what this site needs to do, and can use AI to get there efficiently?”

That’s where the value is moving.

Not into typing code.

Into judgment.