As discussed previously, Solodev Cloud provides developers with a wide range of infrastructure that will empower them to create various applications or services and provide a dynamic and enjoyable web experience to their clients. Catalogs provide developers with a collection of applications and services that they can use to build their own customized applications. Developers can share these collections with other users via organizations to facilitate collaboration.
Once developers have built their applications, they can become Sellers and distribute their products for purchase via an application catalog or have them featured in the Solodev Store. Catalogs also provide resellers with the ability to sell existing marketing services to their clients in streamlined packages at a margin.
Catalogs are categorized into three types listed below:
Private Catalogs – a library that contains a collection of services and applications that can be used by developers to create their own applications. Used in conjunction with organizations, these libraries can be shared privately with other users to facilitate collaboration or provide other users with catalog offerings for their own projects. Developers are also able to use the private catalogs of other users for their own projects – provided that they are members of the users’ organization.
Application Catalogs – Once their application is ready for deployment to the wider public, developers can monetize their applications by selling them on a private marketplace to their customers or have those same applications whitelisted and featured on the official Solodev Marketplace. Learn more about becoming a Solodev Seller.
Service Catalogs – a library that contains a collection of digital market services that digital advertising agencies can sell to their customers at a margin. Vendors can deploy these services to their customers with minimal configuration – enhancing their clients' digital experience. Learn more about becoming a Solodev Reseller.
After creating a catalog item, the information associated with each catalog item is organized into 7 sections with a number of fields used to market and distinguish your catalog items. A description of the catalog fields associated with each section and fulfillment type are provided below.
Contains the most essential information for catalog items. The fields of the General Information changes depending on the category of fulfillment type chosen. The fields based on each category of fulfillment type are listed below:
General Information fields for Infrastructure and Add-ons fulfillment type:
The title of the catalog item. Reflects the name of the application.
The stock keeping unit for the application.
Adjusts the order of the catalog items in the store. If a rank is not specified, catalog items will be ordered alphabetically in the store.
Adds a dynamic badge to the catalog item allowing the seller or reseller to list their top vendors.
Allows you to choose a fulfillment tag from the Service, Infrastructure or Add-ons categories. This cannot be changed after the catalog item is created.
The author of the service or the application.
The domain or website of the publisher/author of the application.
*The starred fields are fields shared between the Infrastructure, Add-ons and Service fulfillment types.
General Information fields for the Service fulfillment type:
Generates a preview from the code snippets passed in the form specs.
Note: The starred fields are fields shared between the Infrastructure, Add-ons and Service fulfillment types.
Add or delete version numbers for the catalog item’s associated application.
Catalog version numbers
Add/delete version numbers for catalog items and their associated applications.
Add product logos and images to distinguish catalog items and market them to customers. The image fields are provided below:
The logo for the catalog item’s associated product. This will be displayed on the store page or detail header.
Product icon that is displayed on the store page or detail header. If the logo and the icon are the same, upload it in the product logo field.
Product image that is displayed on the store page and replaces the product logo and icon. Used for full images instead of icons or logos like modules.
Product image in detail page.
Provide product descriptions and overviews to distinguish catalog items, product features to market those items to customers, product support text to assist customers and collaborators with application troubleshooting, and product instructions to configure and use the applications associated with catalog items.
Product introduction displayed on the store page. 90-character limit.
Product introduction on the detail page. 200-character limit. Do not use html tags.
Product features section in the detail page. 10,000-character limit.
Product details in the right column of the detail page. 10,000-character limit.
Product support text
Product support content in the detail page. 10,000-character limit.
Product instructions content in the detail page. 10,000-character limit.
Provide licensed or subscription-based services to customers.
Allows sellers and resellers to provide a subscription-based service to their customers for a daily, weekly, monthly, or annual fee.
Allows sellers and resellers to provide a licensed based service to their customers for a one-time fee.
Save changes to catalog items. The options for saving changes are provided below.
Save changes without publishing to the front end.
Makes changes publicly available on the front end.
Set the dates for publication of removal of catalog items.
The start date of publication for the catalog item.
The end date of publication for the catalog item.