When an image is replaced directly in OpenAsset (ex: downloaded out of OpenAsset → edited in PhotoShop → replaced using the "Replace" feature on the file page), this will sync back to WordPress.

The following auto-sync options are available within the plugin:

8 Hours | 24 Hours

Re-syncing does NOT sync everything. Each item is checked to see if it’s changed on the OpenAsset side. If a particular field is updated on one project/employee record, all the fields for that one project will get updated. This is based on an “updated date” field on the projects.

Currently the plugin only enables syncing of image files, although further file types may be supported in the future.

The plugin will sync image sizes that offer maximum flexibility for you to display images however you need. Sizes are selected as being the closest to 2000x2000px, up to 3.15MB as jpg, gif or png. In order to optimize images for webpage display we recommend that your web developer uses the Wordpress built in image resizing as documented here. The bundled templates that come with the plugin use this resizing method.

Although there is no set limit, we advise not syncing more than 500 Project & Employee records total.

The plugin will sync image sizes that offer maximum flexibility for you to display images however you need. Sizes are selected as being the closest to 2000x2000px, up to 3.15MB as jpg, gif or png. In order to optimize images for webpage display we recommend that your web developer uses the Wordpress built in image resizing as documented here.

Users will be able to control which OpenAsset fields are populated via the plugin dashboard. All of the fields/files are dynamic based on your instance EXCEPT for the File Field options.

No. The plugin is not currently available with Multisite Network configurations.

We’ve followed best practices throughout and thoroughly tested the plugin prior to launch, however it is difficult to confirm the compatibility with the vast number of plugins and tools available.

The current version of the plugin is designed to help populate the imagery and project/employee data in unison on the experience pages of your website. At this time, it is not configured to streamline image management only on the website. This is feedback we can consider for future versions of the plugin.

This plugin is an out-of-the-box plugin that is purposely built for OpenAsset and Wordpress.

To use the plugin, you need to be an OpenAsset user and leveraging Wordpress as your content management system (CMS).

The plugin is downloaded to the Wordpress Dashboard form the Wordpress Marketplace

The plugin connects to your OpenAsset instance and enables you to configure the OpenAsset data that you would like to sync to your Wordpress site. This data includes Projects, Employees, Roles and Images along with metadata.

Integrating the plugin will require time from your web developer. There are 2 options for integration. There is a simple template that you are free to modify with your website style and branding, or your web developer is able to use data points from the plugin and integrate them into your custom website UI.

Once installed, you will be able to control the projects, employees and images from within OpenAsset. The plugin will automatically update your Wordpress database with data and files from OpenAsset. You can define which cadence sync you wish from preset options, or sync manually.

Data and files are pulled from OpenAsset and stored in your Wordpress Media Library .

The data is synced to the Wordpress database once the plugin is configured and synced.

The files will be removed from the Media Library.

While the plugin itself is available for free on the Wordpress app store, using the plugin with the OpenAsset API requires a license that is charged as an add-on to your OpenAsset subscription.

Yes, the OpenAsset Wordpress Plugin comes with a set of simple UI templates. These serve to get you up and running with a quick proof of concept or can be modified by a web developer to align with your company's branding and integrate into your existing site.

Absolutely! As a Wordpress user, the plugin allows your web developer to integrate into any custom website layout. Read more about this here.

You are able to configure the website section name to whatever you wish.

For example, you may want to call the section about your Employees “Team”. This will then be used in the URL.

For the individual pages, slugs will automatically be created based on the Project or Employee name. You are then able to rename these slugs within Wordpress.

The templates provided with the plugin will work on a range of screen sizes, including mobile and tablet. If you integrate the plugin’s data to your bespoke website frontend, your web developer will need to address mobile compatibility.

Localization is determined by the language the information is captured within OpenAsset. For example, if Project Description in OpenAsset is captured in Spanish, it will appear in Spanish on the website. Please note: there could be service settings or translation tools that would alter this.

Our team's recommendation is to get familiar with the Wordpress Plugin as you scope out your website refresh project to map out what the pages will look like. This way you will know what information is needed in OpenAsset and you can align the web page layout with how the Plugin works. Your web developers can take a look at the Plugin early on in a staging environment to gain familiarity with it. If you proceed later, it may feel like you are redoing your site twice rather than just once.

The plugin will not impact SEO or how the web page(s) are “crawled”. SEO enhancements are managed in the overall page layout and choices the developer makes.

The plugin focuses on pulling images from OpenAsset to help build the project and employee experience pages. You do not have to leverage the plugin for ALL images on a website.

The plugin and OpenAsset configuration provide you with control over the images you want to leverage on your experience pages (via sorting options and file fields).

For explicit control, users can leverage a file field in OA to distinguish which images "Show on Website".

Yes.

Users can control which fields are populated from the Plugin UI

The pilot program confirmed the plugin requires a web developer for primary implementation.

Much of the feedback we received was related to minor updates to our documentation to enhance the experience when referencing help articles.

We also received recommendations to improve the branded templates UI/layout

The plugin delivers value in the current state.

Our recommendation with the plugin now is to share the technical documentation we have with your web developer to get a better understanding of the time it would take to implement based on your specific needs.

Configuring the plugin settings the team can review.

Custom Layout Instructions the web developer can review.

One of the web developers involved in the pilot program said it took 3-5 hours to implement the preset template to a staging environment.

At this point in time we do not have a live example. We can show the "raw" branded template page that they can stylize and brand.

Branded Template Instructions the web developer can review.

No. File images set to Show on Website = "Yes" will not appear in the WordPress media library if the Project is not set to Show on Website = “Yes.”

Your website needs to be running at least Wordpress 6.0 and PHP 8.0.

When a new version of the OpenAsset plugin is available, your Wordpress admin will be notified from within Wordpress using the standard methods. Your Wordpress admin will be able to download and update the plugin directly within Wordpress.

Please see our available support articles for installation and setup below:

No, you will need the help of your web development team to either integrate the bundled templates or integrate the data points into your custom website.

No. The plugin is not currently available with Multisite Network configurations.

Wordpress falls under step 3. Configuration in the onboarding process