Codebots taxonomy

by Lana Brindley, Nov 02, 2017

To create with Codebots, you need to tell the bots not only what you want your project to look like, but also how the underlying technology will fit together. You can give the bots instructions in a number of different ways: to start with you create your initial project, and then you can create epics and user stories in the Stories Backlog. To describe what you want your project to look like, and to design any database interactions, you use the Diagram Editor. This is a drag-and-drop interface.

There are a number of different segments that are used to build a Codebots application within the Diagram Editor. You can put these segments together in different ways, in order to ask the bot to do different things.

How Codebots works

Elements and components

The smallest segment of a Codebots application is an element. This is usually something like a button or box for text. If you put a couple of elements together, then you have a component. Components are combinations of elements, like an icon with a name next to it, or an input box with a save button.

Views and tiles

You can then combine components into views. A view will usually have a few different components, such as some text, an image with a caption, and maybe a space for someone to type their email address with a button to sign up for a newsletter. Views can then be grouped together into tiles, which help you organise them in your application.


The most powerful segment is a plugin, which is a group of tiles all combined to deliver a particular function. Some of the most useful plugins are already created for you to use and can do things like capture and serve documents to your users, make a timeline of events or a calendar, create a menu, or show a list of products with images. Once you know what you want your application to do, you can move plugins into place, and the codebots will write the code to be able to deliver that information to your users.
Click here for more answers on what is Codebots.