When we consider a new option for the embed block, the goals are to ensure it meets our criteria and serves the broader Yale community. We also want to provide insight into how we govern potential new features on the YaleSites platform. We encourage you to consider the following questions:
Is the application you want to embed applicable to other groups across the university?
One of the principles of the YaleSites platform is Uniformity. This means we strive to offer a consistent experience to all community members. Our unified open-source codebase allows us to introduce new features that become instantly available to all YaleSites, benefiting everyone. We aim to support embed options that serve not only the users requesting them, but also our broader community of site builders. Moreover, we strive to avoid supporting multiple options for the same function. When considering an application integration, it’s essential to assess its relevance to various university groups. Broadly applicable integrations promote collaboration and ensure efficient resource use.
Is there an already an existing way to represent this content through other means?
Before embedding an application, it’s crucial to evaluate if the content it provides can be represented in a more streamlined way. Does this content need to be embedded here, or could we link out to an external URL with a button block? This avoids cluttering the website with unnecessary embeds and keeps the interface user-friendly.
Another thing to keep in mind when thinking about the content you’re embedding is whether this content is public. Content behind a login that only a select number of users can access would not be a good representation of that content.
Is embedding this application an accessibility liability?
Accessibility is a key principle of the YaleSites platform. It ensures that all users, regardless of their abilities or disabilities, can interact with and build a YaleSite. However, in the modern digital landscape, many of today’s popular embedded content solutions unfortunately do not meet these accessibility standards. Our dedicated accessibility team ensures that any supported embed option for the YaleSites platform will be usable for all users.
Is embedding this application a security liability?
Security is paramount when embedding applications. The embedded content must not pose any security risks, such as exposing sensitive data or providing loopholes for cyber-attacks. YaleSites is purpose-built for handling data classified as low-risk, ensuring a secure environment for your web content needs. For more information about low-risk data, view Yale’s Data Classification Guideline.
