https://tracker.phpbb.com/issues/?filter=12093hanakin wrote: 2. The current method of tracking the development and progression of the theme is diluted in the confines of the entire projects scope. It is not easy to only see/track changes,bugs,issues only related to the HTML/CSS/JS layer
It's really easy to not include given files or directory in the release package. Hundred of files are already handled like that.hanakin wrote: 3. Their are several resources that are required for development on the front-side that we may not want to ship but should be maintained within the confines of the theme. Add these to the already complex directory structure of phpbb along with a more suited development break-out of content and your file base can become astronomical.
Because you really think that you will release a new version of the style (and so notify all of the users) for each fix? Like for all projects you will wait and realease a unique release periodically.hanakin wrote: 4. Currently if their is a bug or issue with the theme that might be an easy fix we have to either wait for a completely new release of phpbb to publish said fix. When dealing with the front-end these can pile up fairly quickly.
You should have a look to prototech PR, and give recent examples please.hanakin wrote: 5. A change that only affects the front-end with no changes to the back-end is not easily understood for those testing/developing since they usually get merge with unrelated merges of back-end changes.