Stop Regenerating the Whole Post. Just Fix the One Block That's Wrong.

twRty Connect — Thu, 18 Jun 2026 03:18:19 +0000

There's a frustrating pattern that almost everyone hits when they start using AI for writing.

The AI generates a solid post. Most of it is good. Then you hit one section that's off — the tone is wrong, the explanation is weak, or the intro doesn't land. And the instinct is to hit regenerate and start over.

Don't.

Regenerating the whole post to fix one section is like deleting your entire codebase because one function has a bug. It's wasteful, it loses all the good parts, and the new version often introduces different problems while fixing the original one.

At twRty Software Services, we built Blogboat around a different editing model — and this is the most important design decision we made.

Every post is a set of independent blocks

In Blogboat, a blog post isn't a single document. It's a collection of blocks — each section, each heading, each paragraph group is its own editable unit.

When you generate a post, you get the full article. But each block can be targeted individually. If the intro isn't working, you select that block and use AI to rewrite, expand, shorten, or change the tone — just for that block. The rest of the post doesn't move.

This matters for a few reasons:

You keep what's working. The three sections that are well-written, specific, and accurate stay exactly as they are. You don't risk losing them in a regeneration.

You spend your time where it matters. A 700-word post might have one section that needs work. Block editing means you spend 5 minutes on that section instead of 20 minutes reviewing a completely regenerated draft.

The editing feels like writing, not prompting. Instead of crafting a new prompt that tries to get the whole post right again, you interact directly with the content. Select a block, choose an action, review the result.

What block-level AI actions actually look like

In Blogboat's editor, when you select a block you get a set of options:

Rewrite — completely replace the block with a fresh version at the same length and tone
Expand — add more depth, detail, or examples to the block
Shorten — tighten the block without losing the core point
Change tone — shift the block from professional to casual, from conversational to persuasive
AI Suggestion — get a suggested improvement with an Accept/Dismiss option before committing

Each action operates on that block only. The result is shown as a diff-style suggestion — you can accept it or dismiss and try again. You stay in control at every step.

Why this matters for the "80/20" problem in AI writing

Most AI writing tools give you a first draft that's roughly 80% good. The remaining 20% — voice, specificity, accuracy in your particular niche — requires human input.

The problem with whole-post regeneration is that it destroys the 80% to take another swing at the 20%. You're not editing anymore, you're starting over.

Block editing solves this by letting you surgically improve the 20% while preserving the 80%. The posts that come out of this process are faster to produce and higher quality than either pure AI output or full manual editing.

Try it

Write a post, generate it, then identify the one section that doesn't feel right. Edit just that block. See how much faster the final version comes together.

Blogboat is free to start:

🌐 twrty.org/blogboat
📱 iOS · Android

See block editing in action:

Built by the team at twRty Software Services. We make software that solves real workflow problems — Blogboat is our flagship product.

Your Readers Aren't All English Speakers. Here's How to Reach the Rest.

twRty Connect — Thu, 18 Jun 2026 03:10:46 +0000

Think about the last blog post you published.

Who read it?

If you only published in English, you already filtered out roughly 75% of the world's internet users. Spanish speakers alone number over 500 million online. Hindi, Portuguese, French, Arabic, German — these aren't niche markets. They're enormous audiences that most content creators completely ignore, not out of intention, but because the tooling made it hard.

At twRty Software Services, we built multilingual publishing into Blogboat from day one. Here's why it matters and how it works in practice.

The language barrier most creators don't see

The assumption most English-speaking creators operate under is this: "My audience is global, and global means English."

That was true once. It isn't anymore.

Mobile internet access has brought hundreds of millions of new readers online in the last decade — in India, Latin America, Southeast Asia, the Middle East, and across Africa. Most of them prefer to read in their native language. Many of them will scroll past excellent English content simply because it isn't in a language they're comfortable with.

Content that's readable in someone's native language isn't just more accessible — it converts better, earns more trust, and builds deeper audience loyalty. Localised content consistently outperforms translated content, which in turn consistently outperforms English-only content in non-English-speaking markets.

This isn't an opinion. It's a pattern that global brands figured out years ago and that independent creators are only starting to catch up with.

What "multilingual publishing" usually looks like (and why it fails)

Most creators who try to publish in multiple languages hit the same wall:

Option 1 — Write it twice. Write the post in English, then write it again in Spanish. This is twice the work and rarely happens consistently.

Option 2 — Machine translate it. Run the English version through a translation tool, paste the output into a new post. This produces content that reads like a machine translated it — awkward, sometimes inaccurate, often embarrassing.

Option 3 — Hire a translator. Expensive, slow, doesn't scale for a solo creator or small team publishing regularly.

None of these options are sustainable. So most creators publish in English and quietly give up on reaching non-English audiences.

How we approached it in Blogboat

Blogboat lets you generate, edit, and publish your blog in the language you choose — without leaving the app.

You pick the language before you generate. The AI writes in that language natively, not through a translation layer. A Spanish post is written as Spanish from the start — not translated from an English draft. The structure, phrasing, and flow are native to the language, not artifacts of translation.

Supported languages include English, Hindi, Spanish, French, German, Portuguese, Arabic (with right-to-left layout), Japanese, Chinese (Simplified), Korean, Italian, Dutch, Russian, Turkish, Polish, and Swedish.

When you're ready to publish, your content goes to the same 15+ platforms in the language you wrote it — no extra steps, no separate workflow.

A practical use case

Imagine a developer in India who writes technical tutorials. Their primary audience is English-speaking developers. But they also have a significant potential readership in Hindi — developers who would genuinely benefit from their content if it were available in their preferred language.

With Blogboat, they can generate the same tutorial topic in Hindi, review it, edit the blocks that need native-speaker refinement, and publish it. Same workflow, same tools, different language. One extra hour a week to potentially double their audience reach.

This is the kind of leverage that was previously only available to teams with translation budgets.

Who this is for

Multilingual publishing in Blogboat is particularly useful for:

Developers and technical writers with global audiences who want to reach non-English-speaking communities
Indie founders and marketers expanding into new regional markets
Content creators who grew up bilingual and want to publish authentically in both languages
Educators and coaches serving students in specific language communities

Try it

Blogboat is free to start. When you generate your next post, try switching the language and see what comes back.

🌐 twrty.org/blogboat
📱 iOS · Android

twRty Software Services builds web and mobile products. Blogboat is our flagship — an AI writing studio that writes, edits, and publishes to 15+ platforms in your language.

DEV Community: twRty Software Services

Stop Regenerating the Whole Post. Just Fix the One Block That's Wrong.

Every post is a set of independent blocks

What block-level AI actions actually look like

Why this matters for the "80/20" problem in AI writing

Try it

Your Readers Aren't All English Speakers. Here's How to Reach the Rest.

The language barrier most creators don't see

What "multilingual publishing" usually looks like (and why it fails)

How we approached it in Blogboat

A practical use case

Who this is for

Try it