Currently we plan to make Themler more stable and fix bugs. Therefore
a few next updates will not contain new major features.
It's good to know that you are fixing bugs first, though that should have been done way to early.
The alarming thing is, when you take 3 months to fix some minor bugs, what would it take to develop new features?
Second bad thing is you always keep ignoring the suggestions, feedback and voted features from your clients / themler community.
Any way I've few more suggestions (which are bugs that needed to be fixed)
In generated CSS, (for example - wordpress) you put Theme URI : http://www.themler.com/wordpress-themes. This should not be there. Instead there should be project name / URL
When we work on fonts and use Inherit font name etc, firefox or chrome developer extensions shows Billion Font rather than Open Sans or some other font that was actually chosen in Themler?
When we insert image control, the default blank image thumbnail is loaded from http://cstatic.billiondigital.com/themler/354/images/defaultImage.jpg, while it should be added to local repository of themler.
When we insert separator control, whether it is a colored line or text, there is also a link in generated code which is http://cstatic.billiondigital.com/themler/354/images/defaultImage.jpg, kindly remove it as it is unnecessary.
Also please consider to remove unnecessary code from generated CSS. There should be a CSS customizer/editor built into themler through which we can edit live css or there should be a CSS optimizer through which we can optimize css by removing unused styles. (that's a much needed function as current css code is blotty)
Also consider to change how you deal with [text] shortcode, for example, it's pretty odd to user [text tag=h2] instead of <h2> tag, I know we can add html control in order to avoid this issue, but again [text tag=p] is also not good way to produce paragraphs.
The generated code is the main part where you need to focus first, because if themler's code is not SEO friendly, its useless to make beautiful designs. When you start focusing on your generated codes, themler will also become compatible to YOAST, Squirrly and other SEO plugins. Currently excessive usage of shortcodes destroys the purpose of a website (though it looks beautiful )
Bug # 1-4 are extremely easy to fix, which could take maximum an hour or two for your developers. Rest are also not way too much complicated, therefore, kindly incorporate them in upcoming beta or final version.
> Currently we plan to make Themler more stable and fix bugs. Therefore
> a few next updates will not contain new major features.
It's good to know that you are fixing bugs first, though that should have been done way to early.
The alarming thing is, when you take 3 months to fix some minor bugs, what would it take to develop new features?
Second bad thing is you always keep ignoring the suggestions, feedback and voted features from your clients / themler community.
Any way I've few more suggestions (which are bugs that needed to be fixed)
1. In generated CSS, (for example - wordpress) you put Theme URI : http://www.themler.com/wordpress-themes. This should not be there. Instead there should be project name / URL
2. When we work on fonts and use Inherit font name etc, firefox or chrome developer extensions shows Billion Font rather than Open Sans or some other font that was actually chosen in Themler?
3. When we insert image control, the default blank image thumbnail is loaded from http://cstatic.billiondigital.com/themler/354/images/defaultImage.jpg, while it should be added to local repository of themler.
4. When we insert separator control, whether it is a colored line or text, there is also a link in generated code which is http://cstatic.billiondigital.com/themler/354/images/defaultImage.jpg, kindly remove it as it is unnecessary.
5. Also please consider to remove unnecessary code from generated CSS. There should be a CSS customizer/editor built into themler through which we can edit live css or there should be a CSS optimizer through which we can optimize css by removing unused styles. (that's a much needed function as current css code is blotty)
6. Also consider to change how you deal with [text] shortcode, for example, it's pretty odd to user [text tag=h2] instead of <h2> tag, I know we can add html control in order to avoid this issue, but again [text tag=p] is also not good way to produce paragraphs.
The generated code is the main part where you need to focus first, because if themler's code is not SEO friendly, its useless to make beautiful designs. When you start focusing on your generated codes, themler will also become compatible to YOAST, Squirrly and other SEO plugins. Currently excessive usage of shortcodes destroys the purpose of a website (though it looks beautiful )
Bug # 1-4 are extremely easy to fix, which could take maximum an hour or two for your developers. Rest are also not way too much complicated, therefore, kindly incorporate them in upcoming beta or final version.
Last edited 05 March 2017 by QAAF Tech