New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.9 Theme System #3689
Comments
We have also had some discussion about managing JavaScript scripts related to themes. The idea was that we'd have a JS manager similar to the stylesheet manager with some of the following features:
|
Regarding theme installation, I would love to package themes as Composer packages so that they can be installed that way as well as via the standard upload procedure (including simply uploading a ZIP file to the ACP I hope). Composer's JSON schema already has a Composer's schema also has an |
As to theme info, I would start by drawing a direct comparison from what we are doing now. As it stands, the inheritance system that is currently in place works fairly well. The main issue with the current system that I see in practice is that upgrades require quite a bit of knowledge from admins because of how updates are handled. If there was a way to improve this process, that would be a welcome change. I'm currently in the process of mimicking the existing inheritance pattern for a plugin that needs a similar system. I honestly haven't found any ways to improve the current setup, but I am still looking into it. As to direct answers to the questions in @dvz's opening post, each of these will need to be referenced individually. For example, to know which theme properties will be essential to the manifest, we would need to do a project-wide analysis to see what is essential pre-load. |
Also, I would like to see required folder structures for third-party devs so that we can make a trouble-free auto installer for plugins, themes, and translations. (And as @euantorano said, Composer packages) |
The problem in 1.8 lies mainly with presentation of Find Updated Templates - what's IMO missing the most is a comparison of what's changed in specific upgrade in the master set; these "diffs" would be easier to recognize than master-custom comparison (as unrelated modifications are caught up in the report), along with a suitable UI (perhaps the diff - "suggested changes"/"copy these" - and an editor side-by-side). |
That sounds great, @dvz If it were possible to have a side-by-side comparison, that would be optimal. |
Hi, Can you make a responsive theme please |
Yes, that is one of the main 1.9 features.
…On Fri, 15 Nov 2019, at 22:55, Jérémy wrote:
Hi,
Can you make a responsive theme please
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#3689?email_source=notifications&email_token=AAFW24MKQOKZCBLU3POCLSLQT4SH5A5CNFSM4HTEAUV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEG646I#issuecomment-554561145>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFW24I5GNSYD6JBLPOMSGLQT4SH5ANCNFSM4HTEAUVQ>.
|
related discussion: https://community.mybb.com/thread-232217.html |
MyBB 1.8 themes' information, contained in XML files, are expected to be split into the filesystem directly (templates, stylesheets, and additional assets) and a
package.json
manifest file with properties and metadata.The text was updated successfully, but these errors were encountered: