anchor.diff:  }
   ----
   
  -TIP: you can use http://talend.surge.sh/icons/ to identify the one you want to use.
  -
  -== Version and component
  -
  -Not mandatory for the first version but recommended: enforce the version of your component.
  +TIP: You can use http://talend.surge.sh/icons/ to find the icon you want to use.
  +
  +== Enforcing versioning on components
  +
  +It is recommended to enforce the version of your component, event though it is not mandatory for the first version.
   
   [source,java]
   ----
  
positive.code: . Create a package for the actions.
  . Create a package for the component and one sub-package by type of component (input, output, processors, and so on).
  
  == Serialize your configuration
  
  It is recommended to serialize your configuration in order to be able to pass it through other components.
  
  == I/O configuration
  
  When building a new component, the first step is to identify the way it must be configured.
  
  
negative.code:     private MyDataStore datastore;
  }
  ----
  ==== About actions
  
  Input and output components are particular because they can be linked to a set of actions. It is recommended to wire all the actions you can apply to ensure the consumers of your component can provide a rich experience to their users.
  
  The most common actions are the following ones:
  
  [cols="1,1,2,6,6"]
  |====
  