![]() These are the steps to do the copy from the donor theme to the recipient theme. The steps below ensure that this is the case. It is very important that you do this copy in such a way that any subsequent theme updates do not overwrite what you have done. Optionally, one or more JS (plain text) files that contain JavaScript/jQuery code to make the particle work.Īll theme specific particles reside in: THEMENAME/particlesĪll theme specific particle SCSS files reside in: THEMENAME/scss/THEMENAME/particlesĪll theme specific JS files reside in: THEMENAME/js.A SCSS (plain text) file that contains the SASS/CSS to style the rendered particle on your page.A TWIG (plain text) file that uses those fields to render output on your page.A YAML (plain text) file that tells Gantry 5 what fields the particle uses. ![]() This is not about changing any functionality - you are copying the particle "as-is".That may not be replicated in copying a particle. It may be that the donor theme has some special CSS styling for a page/location where that particle is used (e.g.It's therefore your responsibility to watch for donor theme updates and see if the particle was changed, meaning that you would then need to update the particle in your recipient theme also. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |