feat: Add a "Content Edit Mode" for non-technical users

Open
#572 1 comment 4 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python, typescript
Domain
design, frontend

Research direction

The issue names no files, tests, or entry points. Start by locating the Frappe Builder editor entry point and mapping how existing text, images, links, controls, and permissions are represented. Done means a toggleable content-only mode supports the listed edits while preventing the listed design and code changes.

Written by the indexing model from the issue text.

Description

Summary

Introduce a simplified edit mode in Frappe Builder that allows non-technical users to safely update text content and images on existing pages, without exposing layout, styling, or code-editing capabilities.

Problem

Frappe Builder is powerful but its full editor is overwhelming — and risky — for non-technical contributors (marketing, content editors, project owners). A small mistake (dragging a block, editing CSS, changing a class) can break the page layout. As a result, technical users end up handling routine content updates that should be self-service.

Proposed solution

A toggleable Content Edit Mode that restricts the editor to in-place content changes only:

Allowed in this mode:

  • Edit text content (inline, WYSIWYG-style)
  • Replace images (upload / pick from library)
  • Edit links (URL + label)
  • Edit button labels and links

Locked / hidden in this mode:

  • Block structure (no add / delete / move / reorder)
  • Layout and spacing controls
  • CSS / class / style editing
  • Script editor and code blocks
  • Component creation and data sources
  • Page settings
UX notes
  • Toggle accessible from the top bar (e.g. "Content mode" / "Design mode")
  • Visual cue: editable zones get a subtle outline on hover; everything else appears non-interactive
  • Permission-based: a role (e.g. Builder Content Editor) could be restricted to this mode only, so non-technical users never see the full editor
Why this matters
  • Empowers non-technical teams to maintain pages independently
  • Reduces accidental layout breakage
  • Makes Builder viable as a CMS-like tool in organizations with mixed technical skill levels
Dominant language
Python
Stars
2.5k
Forks
583
Avg merge
17h 6m
Merged PRs (30d)
99

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from frappe/builder

All issues in frappe/builder

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.