These days the standard way to get your java libraries is through Maven. However, sometimes you still need to deal with jar files that aren’t available through Maven at all. Perhaps some software vendor has provided a set of jars, or you have a custom build that you aren’t allowed to publish at all.
If this is the case, you could just reference the jars on the file system, the old school approach. But you can also mavenize them yourself, and store them in your local Maven repository (which can be found in your user profile folder, in the folder .m2). That makes it possible to reference these libraries in a pom.xml or in a build.gradle file, giving you all the advantages of modern dependency management.
SDL is conducting a series of webinars ahead of the release of SDL Tridion Sites 9 later this year. Recordings of the webinars are made available by SDL. The upcoming release is an important milestone for SDL Tridion DX, which integrates SDL Tridion Sites (formerly known as SDL Web) and SDL Tridion Docs (formerly SDL Knowledge Center), to define digital experiences on a global scale.
In version 2 of SDL’s Digital Experience Accelerator (mostly referred to as DXA), SDL introduced the DXA resolver. Customizing the resolving process can be used to manipulate the list of items to publish that results from a publish action.
“EditFrames in the Experience Editor is a feature that you can use to give users front-end access to fields that are not directly accessible, either because they are not visible or they are of a type that are not directly front-end editable.”
When editing a component using EditFrames or the Editor Button, the component datasource does not refresh. To do this, you have to save the page first, followed by reloading the page with the latest changes, which is cumbersome for content editors.