-
Notifications
You must be signed in to change notification settings - Fork 32
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
Assets vs primary configuration.yml #47
Comments
Hey @theoiorga, For global assets, everything that is placed in the following global folder and then is included in every Key Message (Pages) folder during the build process. Example of global folder Please note that this build process pre-dated the option of Shared assets in Veeva, so version 2.0 of this module will have a new way of dealing with shared assets. Please let me know if this helps. -Steve |
@stevebritton , Thank you for the quick response. When should we expect the 2.0 version? Thank you so much for your time, |
Actually, you don't need a .hbs file, you can simply place a pdf in the global folder and reference it like so:
Also, here's an example of a page referencing global assets: Regarding the arrows, the current .js library is programmed to slide through sub slides as well as primary slides (key messages) in a linear fashion. With this functionality in place, I would also disable the Swipe feature in SalesForce as that will ensure the arrows and .js library can handle all of the swipe actions without iRep overriding the gesture. For version 2.0, we don't have any hard set dates nailed down; however, I'll be sure to ping you once it's "production ready". -Steve |
@stevebritton and where would I need to reference it? |
Considering configuration.yml file, I understand that
primary
is the pages directory in which you create each slide, but what about theassets
, where do we create those PI and patient brochure?Thanks
The text was updated successfully, but these errors were encountered: