#Portal 2 custom skins update#
#Portal 2 custom skins skin#

Make sure you have your liferay-portal instance configured to use CKEditor in at least one place by setting one of the appropriate properties in your portal-ext.properties file. To test your local CKEditor build in liferay-portal: Git is configured to ignore changes to the submodule, so you will only see them in the output of commands like git status, git show, git log -p (etc) if you pass the -ignore-submodules=none switch.

#Portal 2 custom skins update#

NOTE: In order to prevent unintended commits to the submodule, using ck.sh update is the only supported way to change the commit the submodule is referencing. This will update the ckeditor-dev submodule to point at the corresponding commit. Make sure you're up-to-date with the superproject repository:ДЄ prompt will appear asking you which version you'd like to select. These are the steps you would follow, for example, to apply a workaround for a bug in the upstream project:

Publishing the liferay-ckeditor package to NPM.

With those basic operations in place, the most common workflows are described in the following sections:

#Portal 2 custom skins skin#

ck.sh createskin creates a copy of CKEditor's moono-lisa base skin on /skins folder with the provided name.ck.sh build produces a build based on the current contents of the submodule, writing the files out to the 'ckeditor/' directory and committing the result.ck.sh update updates to a requested version of CKEditor and rebases the contents of the 'patches/' directory onto the new version.ck.sh patch freshens the contents of the 'patches/' directory based on the current contents of the 'liferay' branch in the submodule.ck.sh setup makes sure the submodule is up-to-date, creates a 'liferay' branch inside it, and applies patches from the 'patches/' directory to that branch.The ckeditor-dev submodule always points at the pristine (unmodified) upstream CKEditor repository, and specifically, at a release tag.Make changes in build artifacts obvious (again, but inspecting their history).

Make changes in patches over time obvious (by inspecting their history).

Make Liferay-specific patches easy to inspect by aggregating them into a directory.

A ckeditor directory containing the committed build artifacts.ДЇor details on why we settled on this approach, please see issues #7, #16 and #66 but in short, the desired attributes are:.A ck.sh script for setting up the project, creating/updating patches, and producing releases.A skins/ directory containing custom skins.A patches/ directory containing Liferay-specific changes to be applied to the upstream.A submodule at ckeditor-dev pointing at the upstream CKEditor project.

This repo contains tooling for maintaining Liferay's customized version of CKEditor.