Themeing poll
What is a better approach for Composr's design development?
Each major release moves things forward a lot, but completely breaks existing themes |
![]() ![]() ![]() |
Themeing compatibility is perfect, but it's up to 3rd party themes to have anything decent looking |
![]() ![]() ![]() |
Posted
#2344
(In Topic #430)

Site director

Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Posted

Site staff

Posted

Standard member

KingBast said
Given the lack of existing themes (even ocportal had a limited amount), I say it makes sense to push forward when there is nothing much to break.
From “Post #2,348”, 14th April 2017, 8:52 pm
Need to at least maintain backward compatibility, while there are limited themes I think it is important to note that some sites out there may be running with heavy customisation's. And to have those sites break due to a composr upgrade would be bad to say the least.
1 guest and 0 members have just viewed this.