Hello there,
sorry for the huge and unforgivable delay and lack of support. I’ll do my best to change this in 2015.
Hi, thanks for this request. For the markup and its classes I used the theme 2013 as template. If you want to change the templates you can do that within your theme:
Can I style my own pages? (Version 1.0.2)
Yes you can. As written in the ‘Installation’-tab you only have to copy (donot move, just to be sure to have a backup) the templates from /wp-content/plugins/user-frontend/templates/ to wp-content/themes/your-theme/. After that edit it wisely.
Can I style my own pages? (Version 1.0.3 – upcoming)
Yes you can. As written in the ‘Installation’-tab you only have to copy (donot move, just to be sure to have a backup) the templates from /wp-content/plugins/user-frontend/templates/ to wp-content/themes/your-theme/user-frontend/. After that edit it wisely.
But I will rethink the basic template to fit more needs.
Best regards,
Thomas
Thanks good to hear from you and I look forward to the next version of your plugin.
My comment was about making your plugin more flexible and not tying it to one theme. A large number of WP users do not use a default theme but use one of the thousands on offer.
By making your CSS classes unique to your plugin it prevents conflicts with the CSS in themes and plugins that may be used on the site. Just good coding practice imho.
So, maybe I should add ‘uf-‘ as prefix for the classes?
In my opinion yes and have your own style sheet that defines those classes that way you do not rely on how the them has defined them. It then makes it easy for your plugin users to change those classes to suit their layout.
For instance if the theme description class is defined as font-size:20px and you are only expecting it to be 14px then it will mess up the entire layout of your plugin front end page. If you define it yourself with your own class you have full control.
Okay, I’ll update this in the next big update. Apparently the current Version 1.0.4 is stable and this is really good. So the css/template-Update will be in 1.1.
Best Regards,
Thomas
P.S.: Thanks for your feedback!