below are some ideas i thought could make things slightly better for user & developers alike, mostly a road map for myself and for anyone else who would like to contribute.

Done

• make october:util more helpful instead of Utility command "" does not exist!

• have a regex option to hide files under the media manager ex..gitignore

• install plugins driver, builder by default as 99% of users will be needing it.

• remove the menu item automatically when the cms page is not available instead of showing CMS page: Unnamed menu item in the item description.

• change static pages menu item drag icon to the left for easier ordering/nesting

• add public/ folder by default and mirror storage folder only, for better security and easier maintainability of .htaccess

InProgress

• drag & drop for partial, content, asset

• automatically add an entry to the layout file for partials with ajax components to avoid the ajax error.

• shortcut cheat sheet ex.ctrl/alt+s for saving

• have an extra tab in the code editor to reflect the selected component markup

  atm to override a component style we use http://octobercms.com/docs/cms/components#overriding-partials which for new users ex.'myself' felt kinda lost, another solution which seemd easier was https://octobercms.com/forum/post/overriding-plugins-templates#post-6136,

  BUT

  what if we have a new extra tab ex.component markup right next to the Markup, Code that gets automatically filled with the component markup when the user adds a component, now if the user made any changes to this file, the same procedure made in Overriding component partials above is followed automatically & the code in this tab reflects the markup from the newly made file, now the user don't get confused between the default & new made changes plus keeping the user experience as seamless as possible.

• scroll past end in page editor

• translation option for cms pages (same as static pages)

• have an option to hide pages from the menu list ex.hide custom error pages, could be a checkbox in the page view itself ex.hide from menu

• hidden pages shouldn't show up in the menu list

• menu items translation & a possible solution

• add the same option of creating sub-pages on the fly from static > pages to cms > pages for creating nested menu automatically

• have a button for duplicate file under cms for faster workflow

• add a new side panel item for snippets and make it available for cms > page aswell + move its folder to the theme root instead of being under partials for better separation of concern

  for static pages, the usage is the same

  for cms pages, we have a new tag snippet & have the same usage as partials

• have an option under translation messages to add a new row so we don't need to wait for the list of keys to be populated through the front-end and the translation become available when its needed.

• static menu component alias follows the menu code/title automatically for easier/smoother workflow.

• have an option to close all opened tabs.

• under backend > update plugins, remove manage plugins button & add a new remove, disable/enable buttons inside each plugin for easier/faster manageability of installed plugins.

• add a new console command to get the cms version.

• add the ability to use php functions directly inside twig ex.mt_rand()

• set onStart() lifecycle function as default for code tab, unless the user explicitly change it to something else, to ease the learning curve for newcomers.

• static pages folder under themes > yourTheme > content should be removed if no files in it.

• remove meta folder and move menus to the theme root folder (we can have the static-pages.yml inside it as well).

• use a simpler way for passing variables to partials

  // before
  {% partial "location" city="Vancouver" country="Canada" %}
  // after
  {% partial "location", ("Vancouver", "Canada") %}

• use https://github.com/jenssegers/date instead of only carbon to handle localized dates on the fly

Last updated 8 years ago

Some great ideas in here. It would be cool if you could submit each improvement as a Pull Request on GitHub so we can discuss each one in more detail.

daftspunk said:

Some great ideas in here. It would be cool if you could submit each improvement as a Pull Request on GitHub so we can discuss each one in more detail.

will do ;)

Last updated 8 years ago