What brand comes to mind when you see the following image?
Your unique brand (e.g. colors, fonts, illustrations) is an indication to customers that they are interacting with your company. Over time, your users become familiar with the look of your application and it becomes second nature. For some, the brand colors are so ingrained into their minds that when they appear in different contexts, images of your product flood their memory. It’s likely that you immediately recognized Google’s colors above without so much as a second thought.
Your brand image is your company’s identity to customers, and users expect consistency throughout every flow. That’s why OneSchema’s Branding Suite feature includes over 20 customizations, enabling your CSV importer to seamlessly fit in with the rest of your design.
You can access our Branding Suite via the “Customizations” tab in your dashboard, which gives you the ability to set:
Using LinkedIn as an example, let’s walk through how to use each customization option. You can follow along with the video here or the steps below to see that with just a few key updates, OneSchema’s Embedded Importer quickly transforms to match the design of LinkedIn.
We’ll start in OneSchema’s Customizations suite with default values.
The first option under General is the primary color, which takes in HEX color codes. We’ll start by replacing the default value with LinkedIn’s primary blue color, #0A66C2. Next, in the Buttons section we’ll use the same primary color and adjust the button radius to 0, which will make the buttons square.
Since LinkedIn’s red and yellow vary slightly from OneSchema’s default colors, we’ll replace the error and warning state colors respectively. We’ll also use LinkedIn’s light grey to style the secondary and tertiary buttons.
Our third and final step is to switch to LinkedIn’s font, which is called “Source Sans Pro”. While we’re sticking with the default font colors here, the Customizations options allow for changing each color which may show up. Even the placeholder font color, which is only visible when specific errors exist in the data, can be specified. We’ll set the font URL and family and have our final product.
OneSchema allows every color to be changed, and the image on the first pane can be replaced, and even the border lines can be customized. With just a few minutes of simple adjustments, your users won’t be able to notice a difference between your core product and your importer.
{{blog-content-cta}}
What brand comes to mind when you see the following image?
Your unique brand (e.g. colors, fonts, illustrations) is an indication to customers that they are interacting with your company. Over time, your users become familiar with the look of your application and it becomes second nature. For some, the brand colors are so ingrained into their minds that when they appear in different contexts, images of your product flood their memory. It’s likely that you immediately recognized Google’s colors above without so much as a second thought.
Your brand image is your company’s identity to customers, and users expect consistency throughout every flow. That’s why OneSchema’s Branding Suite feature includes over 20 customizations, enabling your CSV importer to seamlessly fit in with the rest of your design.
You can access our Branding Suite via the “Customizations” tab in your dashboard, which gives you the ability to set:
Using LinkedIn as an example, let’s walk through how to use each customization option. You can follow along with the video here or the steps below to see that with just a few key updates, OneSchema’s Embedded Importer quickly transforms to match the design of LinkedIn.
We’ll start in OneSchema’s Customizations suite with default values.
The first option under General is the primary color, which takes in HEX color codes. We’ll start by replacing the default value with LinkedIn’s primary blue color, #0A66C2. Next, in the Buttons section we’ll use the same primary color and adjust the button radius to 0, which will make the buttons square.
Since LinkedIn’s red and yellow vary slightly from OneSchema’s default colors, we’ll replace the error and warning state colors respectively. We’ll also use LinkedIn’s light grey to style the secondary and tertiary buttons.
Our third and final step is to switch to LinkedIn’s font, which is called “Source Sans Pro”. While we’re sticking with the default font colors here, the Customizations options allow for changing each color which may show up. Even the placeholder font color, which is only visible when specific errors exist in the data, can be specified. We’ll set the font URL and family and have our final product.
OneSchema allows every color to be changed, and the image on the first pane can be replaced, and even the border lines can be customized. With just a few minutes of simple adjustments, your users won’t be able to notice a difference between your core product and your importer.
{{blog-content-cta}}
