Marketplace DAM App Boilerplate

A boilerplate streamlines your workflow with pre-configured templates, ensuring rapid development and seamless integration within the Contentstack's Developer Hub. It elevates digital asset management capabilities and enhances content delivery across diverse platforms.

They can define project-level elements or standard methods for one or more projects.

The following guide shows how to build a DAM (Digital Asset Management) Marketplace app using our Marketplace DAM App Boilerplate. For more information about the Marketplace DAM App Boilerplate, you can check the GitHub repository here.

Why should you use the Marketplace DAM App Boilerplate?

• The DAM app boilerplate provides a standard code structure for all the required UI locations of a DAM app. You can quickly start developing the app by changing the root_config files as needed for the third-party DAM application.
• Creating an application is quick since you only need to modify the required functions in root_config for your UI locations to work.
• We have built a boilerplate that incorporates all the best practices you can use while building your application in Contentstack.
• With this boilerplate, you can save a considerable amount of development time when building a third-party DAM Application.
• The boilerplate uses the Venus Components Library to make your application correspond with our new Contentstack user interface.

Structure of the Marketplace App Boilerplate

The boilerplate folder structure consists of relative files and references, making it easy to acclimate within your project.

Additional Resource: To view the folder structure, please refer to the README.md file.

Below are the app routes for each location in App.tsx:

function App() {
  return (
    <ErrorBoundary>
        <HashRouter>
          <MarketplaceAppProvider>
            <Routes>
             <Route
                path="/config"
                element={
                    <Suspense fallback={<ConfigLoader />}>
                    <AppConfigProvider>
                      <ConfigScreen />
                    </AppConfigProvider>
                  </Suspense>
                }
              />
              <Route
                path="/custom-field"
                element={ 
                    <Suspense fallback={<CustomFieldLoader />}>
                    <CustomFieldProvider>
                      <CustomField />
                    </CustomFieldProvider>
                  </Suspense>
                }
              />
              <Route
                  path="/selector-page" 
                  element={
                    <Suspense fallback={<SelectorPageLoader />}>
                    <SelectorPage />
                  </Suspense>
                }
              />
            </Routes>
          </MarketplaceAppProvider>
        </HashRouter>
      </ErrorBoundary>
  );
}

Using Marketplace DAM App Boilerplate to Develop Custom Applications

To get started with building applications using the boilerplate, follow the steps given below:

Prerequisites

• Contentstack account
• Knowledge of ReactApp Framework and App Development
• Reference to App SDK

Install Dependencies

• Navigate to the root directory of the downloaded zip file.
• Run the following command to install the necessary packages:

In the terminal, go to the APP_DIRECTORY and install the necessary dependencies.

cd <APP_DIRECTORY>

npm i

For UI

1. To install the necessary packages for the UI, navigate to the UI folder.
   cd <APP_DIRECTORY>/ui
   

   npm i
   

2. Once the packages are installed, run the following command in the UI folder to get started. The UI server will start at port 4000.

   For Linux/MacOS:

   npm run start
   

   For Windows:

   npm run winStart
   

For RTE

1. To install the necessary packages for the JSON RTE, navigate to the RTE folder.
   cd <APP_DIRECTORY>/ui/rte
   

   npm i
   

2. After you install the packages, run the following command in the RTE folder to get started. The RTE server will start at port 1268.
   npm run start
   

Note: Add .env files to UI and JSON RTE before starting the server. The .env values are mentioned in the README.md file.

Warning: The UI and RTE are accessible on different ports.

Creating a Project Using The Boilerplate

To use your application, you need to set it up in Contentstack. To do so, perform the steps given below:

1. Log in to your Contentstack account.
2. In the left-hand-side primary navigation, click the Developer Hub icon to go to the Developer Hub.
3. Click the + New App button.
4. In the New App modal, select Stack App as the Type of App. Enter a suitable Name for your app and an optional Description, and then click the Create button. By default, the Status of the created app will be Private.
   

   Warning: While selecting the Type of App in the above step, ensure you select Stack App, as this boilerplate supports stack apps only.

5. On the resulting Basic information page, upload your app’s icon and Save the changes.
   
   
6. Click the UI Locations tab. To set the App URL, click the View Hosting Settings link. You will be redirected to the Hosting tab. On the resulting page, enter the App URL. In the development phase, this will be the UI server URL i.e,
   http://localhost:4000/#
   
   
7. Add the UI locations for your app, as per your requirement, inside the App location(s) option. The DAM template supports the following 3 UI locations:
   1. App Configuration
   2. Custom Field
   3. JSON RTE
8. Add the below routes for each UI Location to get the desired results.

   Note: The name for each UI location is optional. By default, the app name is the UI location name.

   1. App Configuration: In the App Configuration UI location, use /config for Path.
      
   2. Custom Field: In the Custom Field UI location, use <Your_App_Name> for Name and /custom-field for Path. Select the Data Type as JSON to store JSON data in your entry.
      

   Note: For configuring JSON RTE UI location, please refer to the Add JSON RTE UI Location section, as it works on different ports.

9. After saving the recently added UI locations, click the Install App button to install the DAM app.
10. Select the stack where you want to install the app, accept the terms of service, and click the Install button.
    
11. You will be redirected to the configuration page of the app. On the Configuration page, enter the following details:
    1. DAM Text Input: You can enter the input text for the Sample DAM app and save the data. You can also use any other app configuration as per your DAM website.
    2. DAM Select Input: You can use the Select Input field to select any option from the dropdown options.
    3. DAM Radio Input: You can use the Radio Input field to choose an option from the given options (Single Select or Multi Select).

    4. Note: You can customize the app configuration with your dedicated fields.

    5. Save in Entry [Mandatory]: If you select the Custom Fields option, you can select the structure of the data you want to save in the entry. If the All Fields option is selected, you might be able to add limited products in the custom field depending on the size of the data (Refer to the Custom Fields Limitations documentation for more details).

12. 

13. Click the Save button and then click Open Stack to start using the application.

Additional Resource: To learn more, refer to the App Configuration document.

Having the basic DAM app setup ready, you can now update root_config files in the UI directories.

Note: You can go through the Template.MD file in our code repository documentation for complete details on root_config and update it as per the DAM platform that you are trying to integrate.

Add JSON RTE UI Location

Before adding the JSON RTE UI Location, you have to update the App URL i.e. http://localhost:1268

Warning: After changing the port for JSON RTE UI location, you will be unable to view the Configuration screen and Custom field. The app configuration settings were already saved at the time of configuring the app, but will not be visible In the development phase.

In the JSON RTE UI Location, use <Your_ App_Name> for Name and /dam.js for Path.

Having the basic DAM app setup ready, you can now update rte_config files in the UI directories.

Note: You can go through the Template.MD file in our code repository documentation for complete details on rte_config and update it as per the DAM platform that you are trying to integrate.

Use the DAM Application within your Stack

To use the DAM application within an entry of your stack, follow the steps given below:

1. Go to your stack, click the Content Models icon in the left navigation panel, and click the + New Content Type button.
2. Create a content type by adding relevant details as displayed below:

3. 

Steps to use the DAM App within the Custom Field

1. In the Content Type Builder page, add a Custom field in your content type by clicking the Insert a field link represented by a + sign.
2. Under Select Extension/App, select names defined for the Custom Field UI location and click the Proceed button.
   This adds the DAM app in the custom field.
   
3. After adding the app in a custom field, click Save or Save and Close to save your changes.
4. To use the DAM app, create an entry for this newly created content type. To do this, in the left navigation panel, navigate to the Entries page, click + New Entry to create a new entry for the above content type, and then click Proceed.
   You can see the DAM app’s custom field on your entry page as shown below:
   
5. Click the + Choose Asset(s) button.
   
6. Select assets from the third-party DAM website to add them to your entry.
   
7. The asset(s) you selected are referenced within your entry. You can reorder the assets to arrange them in required order in both Thumbnail and List views.
   
8. Click Save to save the entry.

Steps to use the DAM App within the JSON RTE

1. In the Content Type Builder page, add a JSON Rich Text Editor field in your content type by clicking the Insert a field link represented by a + sign.
2. Under Select JSON RTE Plugin(s), choose the names defined for the JSON RTE UI location, and then click the Add Plugin(s) button.
   This adds the DAM app in the JSON RTE.
   
3. After adding the app in a custom field, click Save or Save and Close to save your changes.
4. To use the DAM app, create an entry for this newly created content type. To do this, in the left navigation panel, navigate to the Entries page, click + New Entry to create a new entry for the above content type, and then click Proceed.
   You can see the DAM app’s icon in the JSON RTE on your entry page as shown below:
   
5. Click the DAM app's icon.
   
6. Select assets from the third-party DAM website to add them to your entry.
   
7. The asset(s) you select are referenced within your entry. You can reorder the assets to arrange them in the required order within the JSON RTE.
   
8. Click Save to save the entry.

How to Use Predefined Examples in the Marketplace DAM App Boilerplate

You can check examples of some DAM (Digital Asset Management) apps, such as Bynder and Cloudinary in the GitHub code you downloaded to get started.

To do so, follow the steps below:

1. Select the app example and configure the changes:

   For UI

   1. Navigate to the ui > example > sample_dam_app folder and copy the root_config folder.
   2. Navigate to the ui > src folder and replace the root_config folder with the ui > example > sample_dam_app > root_config folder.

   For RTE

   1. Navigate to the ui > example > sample_dam_app folder and copy the rte_config folder.
   2. Navigate to the ui > rte > src folder and replace the rte_config folder with the ui > example > sample_dam_app > rte_config folder.
2. After configuration, restart both the servers for UI and RTE using the npm command as shown in the Install Dependencies section.
3. Navigate to the stack where your application is installed and view your application in the configured UI location.

Additional Resource: To learn about the use of Bynder and Cloudinary DAM apps, please refer to the Bynder App Installation Guide and Cloudinary App Installation Guide.