Naming Conventions
Naming Convention for the Components
- Use the
{Component name}Wrapper.JSX
for the Base Component. The Base components like ButtonWrapper will not be used directly in any of the component. e.g: ButtonWrapper which will not be directly used instead Button with additional behavior or styles added
- Do NOT use
{Component name}Wrapper.JSX
-
For the components that can be used directly in to the other Components e.g: ListItem, Checkbox e.t.c. Here the ListItem can be used in the CollapsibleListItem, SiteMapSearchResults.
-
When a Component is exported through
index.jsx
Folder Names
-
Top Level Folders: All the top level folders namely assets, components, docs, utilities and the atomic folders like atoms, molecules, organisms, templates will be in camel case
-
Component Folders: All the component folders need to follow the Camel Case

File Names
-
Component Files should follow the Pascal case
-
All the non component files like docs and .js files should go with Camel Case
Storybook Component/Story naming
- Component name in storybook should match with the actual exported component Name e.g. MenuList is the actual Component name but in storybook shown as MenuLists
export default {
title: 'Components/Atoms/MenuList',
component: MenuList
};
- The story name should be 'Playground' if it capable of changing it features when user changes the properties