When shopping for a theme, most theme authors state what you can / cannot do with their theme. If the theme comes with a GNU General Public License [http://en.wikipedia.org/wiki/GNU_General_Public_License] you’ll have all the freedom you can want.
It’s allways polite though to give credit where credit is due. So reveiling ‘your sources’ e.g. in the top of your code / in a credits section is nice.
Thread Starter
Shawn Q
(@siddhachakra)
Of course, the GNU License, great, thank you! I feel that most themes are built upon others’ work anyways (e.g. UI elements, design layouts, js sliders, plugins etc.). I just want to make sure that I’m giving credit where its due and want to be clear where the line is drawn in cases like altering the HTML/CSS of a theme and adding my own custom UI design elements and graphics so that I can use the site for showcasing.
It also seems discouraging to see so much contention towards the use of themes. I know how to design and I’m decent developer, but whats with all the hate? I mean if using templates are wrong then using premade code and plugins that others have developed also has to be looked down upon but its not. I guess I’m just trying to understand where the shift it credit changes.
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
but whats with all the hate?
Themes with licenses not GPL go against the open-source philosophy of the web. Meaning you may not be able to customise them.
It’s in your own interest to use for GPL themes.
