Homepage Blocks vs Product Components

MaynorAI separates the editorial homepage from the durable SaaS machinery underneath it. The homepage can change quickly as the product narrative evolves, while authentication, billing, credits, settings, and admin screens stay stable.

A section that tells the current story is a block. A primitive that keeps the product running is a component.

Blocks are disposable

Blocks are page sections: hero copy, featured analysis, latest articles, membership, community, and submission calls to action. They should be easy to rewrite when MaynorAI shifts focus from a model comparison to a launch guide or prompt template pack.

Components are durable

Components are the reusable product parts: buttons, forms, uploaders, tables, sidebars, billing surfaces, and admin settings. They do not need to know which article is featured this week. They only need clear props and predictable behavior.

Why the split matters

For an AI image SaaS, this split keeps the work honest:

1. Move fast on content — update the homepage, SEO text, and editorial positioning without disturbing core flows.
2. Keep product logic stable — authentication, credits, and deployment code should not change because a headline changed.
3. Reuse proven primitives — image upload, account, billing, and admin screens can keep improving behind the scenes.

The result is a site that can publish quickly while still behaving like a real product.