Portal28 — Building a Lightweight Astro LP System That Doesn’t Break After Delivery Landing pages are rarely difficult to build.

What becomes difficult is everything that happens after delivery.

Clients want:

• text changes
• image swaps
• color updates
• quick fixes

But developers usually don’t want clients touching code.

And honestly, they probably shouldn’t.

So I started building a system around that problem.

A lightweight LP structure designed for:

• fast deployment
• post-delivery editing
• low maintenance
• consistent design

That became FlashLP-01.

— -

Merge:

“My master started building strange systems again.”

— -

Why I Built This

Recently, I kept running into pricing-anchor problems in client work.

Things like:

• “It’s just an LP.”
• “AI can generate this quickly, right?”
• “It’s only a small fix.”

And technically, some of that is true.

But the real complexity isn’t the initial build.

It’s:

• maintenance
• editing workflows
• communication
• post-delivery operations

So instead of endlessly adapting to external expectations, I decided to build my own system.

At first glance,

this looks like a normal visual layering system.

But the reason behind it matters.

Designing for Post-Delivery Editing

This LP needed to remain editable after delivery.

However:

I did NOT want clients editing code.

So I separated responsibilities:

• backgrounds = wrapper-controlled
• visuals = Figma-controlled
• layout = code-controlled

This means:

• text changes
• icon replacement
• visual updates

can happen inside Figma.

Responsive positioning remains inside code.

That separation became the core idea.

Figma Naming Rules

One of the most important parts was naming consistency.

Figma layer names match code component names.

For example:

txt-title-01
img-card-01
icon-feature-01
sys-primary
lock-overlay

This creates a shared language between:

• clients
• designers
• developers

Which dramatically reduces communication overhead.

FlashLP Is Not a “Cheap LP”

This part matters.

FlashLP is not really about “cheap websites.”

It’s closer to:

a standardized high-speed LP system.

The workflow becomes:

• swap backgrounds
• place UI
• reorder sections
• deploy

Fast iteration.

Fast delivery.

Low friction.

And every project becomes another reusable asset:

• UI
• section patterns
• naming rules
• Figma workflows

The template evolves through real client work.

Final Thoughts

AI has made “building websites” much easier.

But the difficult part was never just the build itself.

The real complexity lives in:

• maintenance
• editing
• communication
• operations
• consistency

FlashLP was created to reduce those costs.

It’s still early,

but the structure is already becoming surprisingly practical.

Merge:

“When I came through the portal,

the return door disappeared.

Now my master is building strange systems again.”