Optimizely Graph lets you fetch content and sync data from other Optimizely products. For content search, this lets you create custom search tools that transform user input into a GraphQL query and then process the results into a search results page.
Why use Graph for Content Search?
The benefits of a Optimizely Graph-based search service include:
Let’s explore the steps to make this work using the Alloy project. First, obtain the Content graph keys/secret from Optimizely.
Optimizely.ContentGraph.Cms
package, and note that the Content Delivery API must also be installed as a prerequisite for the graph to function
IServiceCollection
. Additional configuration options are available as needed.Now that the server-side querying is ready, let’s configure the client side to query from the application code.
StrawberryShake.Server
StrawberryShake.Transport.Http
.StrawberryShake.Tools
on the machine
.graphql
file. Create a Queries
folder and place the query file inside it.OptimizelyGraphSingleKeyValue
with the key received from Optimizely (as shown in the appSettings step):
-n AlloyGraphClient
, the generated client will be AddAlloyGraphClient
IAlloyGraphClient
StartPageController
and verify the results
.graphql
query file. If you make any additions or modifications to the query, ensure that the latest schema is downloaded when you rebuild the code
]]>
We recently completed an upgrade project, and one of the notable changes we made was incorporating TinyMCE into its own NuGet package. With the latest version, several adjustments have been made to the implementation process.
During the upgrade, we also had to relocate a custom plugin within the editor. Since I referred to various online sources to execute this, I’ve documented the process below. The implementation involves two key steps:
Step 1: Configuring TinyMCE in Startup.cs within the ConfigureServices method.
Step 2: Implementing the UI side of the plugin.
To begin, as depicted in the image above, you need to register the JavaScript file as an external plugin and ensure it is accessible via the path specified in the AddExternalPlugin
method. In this case, we have a JS file called metricconversion.js
, registered as a plugin with the name metricconvert
, and it is located under the wwwroot
folder according to the provided structure.
Regarding the JS file, it comprises three primary components:
editor.ui.registry.addButton('metricconvert', {})
.editor.ui.registry.addIcon('metric', '<img src="/ClientResources/TinyMce/MetricConversion/images/metric.png" />');
.onAction
method.The final outcome involves:
To facilitate the transition to the latest version of TinyMCE, it’s important to note that several toolbars have been renamed. For more information regarding these changes, you can refer to the following link: TinyMCE Documentation.
This resource will provide you with the necessary insights on the renamed toolbars and their corresponding new names, helping you to adapt to the latest version seamlessly.
]]>The Optimizely Data Platform (ODP) and Google Tag Manager (GTM) are powerful tools for collecting and analyzing data. ODP provides insights into customer behavior, while GTM simplifies managing marketing tags without modifying website code.
What is ODP: ODP allows businesses to collect, aggregate, and analyze data from various sources. It helps optimize marketing campaigns, enhance customer engagement, and drive business growth.
What is GTM?: GTM is a free tool that installs and manages marketing tags without changing website code. It simplifies tracking user actions and collecting data.
In this article we are going to explore simple integration to ODP through Google tag manager as connector. To integrate GTM with ODP, follow these two steps:
Conclusion: