u/Made4uo

Hey everyone! I'm building Fugte and just added a live "Owners Were Here" section on our landing page to test out Fugte Form, which displays live form submissions.

If you're a founder or builder, feel free to add your website URL to the wall at fugte.com.

No signup or email required, just paste your link and tagline so incoming visitors can check out your project. Drop a comment here once you've submitted so I can upvote!

Hey everyone! I'm building Fugte and just added a live "Owners Were Here" section on our landing page to test out Fugte Form, which displays live form submissions.

If you're a founder or builder, feel free to add your website URL to the wall at fugte.com.

No signup or email required, just paste your link and tagline so incoming visitors can check out your project. Drop a comment here once you've submitted so I can upvote your product!

Got banned for spamming when my keyboard was stucked

I had a small founder moment today. I opened Stripe and realized someone had subscribed to my product a few days ago. At first, I thought it was my own test payment. Then I noticed my test payment was the refunded one. The successful payment was from an actual customer. It is only $4.99, so this is not some huge milestone, but it felt surprisingly meaningful. For the past few weeks, I have been wondering whether the product is confusing, whether the positioning is wrong, or whether I am solving a problem people do not care about.

The product lets people turn small website features into customizable embeddable widgets. For example, instead of handing someone raw HTML/CSS/JS for a calculator, form, banner, spinning wheel, pricing section, or interactive feature, you can expose editable settings like text, colors, links, images, and labels. Then a non-technical person can customize it through a form and embed it on their site without touching code.

I originally thought frontend developers would care, but after talking to some, I am not sure they do. They can already edit, host, and ship things themselves.

Now I am wondering if the better audience is

1. People using AI to generate website code but who do not know how to customize, host, or embed it
2. Freelancers/developers who want to hand off editable widgets to clients
3. No-code website owners who need custom interactive features their builder cannot do

Which of these is easiest to understand?

And which sounds like the strongest pain?

I’m building WebDYI, a tool that turns small HTML/CSS/JS components into customizable embeddable widgets.

​

The idea is a creator or developer builds a small widget — like a calculator, form, card, pricing section, spinning wheel, interactive banner, etc.

​

Then instead of handing over raw code, they expose editable settings like text, colors, images, links, labels, button text, spacing, font, icon

​

A client or non-technical user can customize those settings without touching the code, then embed the final widget on Canva, Notion, Shopify, WordPress, or any website with an iframe.

​

I’m looking for 5 beta creators who already make things like:

- HTML/CSS/JS components

- small website sections

- calculators/forms/cards

- AI-generated website features

- Canva/Notion/Shopify embeds

​

I’ll help turn one of your existing ideas/components into a customizable WebDYI template and feature it in the gallery.

​

This is not a paid job right now. I’m mainly looking for feedback from creators and trying to see if this workflow is useful.

Would anyone here be interested in testing it with me?

​

I’m building WebDYI, a tool that turns small HTML/CSS/JS features into customizable widgets people can embed on websites.

​

The audience I’m testing is:

- frontend creators

- no-code users

- people who get code from AI but don’t know how to reuse or edit it later

​

Can you tell me if the website explains the idea clearly in the first 5 seconds?

Do you understand what the product does, or is it confusing?

I’m experimenting with a workflow for small HTML/CSS/JS components.

​

The idea:

​

A frontend dev builds a component like a calculator, form, card, pricing section, spinning wheel, etc.

​

Then instead of handing over raw code, the dev exposes editable settings like:

- text

- colors

- images

- links

- labels

- button text

- spacing

​

The client or non-technical user can customize those settings without touching the code, then embed the result with an iframe.

​

I’m testing this with WebDYI and looking for 5 beta creators/devs who already make small components or AI-generated website features.

​

I’m not trying to sell anything right now. I’m trying to learn whether this workflow is actually useful for frontend devs, freelancers, or people making small website tools.

​

Would you use something like this for client work, or does it feel unnecessary?

I had a funny moment the other day.

​

I was working on my vibe-coded website and realized I needed a simple Featured On or Seen On section.

​

Nothing crazy. Just a section where I can show places where the site/product has been listed, shared, launched, or mentioned.

​

Normally, I would just ask Claude or ChatGPT to generate the HTML/CSS/JS, paste it into the site, and redeploy.

​

But then I realized this is one of those sections I’ll probably need to change later. Maybe I add more logos or change the title or update links.

​

And I really didn’t want to touch the code or redeploy the whole site every time I make a tiny update.

​

So I used WebDYI (Deploy Your Integration), which is a tool I’m building, to turn that section into an editable embeddable widget.

​

Now the actual section lives separately, and I can update the logo, text, links from settings instead of changing the website code again.

​

It made me realize that a lot of vibe-coded stuff is not really a “full app.”

​

Sometimes it’s just a small component you want to ship, reuse, edit, and embed somewhere.

​

Curious if anyone else runs into this. When you vibe-code small website components, do you usually deploy them as part of the full app, or do you ever wish they were just reusable editable embeds?

​

Note: im still fixing some UIs, so its not perfect yet but usable.

You build a website in Canva, Notion, Carrd, Shopify, or another no-code tool.

Then you realize something is missing. Maybe you need a custom calculator, a before/after slider, a quiz, an interactive card, a special form, or some small feature your builder does not support.

So you ask ChatGPT. ChatGPT gives you HTML, CSS, and JavaScript.

Then comes the real problem:

Where do you actually put the code?

That is the problem I’m trying to solve with WebDYI.com,

The idea is simple:

A developer or AI creates a small self-contained widget using HTML, CSS, and JavaScript. Then WebDYI turns the editable parts into simple settings, like text, colors, images, labels, buttons, and more.

So the non-technical user does not need to touch the code. They can customize the widget visually and embed it into their website with an iframe.

I’m still figuring out the positioning, so I’d love honest feedback below.

Would this be useful for no-code users, or does it still feel too technical because the widget starts with code?

Also, what kind of widget do you wish your no-code website builder had?

Disclosure: I’m building WebDYI so I’m using the promoted flair. I’m not posting this as a launch announcement. I’m trying to understand if this is a real pain for no-code users.

https://reddit.com/link/1u0m3tp/video/mn79foajs46h1/player

We have a first user who ask for a simple counter tracking widget. Widget created in few minutes and posted for free. That's how easy it was to create from idea to working widget. Make this yours today at webdyi.com

https://preview.redd.it/al5szdhp835h1.png?width=1761&format=png&auto=webp&s=85cc891623bd619b0ffa36253f2669210a7fd099