Open Question and Feedback for wCMS Core Devs
Posted: Fri Aug 16, 2024 6:57 pm
Hi!
I've been using you wCMS for give or take a week now, and I have a question about forking your project.
It is obviously open source, but I the kind of person who always asks and openly want to discuss before moving forward.
The list below are suggestions based on my personal experience, skills, and well over 20+ years within front- and backend solutions. I mean no disrespect whatsoever, I just want ask and by doing so, get some clarification on the following questions:
#1: The Settings modal; are there plans on changing its behavior in terms of not closing it after each click? In all honesty, the current behavior is not user friendly.
#2: Are there any plans on changing the default editor? If not, are there plans on updating the Summernote editor since you've stated that it's "outdated"?
Also, in regards to Summernote, are there plans during an update to remove external JS and/or other request?
#3: The database.js can easily grow and become quite large (from kb > mb) which impacts site speed and loading times considering that the file, from my current understanding, is loaded each time an request is made.
Have you considered other options regarding PHP in terms of memory (open, read, close) for this? Imagine a blog with hundreds of posts with hundreds of thousands of daily readers, each time a post is loaded, the database.js (JSON) has to be loaded. Caching aside, have you thought of keeping it separated from all the content?
Perhaps have the current database.js to only manage the meny and basic information, keeping its file size to maximum a few kilobytes and having each page/post ss a separate "database"?
#4: The menu section inside the settings modal has no option from what I can see for moving a sub page into becoming a parent link? Will this change?
#5: Notifications can easily, since they are stacked when more than one, be overwhelming. Any chance of using just one notification and instead add additional ones within a <details><summary></summary></details> so-called section?
#6: För the menu itself, is there a way to overwrite its CSS without using !important? If not, do you have a snippet based on existing hooks allowing us to create custom menus with or without using the global menu argument hoos? The menu, no matter theme used, looks kind of non user friendly and the mobile version could also be improved since the setting and logout are in the way.
I would love to know the actual structure of the menu, as in:
<nav>
<ul>
<li>....</li>
</ul>
</nav>
And the classes used. Edit: yes, I am checking and reviewing using inspect.
Same goes in terms of CSS for the Settings modal and the logout button. The are in the way depending on screensize and even though I done a test by moving the PHP shorttag into the footer, it seems the CSS is loaded from an external source which based on need, forces me to use !important CSS (which should never be used).
#7: Are there any plans of using self hosted or inline code for all the JS etc which the admin (Settings) use?
To me, it seems like overkill to load complete minified versions of entire libraries while in reality, only a very small part of them are utilized.
#8: The content areas are one thing, but are there any plans on making the header editable?
#9: Are there plans on adding flex or grid layouts, or are layouts as such already implemented?
Thanks!
I've been using you wCMS for give or take a week now, and I have a question about forking your project.
It is obviously open source, but I the kind of person who always asks and openly want to discuss before moving forward.
The list below are suggestions based on my personal experience, skills, and well over 20+ years within front- and backend solutions. I mean no disrespect whatsoever, I just want ask and by doing so, get some clarification on the following questions:
#1: The Settings modal; are there plans on changing its behavior in terms of not closing it after each click? In all honesty, the current behavior is not user friendly.
#2: Are there any plans on changing the default editor? If not, are there plans on updating the Summernote editor since you've stated that it's "outdated"?
Also, in regards to Summernote, are there plans during an update to remove external JS and/or other request?
#3: The database.js can easily grow and become quite large (from kb > mb) which impacts site speed and loading times considering that the file, from my current understanding, is loaded each time an request is made.
Have you considered other options regarding PHP in terms of memory (open, read, close) for this? Imagine a blog with hundreds of posts with hundreds of thousands of daily readers, each time a post is loaded, the database.js (JSON) has to be loaded. Caching aside, have you thought of keeping it separated from all the content?
Perhaps have the current database.js to only manage the meny and basic information, keeping its file size to maximum a few kilobytes and having each page/post ss a separate "database"?
#4: The menu section inside the settings modal has no option from what I can see for moving a sub page into becoming a parent link? Will this change?
#5: Notifications can easily, since they are stacked when more than one, be overwhelming. Any chance of using just one notification and instead add additional ones within a <details><summary></summary></details> so-called section?
#6: För the menu itself, is there a way to overwrite its CSS without using !important? If not, do you have a snippet based on existing hooks allowing us to create custom menus with or without using the global menu argument hoos? The menu, no matter theme used, looks kind of non user friendly and the mobile version could also be improved since the setting and logout are in the way.
I would love to know the actual structure of the menu, as in:
<nav>
<ul>
<li>....</li>
</ul>
</nav>
And the classes used. Edit: yes, I am checking and reviewing using inspect.
Same goes in terms of CSS for the Settings modal and the logout button. The are in the way depending on screensize and even though I done a test by moving the PHP shorttag into the footer, it seems the CSS is loaded from an external source which based on need, forces me to use !important CSS (which should never be used).
#7: Are there any plans of using self hosted or inline code for all the JS etc which the admin (Settings) use?
To me, it seems like overkill to load complete minified versions of entire libraries while in reality, only a very small part of them are utilized.
#8: The content areas are one thing, but are there any plans on making the header editable?
#9: Are there plans on adding flex or grid layouts, or are layouts as such already implemented?
Thanks!
