Integrated visual CMS.
Marketing edits. Devs code.
Performance and open source from pure headless. Visual and inline editing from Shopify/VTEX. Both together, in every K-Shop delivered by KMEE.
You don't have to choose between "performance and open source from pure headless" and "marketing edits without calling the dev like in Shopify".
K-Shop delivers both.
3 capabilities, one experience
Inline · Visual Editor · Theme Injector. Working together.
Inline Editable
Marketing clicks any text, headline, banner or image inside the live site and edits right there. Saves. Goes live. No separate dashboard, no preview, no deploy.
Use case
Change home headline, swap hero image, tweak landing copy — all in the context where it'll appear.
Visual Editor
Page builder in the style of Webflow/Shopify Theme Editor. Drag blocks (hero, product grid, testimonials, FAQ), reorder, configure. Saves entire pages as versioned JSON.
Use case
Create campaign landing, seasonal promo page, news blog — without opening Next.js.
Theme Injector
Real-time theme switching: primary/secondary colors, fonts, radii, shadows. A/B test brand identity? Black Friday with temporary theme? No deploy. HSL tokens applied via CSS vars.
Use case
Black Friday red, Christmas green, white-label for subsidiary — all controllable without code.
Who uses what
Each role with its entry — no responsibility confusion.
Content / Marketing
Edits headlines, copy, banners, CTAs directly on the site. No Notion, no code, no dev ticket.
E-commerce manager
Reorders product highlights, creates campaign landing, configures seasonal promo — no technical ticket.
Designer / Brand
Swaps color palette, font, radii. Sees the whole site react in real time. A/B tests identity.
Dev
Configures once which fields are editable (in code). From then on: zero marketing tickets requesting copy changes.
The best of both worlds
K-Shop vs Shopify, VTEX, Magento and pure headless (no CMS).
| Criterion | Shopify | VTEX | Magento | Pure headless | K-Shop |
|---|---|---|---|---|---|
| Visual page editor | Theme Editor (Liquid) | Site Editor (IO) | Page Builder | None | Visual Editor (drag & drop) |
| Inline editing (click and edit) | Limited | Limited | No | None | Yes, on every editable block |
| Real-time theme switcher | Paid (Plus) | Limited | Limited | None | Native, no deploy |
| Content versioning | Not native | Yes (workspaces) | Limited | Yes (Git) | Yes — versioned in Git/DB |
| Code customization | Liquid (rigid) | IO (steep curve) | Medium | Total | Total — your code |
| Lock-in | High | High | Medium | None | None (open source) |
| Performance (Lighthouse) | 70-80 | 60-75 | 60-75 | 90+ | 90+ |
Pure headless = Next.js/Remix/Astro stack with no visual CMS (e.g., Medusa, Saleor, Vendure). Great performance and flexibility, but marketing depends on dev for any content change.
How it works in practice
From technical setup to production publishing.
Dev marks the component as editable
In React code, a wrapper marks the title, banner or block as CMS-editable. Defines schema (text, image, product list, etc.).
<EditableBlock name="hero.headline">{title}</EditableBlock> Marketing enters edit mode
Visits /admin/edit or clicks the floating 'Edit' button. Visual gets handles overlaid on each editable block.
→ /admin/edit (admin session) Edits inline or via visual editor
Clicks text, edits, saves. Or opens side panel to configure full block (hero, grid, FAQ).
Inline edit · Visual builder Content persisted
Saved to CMS storage (MongoDB/PostgreSQL/Git per config). Versioned, audit trail, rollback.
Versioned · Audit trail · Rollback Publishes to production
Production push without rebuilding the app — only page cache revalidation. Visible in seconds.
ISR / on-demand revalidation What the CMS does NOT touch
By design, some data is out of marketing's reach.
Marketing does NOT edit
- !Price, stock, SKU (live in Odoo)
- !Tax data (NCM, CFOP, IBPT)
- !Shipping and payment rules
- !Customer / order records
All in Odoo, single source of truth.
Marketing edits freely
- ✓Banners, hero, copy, CTAs
- ✓Product order in highlights
- ✓Institutional pages and blog
- ✓Visual theme (colors, fonts, radii)
- ✓Seasonal campaign landings
Frequently asked questions
About K-Shop's visual CMS.
Is it TinaCMS? ▼
Yes — we use TinaCMS as the visual + Inline editing layer. It's open source, has an active community, and integrates very well with Next.js. The new piece is the integration between TinaCMS and the K-Shop stack (shared Supabase auth, pre-built block schema, custom theme injector by KMEE).
Can marketing edit products? Price, stock? ▼
No — and that's intentional. Products, prices, stock, tax stay in Odoo (the business source of truth). The CMS edits presentation: title, banner, product order in highlights, hero copy, blog. No risk of marketing changing fiscal price by mistake.
What if I want to edit the WHOLE page, not just blocks? ▼
There's the Visual Editor, which lets you create whole pages with draggable blocks. Useful for campaign landing, blog, promo page. For structural pages (home, listing, product detail), the normal flow is to use Inline on top of the fixed template.
Where is content stored? ▼
Default: TinaCMS with Git backend (versioned, open source). For clients preferring SQL DB, we plug PostgreSQL or MongoDB. You choose. Either way: versioned, audit trail, granular permissions.
Multi-language CMS? ▼
Yes. Each editable block accepts variants per locale (pt-BR, en-US, es-ES). Marketing edits the 3 versions in the same UI, no code.
How much does it cost? ▼
Zero extra license — TinaCMS is open source. The cost is the initial setup (included in the K-Shop implementation) and infrastructure for the backend (Git or DB). Unlimited users.
Want to see the CMS running?
We show the visual editor in action in a 30-minute demo. You'll see marketing changing the site without deploy, in real time.