@Chris Korhonen I agree with you that our OpenBrand idea does not solve the two problems that you are describing. But the first problem you describe is based on a non agreed change of style and non agreed add of functionality. And that will lead to both brilliant customization as well as disasters depending on the skills of the user that is making the changes. And that problem can never be solved in an easy way.
The other problem you talk about; removing parts of sites thus fiddling with ad-revenue and promotion. Yes that is bad but it is equally hard to solve as your first problem.
Our idea with the OpenBrand standard is not trying to solve those two problems.
What me and Jaan Orvet is asking for is a standard for agreed changes of styling, and we think that the OpenBrand idea is best suited for webapps and services, not public sites.
If you as a site owner or app-provider say “Ok, I follow the OpenBrand standard” then you know what parts of your app/service that will be open for user styling. And on the other side the user will know what they can change. It all has to be done in a controled way so that everyone knows the guidelines and it does not interfear with the overall development.
The main goal of OpenBrand is not to remove parts of the site or change functionality. It’s more to, as @Jason Karns is talking about, changing the look and feel of the app/service that I buy into so that it fits in with my (as a user) brand.
Andreas Carlsson
@Chris Korhonen I agree with you that our OpenBrand idea does not solve the two problems that you are describing. But the first problem you describe is based on a non agreed change of style and non agreed add of functionality. And that will lead to both brilliant customization as well as disasters depending on the skills of the user that is making the changes. And that problem can never be solved in an easy way.
The other problem you talk about; removing parts of sites thus fiddling with ad-revenue and promotion. Yes that is bad but it is equally hard to solve as your first problem.
Our idea with the OpenBrand standard is not trying to solve those two problems.
What me and Jaan Orvet is asking for is a standard for agreed changes of styling, and we think that the OpenBrand idea is best suited for webapps and services, not public sites.
If you as a site owner or app-provider say “Ok, I follow the OpenBrand standard” then you know what parts of your app/service that will be open for user styling. And on the other side the user will know what they can change. It all has to be done in a controled way so that everyone knows the guidelines and it does not interfear with the overall development.
The main goal of OpenBrand is not to remove parts of the site or change functionality. It’s more to, as @Jason Karns is talking about, changing the look and feel of the app/service that I buy into so that it fits in with my (as a user) brand.