Open Question and Feedback for wCMS Core Devs

[TinyCoding]

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!

[wiz]

To answer a few of these that I haven't here: viewtopic.php?p=8451#p8451

For most of these, we really welcome PR's. There are no restrictions to the core of WonderCMS.

#1: Opened GitHub issue if we tackle it in the nearby future ourselves.
#2: There are no plans on updating the default HTML editor, we would really like to keep editors a separate plugin, which would be amazing to have.
#5: Notifications can be completely disabled as of a few versions back, however stacking them into one would be a stretch, however any improvements are welcome. We have to keep in mind there are also 3 types of notifications, would they be treated the same?
#7: This could also be improve with an option in the security settings section, which would enable users to include their own.
#8: Could you please elaborate with an example, do you mean the header title? If yes, there is a theme or two that enabled editing the title without going to the Settings modal.
#9: No plans from my side

Please ask again if I missed something you wanted to figure out and I missed somewhere.

[TinyCoding]

Hi!

First of all, sorry for my late response. Been re-writing some of the core since you and everyone else were open and said, "you are free to fork and do whatever you like".

I want to start with nr 8 because it would benefit all users. What I mean is this:
We can edit most areas of the website just blicking on the section/area and directly from there, edit the text using the texteditor.
Would it not be beneficial if we could click on the <head> so to speak (even that is the wrong tag to refer to) and from there, edit whatever is in the <header> tag? That way we could add text, images, links (whatever we want) before or after the logo, menu and/ or in-between them?

Perhaps a simple HTML code example can explain what I mean?

Code example:

<!DOCTYPE html>
<html lang="en" dir="ltr" class="no-js">
<head>
<meta http-equiv="Content-Security-Policy" content="all your meta here">
these can be used, but should be set by the server
<meta http-equiv="X-Content-Type-Options" content="nosniff">
<meta http-equiv="X-Frame-Options" content="DENY">
<meta http-equiv="X-XSS-Protection" content="1; mode=block">
<title>website name</title>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="keywords" content="">
<meta name="description" content="">
<link rel="stylesheet" href="styles.css" type="text/css" media="screen">
<link rel="shortcut icon" href="your base64 favicon here" />
<meta name="author" content="">
<meta name="robots" content="follow, index">
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="">
<meta name="twitter:image" content="">
<meta name="twitter:url" content="">
<meta name="twitter:description" content="">
<meta property="og:locale" content="en_US">
<meta property="og:url" content="" />
<meta property="og:title" content="" />
<meta property="og:image" content="" />
<meta property="og:type" content="article" />
<meta property="og:site_name" content=""/>
<meta property="og:description" content=""/>
<!-- should this to be ediable? -->
</head>
<body>
<header>
<!-- should be ediable -->
<nav>
<a href="/" rel="noreferrer noopener" class="current">Start</a>
<a href="https://example.com/link" rel="noreferrer noopener">Link</a>
<a href="https://example.com/link-two" rel="noreferrer noopener">Link</a>
</nav>
<h1>
<svg height="40" width="320" xmlns="http://www.w3.org/2000/svg">
<rect fill="orange" height="40" rx="4" ry="4" width="320" />
<text dominant-baseline="middle" fill="#333" font-family="arial" font-size="30" text-anchor="middle" x="50%" y="50%">example.com</text>
</svg>
</h1>
<!-- should be ediable until here -->
</header>
<main>
<!-- content here, should be editable -->
</main>
<footer>
<p>footer text, should be editable</p>
</footer>
</body>
</html>

Regarding the notifications, perhaps stacking them all is not the best idea, but at the same time - seeing 4 or 5 or 6 or however many there are stacked is also not the best UI? My feedback was merly an idea in terms of, "how can I help, if I can help?"

The one main thing I hope you improve upon is the fact that "you jump back to the site / admin frontend" each time you make a change. That is, to be honest, very annoying.