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

Client resources can be defined by storing their content directly in Emakin or by linking to an external URL. Server-side JavaScript must be stored in Content.

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. For Package resources, enter the client package name that Emakin should require.

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 browser-side code can use it
  • Server Side: imports the stored JavaScript Content into server-side script contexts
  • Both Client and Server Side: applies both behaviors to stored JavaScript content

JavaScript entries without a Path can select Client Side, Server Side, or Both. CSS, Font, Package, and URL-backed JavaScript entries are client-side only. Server-side loading never retrieves the library from Path.

Content

Inline JavaScript or CSS source. For JavaScript, non-empty content is required for Server Side or Both. Fonts and packages use their configured path instead.