craftcms / craftcms/ckeditor

Would Give Firstborn Child for a JSON file Config of CKEditor Instead of CMS Configuration

Open
#270 0 comments 33 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
PHP
Stars
47
Forks
32
PR merge metrics
No merged PRs in 30d

Description

Description

This is more of a feature request. I think this is the spot?

I loved Redactor. I could just paste my JSON configs between projects and not think about it.

I dread setting up a new CKEditor site, in particular the config part. I can't just drop my config files in like I could with redactor. I need to go into the Plugin setting, add an entry, manually drag CKEditor buttons around a control panel, add custom JSON for anchor tags because (bafflingly) CKEditor doesn't have a "_blank" option in the a tags, save it, repeat for a few extra styles., deploy it.

If I forgot a button lik e"bold" and just want to upload a tweak to the config file, I need to fire up local. Change the plugin. Get the config file change. Run a proper backup in prod - which is usually load balanced for us - zip fils, back up the db, run a prop QA, make sure I have a way to revert etc. then deploy the change, hope there's no issues. And then I can have my front end button config change. It can be a bit dreadful.

Can we enable the ability to configure these in a config file or php like we did with redactor?

Additional info
  • Craft version: 4 or 5

Contributor guide

Open the 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.

Research direction

The issue names no files, tests, or entry points. Start by reviewing how the CKEditor plugin currently stores CMS configuration and compare it with the Redactor configuration approach described. Done means providing a documented, deployable configuration-file or PHP-based alternative to the control-panel setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.