Libraries tagged by page sections
fabrizio/commentator
2 Downloads
A Laravel package that lets you add a comment section to your pages.
fuhton/simple-admin
7 Downloads
An admin section for selected pages.
utsavrock1811/magento2-checkout-customisation
5 Downloads
Magento 2 Add custom text under the 'ship to' section of order summary page on checkout page
sunnysideup/membersonlypages
34 Downloads
This helps you create a section of Members Only pages, by adding a special usergroups. This is ideal for setting up an intranet. That is, not just anyone can access the pages. You have to be either an admin OR a member of the specified group.
sunnysideup/membersonly
29 Downloads
This helps you create a section of Members Only pages, by adding a special usergroups. This is ideal for setting up an intranet. That is, not just anyone can access the pages. You have to be either an admin OR a member of the specified group.
sunnysideup/membermanagement
18 Downloads
This helps you create a section of Members Only pages, by adding a special usergroups. This is ideal for setting up an intranet. That is, not just anyone can access the pages. You have to be either an admin OR a member of the specified group.
magexpertise/checkout
5 Downloads
Magento 2 Add custom text under the 'ship to' section of order summary page on checkout page
rabble/preview-bundle
37 Downloads
Adds a preview to the content section when editing or creating a page in the content bundle.
andrewhoule/silverstripe-basicnews
392 Downloads
Creates a basic news section (news holder and sub news pages).
qbus/contao-inherit-fallback-articles
62 Downloads
Inherit articles when a page has no articles for a particular layout section.
qbus/contao-home-fallback-articles
0 Downloads
Get articles from the home page as a fallback when a page has no articles for a particular layout section.
qbus/contao-fallback-articles
72 Downloads
A basis for defining methods that can get fallback articles when a page has no articles for a particular layout section.
matthewbaggett/docker-api-php-client
6 Downloads
The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.43) is used. For example, calling `/info` is the same as calling `/v1.43/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```
mageinic/hyva-faq
0 Downloads
FAQ by MageINIC. Product FAQ empowers you to effortlessly create and manage a comprehensive FAQ section, enhancing customer satisfaction and conversion rates. Organize FAQs into categories, use expandable sections for detailed answers, and seamlessly integrate FAQs into product pages.
mageinic/faq
4 Downloads
FAQ by MageINIC. Product FAQ empowers you to effortlessly create and manage a comprehensive FAQ section, enhancing customer satisfaction and conversion rates. Organize FAQs into categories, use expandable sections for detailed answers, and seamlessly integrate FAQs into product pages.