This feature idea allows CJT users to be able to create their own WordPress themes and plugins. We believe the framework is already there for this to happen.

The idea is better explained in this abstract example on creating a Theme. A user clicks a button (e.g. Create Theme) and CJT would access the directory structure and create the Theme folder, basic template files, etc. All the internal functionality for the theme would be done by the user, however we can add more help and templates for those more commonly used. For example PHP code that iterates over all the posts to be displayed can be readily picked up and inserted by the user.

We feel there needs to be an easier way for users to add, modify, test and experiment with CSS elements and values within code blocks.

For example, when clicking on the assigned Page (Post, Page, Category, etc…), a popup form can appear displaying that page, and allowing users to inspect the element via a mouse click. After the element is clicked, a window with CSS properties appear, where users can pick up CSS values. After clicking Ok, the window will close and automatically add the code into the CJT code block.

When we first designed this plugin many years ago, we created almost 100 rasterised icons. It seems that technology has left behind rasterised icons in favour for icon fonts. This allows graphics to be output in a similar way that textual fonts are output, where they can be resized and recoloured using CSS code.

The idea is to replace the entire CJT rasterised icon set as icon fonts to make it more like WordPress. We will also look at other aspects of the layout to conform more to the WordPress look and feel too.

Every time you create a code block, a shortcode is generated using the code block title. You can add an entire code block into a page/post using them because within the Page/Post editor, we have a dedicated TinyMCE button that provides a dropdown list of all available shortcodes.

The problem is, when many code blocks have been created, there will also be a large list of shorcodes and it can be very difficult to find what you are looking for.

There needs to be a simple function developed to output the shortcode list alphabetically.

This feature idea will allow users to create a full backup, which is uploaded and stored on the CJT server. This backup can then be downloaded and imported again into a website running CJT.

Benefits include:

  • Accessing your backup from anywhere and everywhere
  • Can be imported again into any another CJT installation
  • Allow for managing multiple backups
  • In the future we might provide a gateway, where users can share their code blocks between each other

It would be great if users can edit and save revisions for WordPress core, plugin and theme files. We would have to create another revision copy in another location, delegate this copy instead of the original one.

We believe this can be achieved for CSS and JavaScript files and we have many workarounds and solutions to get this to work for PHP, however we really need to investigate this further to see if it’s possible to do.

Important Note

It is not a good idea to update the real file on disk, as this is a security risk and might fail under many servers. It also might destroy the site.

We believe there are many users who are developers that use CSS & JavaScript Toolbox for their clients. CJT may be installed on many client sites, and even on a WordPress multisite installation.

With that in mind, there needs to be a way from which they can replicate the code blocks to all clients from a central location. In other words, like a base server that pushes all code blocks to other servers. Client sites could therefore be managed remotely. Developers would be able to manage CJT blocks from one WordPress site (i.e. master site) without opening any client WordPress sites using the browser.