Download
2012-10-25, 06:58:36
Thank you for this thread; GS is great and still can make good progress!
My next version wishes comparing to GetSimple 3.1.2 (I hope nothing is already there):
Include a feature in the core that allows to define Custom Fields in a template, so that these fields show up in the page editor only when using a certain template. A bit different to the Custom Fields plugin where you define the fields for all pages in a backend-configuration; I have found just now Simple Input Tabs plugin which seems to do my wish, but I like to have it in the core and possibly with the field format options (name, description, field type, prefilled text/selections, etc.) of the Custom Fields plugin.
Add core support for simple chronological pages (news, simple blog, etc.) that are sortable by date or priority and the list order can be changed (backend, maybe also frontend). Extended features (WP like blog) should remain in a supported plugin.
Choose 5 to 10 plugins that receive maximum core support: included in pre-release testing, code optimization for best integration, long time support, etc. My proposals: I18N, I18N Custom Fields (only if core support like above is not integrated), I18N Gallery, p01-contact (needs update/optimization or substitution), I18N Search, Blog Plugin (News Manager?)
You can apply increased core support for a greater number of plugins (20?) in a similar way but doing the workflow only for major GS releases.
Best would be if you make a poll under the users for preselection of the most desired plugins.
Allow noindex, nofollow setting for a single page (maybe ON/OFF setting in gsconfig?) Link
Allow Change of default Link type in editor at least for Local page/URL maybe in gsconfig? Link
Already discussed, but I repeat to confirm my support:
WYSIWYG CKeditor: check if GS integration advantages vs. HTML5/CSS3 compatibility is still ok, allow easy customization and integration of other editors. Link
Increasing of Multi-User features. Please add also easy output options of names, times, etc. in the template.
My next version wishes comparing to GetSimple 3.1.2 (I hope nothing is already there):
Include a feature in the core that allows to define Custom Fields in a template, so that these fields show up in the page editor only when using a certain template. A bit different to the Custom Fields plugin where you define the fields for all pages in a backend-configuration; I have found just now Simple Input Tabs plugin which seems to do my wish, but I like to have it in the core and possibly with the field format options (name, description, field type, prefilled text/selections, etc.) of the Custom Fields plugin.
Add core support for simple chronological pages (news, simple blog, etc.) that are sortable by date or priority and the list order can be changed (backend, maybe also frontend). Extended features (WP like blog) should remain in a supported plugin.
Choose 5 to 10 plugins that receive maximum core support: included in pre-release testing, code optimization for best integration, long time support, etc. My proposals: I18N, I18N Custom Fields (only if core support like above is not integrated), I18N Gallery, p01-contact (needs update/optimization or substitution), I18N Search, Blog Plugin (News Manager?)
You can apply increased core support for a greater number of plugins (20?) in a similar way but doing the workflow only for major GS releases.
Best would be if you make a poll under the users for preselection of the most desired plugins.
Allow noindex, nofollow setting for a single page (maybe ON/OFF setting in gsconfig?) Link
Allow Change of default Link type in editor at least for Local page/URL maybe in gsconfig? Link
Already discussed, but I repeat to confirm my support:
WYSIWYG CKeditor: check if GS integration advantages vs. HTML5/CSS3 compatibility is still ok, allow easy customization and integration of other editors. Link
Increasing of Multi-User features. Please add also easy output options of names, times, etc. in the template.
Advanced HTML5 & CSS3 coder. Simple JS & PHP hacker (not enough for new function coding). Build one webpage with GS (late 2012). Focusing on Theme customizing/Template files. Experience with WP.
