Please enable JavaScript.
Coggle requires JavaScript to display documents.
How to remove custom thymeleaf beans from widgets (What are all the beans?…
How to remove custom thymeleaf beans from widgets
Can we remove all of them?
Remove all except
component
content
What are all the beans?
component
widget's way of retrieving
components
Why is this needed?
asset
talks to CMS
content
retrieves ContentDataModel
metadata
navigation
talks to NavigationWebService
events
talks to EventReg
trips
talks to TripsWebService
article
Talks to CMS to get article metadata
proxyable
generic call to retrieve data from
various services
brand
gets brand-landing
related content
only in rei.com
inspire
gets inspriational(?) type of data
who would use this?
Currently, it only retrieves
content from EventReg
Need Monitoring set up
What does monitoring
mean in this aspect?
CMS gets notified when changes
occur that relate to the annotated
What constitutes as a change?
new one gets introduced
an annotation (or numerous annotations)
are removed
Dashboard
What kind of dashboard is needed?
count of all annotated beans
how can we do this?
count of all widgets using annotated beans
How can we do this?
count of all page configs with widgets that have annotated beans
Add performance enhancements
maintain consistency
with what?
an annotated bean referenced multiple times
within a widget
in multiple widgets within the same page cofig
within a ContentDataModel
Anywhere else?
how can we prove these features are actually enhancing page loading times?
A naming convention is chosen for model
why is this important?
our widget creators/maintainers need to know
the way to get the models that get created
What are some naming conventions?
Where will the annotated beans move to?
In Hippo
As a list of key/value pairs in ContentDataModel property
As a list of key/value pairs in a ComponentConfig
as a list of key/value pairs in page-configs
Can these values be verified pre-render time?
no
This is true currently
Key/value pairs could be written like proxyable
How will users know what to put in this list?
How can this solution support dynamic content?
What is dynamic content in this aspect?
Do we need to worry about this now?
This could be a
want
instead of a
must
Where will the 'dynamic' content come from?
Needs to be backwards compatible
The current way needs to be supported
moving forward
how to do achieve this?
What downstream changes
are needed?
CMS to support Hippo changes
Components
how?
retrieves new key/value pair
from CMS and does something
similar to proxyable to get content
data retrieved gets injected into
the model
rei.com
how?
How to tackle recursive calls?
What constitutes as a
recursive call?