Skip to main content
In this video, I’m going to be demonstrating the KIBO Dev Center. The Dev Center is a centralized location for managing all the different environments needed for development, testing, and deployment of KIBO’s e-commerce solutions. Each Dev Account is associated with a single production tenant. This ensures a clear and controlled relationship between development activities and the live, customer-facing environment. Some Dev Accounts do not have production tenants; for example, a training or implementation partner account. This is common for accounts used for training purposes or by partners who are assisting with the implementation of the platform. In this video, I’m going to be demonstrating the KIBO Dev Center. The Dev Center is a centralized location for managing all the different environments needed for development, testing, and deployment of KIBO’s e-commerce solutions. Each Dev Account is associated with a single production tenant. This ensures a clear and controlled relationship between development activities and the live, customer-facing environment. Some Dev Accounts do not have production tenants; for example, a training or implementation partner account. This is common for accounts used for training purposes or by partners who are assisting with the implementation of the platform. This is the KIBO Dev Center. We’ll discuss each section individually. This is the KIBO Dev Center. We’ll discuss each section individually. First up is the “Develop” menu dropdown, where we’ll walk through both the “Applications” and “Themes” submenus. First up is the “Develop” menu dropdown, where we’ll walk through both the “Applications” and “Themes” submenus. Users can build and install “Applications” in sandboxes to extend the functionality of the KIBO Composable Commerce Platform and integrate with external systems. Users can also browse third-party applications and install them on a sandbox from the App Marketplace.Applications can have multiple versions with behaviors and events specific to each version. Navigating to the “Applications” menu in the Dev Center, we can manage existing applications or create new applications by clicking the “Create Application” button on the top right. We can also install applications to sandboxes, manage application versions, configure behaviors, events, attributes, and capabilities, and submit an application for certification.We’ll cover “Application” creation and management in a separate video. Users can build and install “Applications” in sandboxes to extend the functionality of the KIBO Composable Commerce Platform and integrate with external systems. Users can also browse third-party applications and install them on a sandbox from the App Marketplace. Applications can have multiple versions with behaviors and events specific to each version. Navigating to the “Applications” menu in the Dev Center, we can manage existing applications or create new applications by clicking the “Create Application” button on the top right. We can also install applications to sandboxes, manage application versions, configure behaviors, events, attributes, and capabilities, and submit an application for certification. We’ll cover “Application” creation and management in a separate video. “Themes” contain the design templates of the customer Email templates. We can also modify the look and feel of the Fulfiller Interface by configuring a Theme that includes custom assets.We’ll discuss creating and managing “Themes” in a separate video. “Themes” contain the design templates of the customer Email templates. We can also modify the look and feel of the Fulfiller Interface by configuring a Theme that includes custom assets. We’ll discuss creating and managing “Themes” in a separate video. Next is the “Sandbox” menu. To test “Application” and “Theme” assets we’ve developed, we need to install them on a sandbox. A sandbox simulates a production environment, but is used exclusively for testing and is maintained separately from production environments. We’ll cover how to create and manage “Sandboxes” in a separate video. Next is the “Sandbox” menu. To test “Application” and “Theme” assets we’ve developed, we need to install them on a sandbox. A sandbox simulates a production environment, but is used exclusively for testing and is maintained separately from production environments. We’ll cover how to create and manage “Sandboxes” in a separate video. Next up is the “Projects” menu. “Projects” are optional, but KIBO recommends creating them to group all “Sandboxes”, “Applications”, “Themes”, and team members associated with a particular body of work. Having one location to view and manage the items associated with a project makes managing the project easier.If you are a KIBO partner, we strongly recommend you create a project for each of your clients.We’ll discuss creating and managing “Projects” in a separate video. Next up is the Project’s menu. Menu, projects are optional, but kibo recommends, creating them to group all sandboxes applications themes and team members associated with a particular body of work. Having one location to view and manage the items associated with a project makes managing the project easier. If you are a kibo partner, we strongly recommend, you create a project for each of your clients. We’ll discuss creating and managing projects in a separate video. Next is the “API” menu dropdown, where we’ll look at both the “Limits” and “Docs” submenus. Next is the “API” menu dropdown, where we’ll look at both the “Limits” and “Docs” submenus. Users should self-manage their own tenant to avoid overburdening the KIBO platform and negatively impacting performance for all other users. This is enforced by KIBO’s rate limiting rules, which will reject requests from any tenants that are submitting too many requests to certain API routes within a given time frame.In the sandbox environment, all tenants are grouped together under the same rate limits. If one tenant reaches the limit, then requests on all sandboxes will be rejected. However, tenants are rate limited separately in production environments. If one production tenant reaches a limit, then the restriction will only affect that specific tenant. Rate limits for staging and pre-prod environments also apply per tenant just like production tenants. Rate limits for sandbox, pre-prod, performance testing, and production do not affect each other and are counted separately. The maximum limit can vary depending on the route and is distributed across an entire tenant at any given time. Users should self-manage their own tenant to avoid. Overburdening the kibo platform and negatively impacting performance for all other users. This is enforced by keebos rate, limiting rules, which will reject requests from any tenants that are submitting too many requests to certain API routes within a given time frame. In the sandbox environment. All tenants are grouped together under the same rate limits, If one tenant reaches the limit, then requests on all sandboxes will be rejected. However, tenants are rate limited separately in production environments. If one production tenant reaches a limit, then the Restriction will only affect that specific tenant rate limits for staging and pre-proto, apply per tenant just like production tenants. Rate limits for sandbox pre-produced testing and production do not affect each other and are counted separately. The maximum limit can vary depending on the route and is distributed across an entire tenant at any given time. The “Docs” submenu option under the API menu dropdown navigates users to KIBO API documentation at api docs dot kibo commerce dot com.KIBO’s API documentation page has everything to help users get started with KIBO’s API’s, and even allows users to test API calls directly to a tenant without having to configure applications. The doc Sub menu option under the API menu, dropdown navigates users to kibo API, documentation at API, docs Dot kibo. Commerce.com Kebo’s API documentation page has everything to help users, get started with kibo apis. And even allows users to test API calls directly to a tenant without having to configure applications. Next is the “Logs” menu dropdown, where we’ll review the “Correlation ID Lookup”, “Action Logs” and “HTTP Traffic” submenus. Next is the “Logs” menu dropdown, where we’ll review the “Correlation ID Lookup”, “Action Logs” and “HTTP Traffic” submenus. Error logs provide more detail about why an error occurred and can help users with troubleshooting. When a platform error occurs, the system logs it according to the unique identifier of the associated API request, known as a “Correlation ID”. The “Correlation ID” displays in either the Dev Center UI or API response body, depending on how we’re using the platform. We can enter a “Correlation ID” in this menu in the upper right search bar to retrieve the error log details. Error logs provide more detail about why an error occurred and can help users with troubleshooting. When a platform error occurs, the system logs it according to the unique identifier of the associated API request, known as a “Correlation ID”. The “Correlation ID” displays in either the Dev Center UI or API response body, depending on how we’re using the platform. We can enter a “Correlation ID” in this menu in the upper right search bar to retrieve the error log details. “Action Logs” contain details about custom JavaScript functions that have been developed using the API Extension framework and installed on a tenant.“Action Logs” can tell users when a custom function began or finished executing, how much time it took a custom function to execute, and when and why a custom function failed to execute successfully. “Action Logs” contain details about custom JavaScript functions that have been developed using the API Extension framework and installed on a tenant. “Action Logs” can tell users when a custom function began or finished executing, how much time it took a custom function to execute, and when and why a custom function failed to execute successfully. “HTTP Traffic” metrics are analytics that help users measure their site performance as experienced by visitors. Filters can refine the request data for more specific and custom criteria, while dimensions organize the data based on different categories and support filtering. “HTTP Traffic” metrics are analytics that help users measure their site performance as experienced by visitors. Filters can refine the request data for more specific and custom criteria, while dimensions organize the data based on different categories and support filtering. Next is the “Help” menu dropdown. The “Help” menu contains links to User and Developer documentation based on the topics we just reviewed, such as the “Dev Center”, “Applications”, “Themes”, “API”, and “API Extensions”. In this example, we’ll click “Getting Started” under the “Dev Center” submenu. Next is the “Help” menu dropdown. The “Help” menu contains links to User and Developer documentation based on the topics we just reviewed, such as the “Dev Center”, “Applications”, “Themes”, “API”, and “API Extensions”. In this example, we’ll click “Getting Started” under the “Dev Center” submenu. This opens another tab in the browser with more information on the relevant topic. Here, a user can get more information on how to “Set Up a KIBO Dev Account”. This opens another tab in the browser with more information on the relevant topic. Here, a user can get more information on how to “Set Up a KIBO Dev Account”. The next two menus will cover the “Dev Center” and individual “User” settings. First, we’ll look at the “Dev Center” settings. The name of this menu will vary, depending on what the specific Dev Center is named.For this example, our Dev Center is named “Kibo GTM Demos”. In this menu dropdown, we’ll review the “Account Info” and “Users” submenus. The next two menus will cover the “Dev Center” and individual “User” settings. First, we’ll look at the “Dev Center” settings. The name of this menu will vary, depending on what the specific Dev Center is named. For this example, our Dev Center is named “Kibo GTM Demos”. In this menu dropdown, we’ll review the “Account Info” and “Users” submenus. In the “Account Info” menu, we can manage the “Account Name”. We can also optionally provide “Contact” and “Social Media” information using the side tabs, if applicable. “Account Type” is set when the Dev Center account is initialized, and therefore cannot be changed. In the “Account Info” menu, we can manage the “Account Name”. We can also optionally provide “Contact” and “Social Media” information using the side tabs, if applicable. “Account Type” is set when the Dev Center account is initialized, and therefore cannot be changed. User management allows Account Administrators to add users and assign roles for staff in their organization, grant solution partners or existing users access to sandboxes, and add users to their Dev Center projects. User management allows Account Administrators to add users and assign roles for staff in their organization, grant solution partners or existing users access to sandboxes, and add users to their Dev Center projects. To invite a new user to our Dev Center Account, we’ll click the “Invite User” button on the top right. To invite a new user to our Dev Center Account, we’ll click the “Invite User” button on the top right. This will open a modal window where we’ll input the new users “Email address”, then we’ll select a “User Role” for this user, and then click “Save”. This will send an invite email to the new User that they can click on and continue setting up their user profile.There are five predefined roles that a user can have, each with it’s own permissions. These role permissions cannot be edited. For more information on the KIBO Dev Center User Roles, click the documentation link located on this page. This will open a modal window where we’ll input the new users “Email address”, then we’ll select a “User Role” for this user, and then click “Save”. This will send an invite email to the new User that they can click on and continue setting up their user profile. There are five predefined roles that a user can have, each with it’s own permissions. These role permissions cannot be edited. For more information on the KIBO Dev Center User Roles, click the documentation link located on this page. Lastly, we’ll review the individual “User” settings menu. Again, the name of this menu will vary depending on the user. In this menu dropdown, we’ll review the “My Profile”, “Launchpad”, and “Log Out” submenus. Lastly, we’ll review the individual user settings menu. Again, the name of this menu will vary depending on the user. In this menu drop-down, we’ll review the my profile Launchpad and logout sub-menus. In the “My Profile” menu, a user can edit their “First” and “Last Name” and “Developer Type” definition. “Developer Type” can be “Application Developer”, “Theme Developer”, or both. The user can also optionally add their “Contact Information” using the tabs on the side.“Email Address” is tied to the user account and cannot be changed. Also, a User is not allowed to change their own “User Role”. Should a users role need to be edited, another user on the account with the required permissions will need to make that change. In the “My Profile” menu, a user can edit their “First” and “Last Name” and “Developer Type” definition. “Developer Type” can be “Application Developer”, “Theme Developer”, or both. The user can also optionally add their “Contact Information” using the tabs on the side. “Email Address” is tied to the user account and cannot be changed. Also, a User is not allowed to change their own “User Role”. Should a users role need to be edited, another user on the account with the required permissions will need to make that change. Clicking the Launchpad link under the “User Settings” menu will open up the KIBO Launchpad. Clicking the Launchpad link under the “User Settings” menu will open up the KIBO Launchpad. The “KIBO Launchpad” allows users to navigate to other Developer, Production, or Sandbox environments. For example, if we wanted to navigate into the “Kibo Professional Services” Dev Center, we could do that from the “KIBO Launchpad”.Users will only see and be able to navigate into environments they have been given access to. The “KIBO Launchpad” allows users to navigate to other Developer, Production, or Sandbox environments. For example, if we wanted to navigate into the “Kibo Professional Services” Dev Center, we could do that from the “KIBO Launchpad”. Users will only see and be able to navigate into environments they have been given access to. Lastly, clicking the “Log Out” link will log the user out of the KIBO Platform entirely. If we need to access any part of the KIBO Platform after logging out, we will need to login again. Important Note - For security purposes, KIBO logs users out every 24 hours, regardless of platform usage. Lastly, clicking. The logout link will log the user out of the kibo platform entirely. If we need to access any part of the kibo platform, after logging out, we will need to log in again. Important note. For security purposes, kibo, logs users out every 24 hours, regardless of platform usage.

Want to learn more?

Get Started with Applications

Learn more about this topic

Developer Tools

Learn more about this topic