Skip to content

Libraries

Libraries lets administrators register reusable resources such as JavaScript files, stylesheets, or fonts so they can be used throughout the application.

Open Operations → Libraries.

Use this page when forms or scripts depend on shared front-end or script resources.

Typical Uses

  • add a third-party JavaScript library
  • add shared CSS
  • add font resources
  • make a script available to server-side execution

Resources can be defined either by storing their content directly in Emakin or by linking to an external URL.

Note: If an external URL is used, all users must be able to reach that URL.

Settings Reference

Is Enabled?

Controls whether the library is active and included.

Name

Descriptive name used for identification in administration. It does not change how the resource is rendered.

Path

For JavaScript, CSS, or font resources, enter the URL of the library file, for example /file/<id> or an external URL. The field is not shown for server-only libraries. For Package resources, enter the package name instead.

Type

Defines the resource type: JavaScript, CSS, Font, or Package.

Render Type

Defines where the library should be available:

  • Client Side: included in HTML so client-side JavaScript can use it
  • Server Side: available to server-side scripts
  • Both Client and Server Side: makes supported URL-based resources available in both contexts

For a server-only JavaScript or CSS library, store the source in Content. A JavaScript library without a path can only use the client-side render type.

Content

Inline JavaScript or CSS source. This is available for JavaScript and CSS entries when the resource configuration permits inline content. Fonts and packages use their configured path instead.