anchor.diff:    feature_c:
       state: ready_for_release
       description: This turns on feature c
  -    ```
  +~~~~
  +
   
   **Some things you should consider when implementing feature toggles:**
   
  
positive.code: 
  In trunk based development (TBD), developers collaborate on code in a single branch called “trunk”. The key benefit is to avoid drift in development branches and the resulting merge hell. 
  
  TRUNK BASED DEV IMAGE HERE
  
  This is contrary to the practice of maintaining long-lived feature and release branches. In a branching model, though you may be running builds on individual branches, arguably you aren’t doing continuous integration. In trunk based development, you should never find your trunk in a state where your CD process is unable to deploy. All code should be checked into trunk, built and tested constantly, and the codebase deployable on demand: all of this make CD a reality.
  
  TBD results in much simpler CD workflows: you don’t have to build multiple branches in parallel, map branches to environments and re-test when the same features get merged to trunk. Simplifying workflows is very important in the context of microservices, as the complexity is exasperated as the number of microservices grows. 
  
  Feature toggles is an important technique for TBD. 
  
  
  ##Feature Toggles
  
negative.code: 
  Here is a very simple example. The team are working on four features for the same application: search, menu, sign-in and in-app chat. The in-app chat feature is incomplete (but you still check into trunk in TBD) or you find issues with the in-app chat in pre-production testing. With feature toggles, you can simply turn in-app chat off, even at run time. 
  
  <img src="/assets/images/blog/cd-considerations/feature-toggles.png" alt="Feature Toggles"/>
  
  Feature toggles are usually stored in a specification or configuration file close to the codebase and used by automation in the CD pipeline to turn toggles on in specific environments. They are just conditions in your code base.You should separate setting these toggles from the actual release process so that you can control it in run time. 
  
  ~~~~
  feature_a:
      state: in_dev
      description: This turns on feature a
    feature_b:
  