Site Publisher Search and Sorting in the end-user cPanel interface
Open Discussion
The cPanel Site Publisher introduce great feature for offering a simple and quick website design for the client. Currently, the cPanel interface will list all of the available templates in a huge list. This is easy to use with the default 3 templates installed, but once you have a 100 + templates, it is more difficult to select the desired template. I suggest the ability to search installed template by keyword or by category. Both information could be entered directly in the meta.json file in the “information” tag.
EX :
-
{
- "information": {
- "id": "stylish",
- "name": "Stylish",
- "description": "Page contemporaine avec style",
- "preview_image_path": "/preview.png",
- "category":"business card",
- "keyword","corporate, blue, cellphone,splashpage"
- },
- "fields": [
- ….
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
Can do.
The only concern I can see with this is the ability to localize this information so that those who don't speak english can find templates using their native languages AND site template designers can design templates with specific regions in mind. We'll need to accommodate that in the plans for keyword meta information
Can do.
The only concern I can see with this is the ability to localize this information so that those who don't speak english can find templates using their native languages AND site template designers can design templates with specific regions in mind. We'll need to accommodate that in the plans for keyword meta information
I agree with you, this problem is already present with the current format, since we can’t define a language for the actual description and field detail.
To solve this problem, the main template should have a “default language” tag in the meta.json file, and every language tag should be in separate files (You would therefore remove the "label" and "placeholder" from the field area): EX
"information": {
"id": "personal",
"name": "Personal",
"description": "Single page personal site",
"preview_image_path":"/preview.png",
“ default_lang”:”English”,
},
"fields": [
{
"id": "fullName",
"type": "text",
},
And create separate langue json files so that each provider could support the re desired language (if the cPanel default language is not in the list that the system would use the template default language setting).
"fields":{
"fullName_label":"Enter your FullName",
"fullName_placeholder":"YourName",
}
}
I agree with you, this problem is already present with the current format, since we can’t define a language for the actual description and field detail.
To solve this problem, the main template should have a “default language” tag in the meta.json file, and every language tag should be in separate files (You would therefore remove the "label" and "placeholder" from the field area): EX
"information": {
"id": "personal",
"name": "Personal",
"description": "Single page personal site",
"preview_image_path":"/preview.png",
“ default_lang”:”English”,
},
"fields": [
{
"id": "fullName",
"type": "text",
},
And create separate langue json files so that each provider could support the re desired language (if the cPanel default language is not in the list that the system would use the template default language setting).
"fields":{
"fullName_label":"Enter your FullName",
"fullName_placeholder":"YourName",
}
}
Language support is definitely needed!
Language support is definitely needed!
Replies have been locked on this page!