AEM sidekick not visible

How to display sidekick in AEM page template.
In AEM the sidekick is an important UI to get access to various components in our application.
It's very important to get access to it while authoring our pages.

Here are some causes which answers the question

Why the AEM sidekick is not visible?
1. Viewing in Touch UI editor.
The latest versions of AEM opens a page to be authored in Touch UI. The sidekick is accessible in the Classic UI. To go to the classic UI you can do the following.

i. Replace the editor.html from the URL with cf#. So this means

Editor Mode (Sidekick Hidden): http://localhost:4502/editor.html/content/myProject/abc.html
Classic UI Mode (Sidekick Visible): http://localhost:4502/cf#/content/myProject/abc.html
ii. From the menu open Classic UI.

For doing this click on this button on the left top corner of the editor.

Select "Open in Classic UI" from the drop down menu.


2. Including the init.jsp file.
As the name suggests the init.jsp file helps to initialize vital components to load the sidekick. If you don't include this file then the AEM sidekick will not be visible.

To include the file copy and paste the line below to your Page Component. (Page component is the component which you use to create the page template.)
<cq:include script="/libs/wcm/core/components/init/init.jsp"/>

3. A component causing error which prevents sidekick to load.
In some cases the sidekick is not able to load one of the components added to the paragraph system in design mode. This could be due to a problem with the component.

To fix this we need to delete our ewly added components one by one until the problem component is found.

To do this:
Log in to CRXDE.
Navigate to /etc/designs/[your application name].
The structure in /etc/designs is parallel to your templates' content structure.
For example, /etc/designs/geometrixx/jcr:content/homepage/par is a paragraph system in Geometrixx's homepage template.


On expanding the homepage node.


So we can one by one delete the components like section/colctrl/section/..... until the problem component is found.