anchor.diff:    <apex:slds />
   
       <div class="slds-scope">
  -    	<!-- CONTENT GOES HERE -->	
  +        <!-- CONTENT GOES HERE -->    
       </div>
       
   </apex:page>
   ----
   
  -That's IT! No changes in your controller, only some small changes in the page markup! But if you want to go even further..
  -
  -==== 2. Transform the Visualforce page into set of Lightning Components
  -
  -Well.. sometimes - this is hardcore, especially, if the backend composition is hard and depends on a *viewstate* - because there's no *viewstate* in Lighnting UI. I will not focus on the frontend changes - they will be huge, and they will be different from page to page. Please note, that some things are critically changed, especially input lookup (native one is unavailable) and some chatter vf tags.
  +That's IT! No changes in your controller, only some small changes in the page markup! But if you want to go even further.
  +
  +==== 2. Transform the Visualforce page into a set of Lightning Components
  +
  +Well.. sometimes - this is hardcore, especially, if the backend composition is hard and depends on a *viewstate* - because there's no *viewstate* in Lightning UI. I will not focus on the frontend changes - they will be huge, and they will be different from page to page. Please note, that some things are critically changed, especially input lookup (native one is unavailable) and some chatter vf tags.
   
   But how to transform the backend? At first, we should answer two questions:
  -- Should we use page both on Salesforce Classic and in Lightning UI? If yes, than consider lightning styles for visualforce page. Only do this if you cannot utilize VF page in two different places
  +- Should we use page both on Salesforce Classic and in Lightning UI? If yes, then consider lightning styles for a visualforce page. Only do this if you cannot utilize VF page in two different places
   - Does you backend developed through @RemoteAction annotated methods, or it's done via viewstate instance methods?
   
   ===== RemoteAction changes
   
  -RemoteAction changes are very simple - both VF and LC can use the *same* controller with the *same* methods! Example below will compile and work:
  +RemoteAction changes are very simple - both VF and LC can use the *same* controller with the *same* methods! An example below will compile and work:
   
   .TestController.apxc
   [source,Java]
  
positive.code: ** Solutions
  ** Ideas
  ** https://developer.salesforce.com/docs/atlas.en-us.noversion.service_sdk_android.meta/service_sdk_android/android_sos_overview.htm[SOS]
  ** Knowledge (can be used, bot lots of functionallity is unavaliable at this moment)
  
  If your business is OK to switch to Salesforce Classic to continue to use those features - then you'll be fine to proceed with customization changes
  
  
negative.code:         var caseObject = component.get("v.record");
  
          if (caseObject.Type != "Social") {
              component.set("v.recordError", "error message for non-social case");
          } else {
              caseObject.Type = "Social Plus"
              component.set("v.record", caseObject);
              component.find("recordLoader").saveRecord(
                  $A.getCallback(
                      function(saveResult) {
                          //You can add error handling here
                      }
                  )
              );
          }
      }
  })
  ----
  
  A Final step will be simple - create action with this component for Case sObject and add it to the layout! No Apex/3rd-party library required.
  
  === Visualforce Pages
  
  Every scenario here is pretty unique, however, few common page types can be separated: Reports pages, PDF-rendered pages, and new/edit/view papes. For the PDF we'll keep it as it is - as no changes and no ability to render lightning components as a pdf. But for the report-like and new/edit/view pages we have to change it to the lightning UI;
  
  ==== 1. Set the lightning styles
  
  