Just wondering if we can add more metadata (and complete missing metadata) to extensions, roll manifest to version 1.1 - i know there has also been attempts at how to put commercial extensions in to the extension library also, so here’s some thoughts (other than to rename the ‘applications’ link to ‘extensions’ in v7.x)
Some extensions are missing a category, but I’d suggest we replace category with some kind of tagging instead in version 1.1 of manifests.
Suggesting we should add:
author: the name / org of the author
author_logo_uri: a square logo image
documentation_uri : a link to documentation
source_uri: a link to the source code repository
purchase_uri: a link to purchase a licence
licence_endpoint_uri: a rest endpoint which returns licence validity / gets pinged when extension is installed/uninstalled
tags : tags that help people filter and search for the extension
There could be a list of predefined tags, however people should be able to create their own also so they can have freedom in their own extension repos to choose their own adventure internally.
You will also notice a licence_endpoint_uri which could trigger functionalities with cfadmin tag and admin ui… so to activate licence you could post to endpoint, to check use GET and remove use DELETE verbs on a request to same endpoint, to refresh use PATCH (if you see need for this also), then just add functionality to cfadmin action=“licence” method=“GET” key="{some key string by vendor} - KISS (keep it simple). Vendors could use other methods internally for their components, but the response could also be used to ‘educate’ the admin to licenced versions also, so if you have licence for v1 reponse says valid until: v2, so if version 2 comes out it could notify the admin of new ‘upgrade’.
Could also be used in logic if we had ‘automatically update to latest version’ to not ‘automatically’ update if that flag ‘could’ be set ( update automatically : dot/minor/major )
So PDF extension could add
author: Ortus Solutions
author_logo: https://www.ortussolutions.com/__media/home-carousel/ortus-logo.jpg
author_uri: https://www.ortussolutions.com/
documentation_uri: https://docs.ortussolutions.com/ortuspdf/2.1.0/index.html
source_uri: https://github.com/ortus-docs/ortuspdf
purchase_uri: https://www.ortussolutions.com/products/ortuspdf#buy
licence_endpoint_uri: https://licence.ortussolutions.com/validate/
tags: generator, document, pdf
Example CURRENT manifest:
Manifest-Version: 1.0
Built-Date: 2024-08-08 14:42:40
version: "1.0.1.2-SNAPSHOT"
id: "D6700FE4-E168-4512-9B95E1AE7784A3A5"
name: "AWS Kinesis Resource Extension"
description: "Core Extension to integrate Kinesis into Lucee."
lucee-core-version: "5.0.0.157"
release-type: server
start-bundles: false