Elephant Web Admin API is a new set of tools for creating pages and editing contents in a single place.

The main goal of the API is simplifying tasks and providing web pages with the same features other modules already have. For one, the EWiki.

New features

Context admin

• Layout attributes, including the template root choice.
• Integration with the Elephant i18n API.

Content admin

• Editable with the application Wiki Editor.
• Access to full-featured repository.
• Easy navigation among page versions.
• Versions within the same session auto-removed by default.

Elephant Configuration Files contain information about what's internally happening when delivering content, reading databases or sending emails.

Configuration files are classified into different roots, and developed into specific branches, with meaningful names. This table explains the roots.

Terms of Use

Files in this folder, can be .txt, .html and .wiki. Each type will be interpreted as expected by the file's extension. The result will be a dialog with as many tabs as files encountered, being the name in the tab, the file's name.

Welcome

Files in this folder, can be extra.txt or extra.wiki. Each type will be interpreted as expected by the file's extension. The result will be added to the welcome email.

The text file will integrate into the email with default size and font. The wiki file is expected to include wiki with email compatible syntax.

Elephant Configurator is a file based configuration tool. The main intention is to encapsulate Elephant site properties. The tool uses a map of keys, values, contextual help and triggers. This is a list of keys, and their use within Elephant based modules, including the BrightSide libraries. This feature is only available to superuser.

Elephant Templates are fully responsive by default, using the CSS/JavaScript framework Fomantic-UI.

Since version 3, Elephant introduces two different types of responsiveness, browser-based as server-based.

Browser-based

Browser-based responsiveness is mainly provided by the standard templates + Fomantic-UI. The templates provide the necessary information to the browser, to adjust components for different screen sizes. The browser is then capable of restructure the content dinamically, without reloading the page.

To try the browser-based responsiveness, resize the browser window. You will see how components change, stacking columns, or changing the main menu type when the size resembles a cellphone device.

Server-based

Server-based responsiveness is controlled by the server side. Allows to provide different content depending on user roles, dao-iterators or dynamic macros.

Server-based responsiveness ensures that site visitors only receive the content addressed to their role or current device. The main difference with browser-based responsiveness is that the browser only receives the appropiate source-content.

Server-driven context

A server-driven context is an extension of the server-based responsiveness. Context server-driven property must be set by the Superuser.

Contexts with this property set to true, can use conditionals inside the EWiki content. Examples would be:

@s{if mobile}
  ... /* this content will be sent only to mobile devices */
@s{/if}

@s{if rolemap['@partner:on']}
  ... /* this content will be sent only to partners */
@s{/if}

Elephant Security Locks were introduced in 2020, to mitigate malicious attempts to access the website. Currently, the API uses different layers to protect the resources, the Security Locks themselves, and the Take a Nap system.

Security Locks

The Security Locks, block IPs permanently for specific reasons. The system activate the Security Locks by default.

Take a Nap

Take a Nap is a more flexible system, with a bigger scope. Recognizes two status, at peace and not at peace. When not at peace, the system forces Elephant is taking a nap status. The status is not absolute, not wide range, and won't be detailed here for obvious reasons.