Libraries tagged by unordered list

Simple, immutable data structures

Go to Download

Display an HTML menu using unordered lists

Go to Download

Convert an associative Array to a UL for display in the CMS and elsewhere

Go to Download

Data structures for PHP language

Go to Download

Special TinyMCE plugin to add more advanced options to the ordered and unordered list buttons.

Go to Download

Simple, immutable data structures

Go to Download

The yii2-treeview widget is a Yii 2 wrapper for the [Treeview](http://bassistance.de/jquery-plugins/jquery-plugin-treeview/). Transform an unordered list into an expandable and collapsable tree, great for unobtrusive navigation enhancements. Supports both location and cookie based persistence.

Go to Download

The Nodeum API makes it easy to tap into the digital data mesh that runs across your organisation. Make requests to our API endpoints and we’ll give you everything you need to interconnect your business workflows with your storage. All production API requests are made to: http://nodeumhostname/api/ The current production version of the API is v1. **REST** The Nodeum API is a RESTful API. This means that the API is designed to allow you to get, create, update, & delete objects with the HTTP verbs GET, POST, PUT, PATCH, & DELETE. **JSON** The Nodeum API speaks exclusively in JSON. This means that you should always set the Content-Type header to application/json to ensure that your requests are properly accepted and processed by the API. **Authentication** All API calls require user-password authentication. **Cross-Origin Resource Sharing** The Nodeum API supports CORS for communicating from Javascript for these endpoints. You will need to specify an Origin URI when creating your application to allow for CORS to be whitelisted for your domain. **Pagination** Some endpoints such as File Listing return a potentially lengthy array of objects. In order to keep the response sizes manageable the API will take advantage of pagination. Pagination is a mechanism for returning a subset of the results for a request and allowing for subsequent requests to “page” through the rest of the results until the end is reached. Paginated endpoints follow a standard interface that accepts two query parameters, limit and offset, and return a payload that follows a standard form. These parameters names and their behavior are borrowed from SQL LIMIT and OFFSET keywords. **Versioning** The Nodeum API is constantly being worked on to add features, make improvements, and fix bugs. This means that you should expect changes to be introduced and documented. However, there are some changes or additions that are considered backwards-compatible and your applications should be flexible enough to handle them. These include: - Adding new endpoints to the API - Adding new attributes to the response of an existing endpoint - Changing the order of attributes of responses (JSON by definition is an object of unordered key/value pairs) **Filter parameters** When browsing a list of items, multiple filter parameters may be applied. Some operators can be added to the value as a prefix: - `=` value is equal. Default operator, may be omitted - `!=` value is different - `>` greater than - `>=` greater than or equal - `=` lower than or equal - `>

Go to Download

Sequence plugin for CakePHP to maintain ordered list of records

Go to Download

A collection of array sorting transforms and functions

Go to Download

Extension for league/commonmark to support additional numbering types for ordered lists

Go to Download

PSR-14 event dispatcher for PHP with priority-ordered listeners, type-hierarchy matching, stoppable events, and deferred dispatch via EventCollector; a building block of the open-source foundation that Jardis-generated DDD code runs on

Go to Download

Lexicographic order calculator, useful for persisting ordered lists.

Go to Download

A PHP port of LexoRank - a ranking system that uses strings to maintain ordered lists

Go to Download

Accept Header toolbox 🧰 to Laravel. Validation and interpretation based on RFC 7231, section 5.3.1 and 5.3.2. Conversion of the list of media types to ordered Laravel Collections (by priority, according to RFC).

Go to Download