You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@darko-hrgovic I'm still exploring this a bit, but from what I see so far:
child themes can remain unchanged (other than core_version_requirement and fixing deprecated code in any custom hooks) for Drupal 10 - the changes in the parent theme won't require any changes to the child theme
classy is NOT a valid starterkit theme, but this can be bypassed by 'hacking core' and adding starterkit: true to the classy .info file. This then allows classy to generate a base theme via the php core/scripts/drupal generate-theme --starterkit classy [my_new_theme]. The one thing I'm not 100% clear on is whether classy has the required base elements from its base theme, stable. Nested dolls... This needs review / testing
If we can rely on the output of the script above (ie. it's complete and includes all assets), the transition is fairly simple. We add any templates that are not in the theme already, update the hooks (there's one additional), add image / css assets and update the libraries. At that point Galactus can be a completely decoupled base theme without any additional core themes it will need to rely on.
Anyway, that's what I see so far. The proof will be in the pudding (whatever that means)....
James, Joel and I discussed the deprecation of Classy and need to rebuild Galactus with starterkit and remove the Classy dependency.
How will this affect this theme?
Does it also need to be rebuilt with Galactus as the starterkit?
The text was updated successfully, but these errors were encountered: