I've created a component group with some components and created one page template with a parsys which should display all components in side line.
For this I created a basePage template and created /etc/designs/myproject/jcr:content/basePage with a parsys inside it as shown in diagram,I added all required component groups in that parsys node as property "components". This way I was able to see all my component groups in sidekick of classic UI but in case of touch UI I was unable to see anything in pop up window after clickin on parsys. While my component groups & components were listed under sideline of touch UI but not on the pop up window after clicking on parsys.
I believe there is a caching issue in the Touch UI that prevents new components from showing up. I see this issue very frequently, and it's rather annoying. Easiest way to solve is to shut down your instance and restart it - at least until Adobe releases a fix.
Each CQ5 template has a different set of components that can be defined to be available for use. This allows you to control what the authors will be allowed to use, and it makes it easier for them, because they will only see the relevant components, instead of the tons of components CQ5 offers.
When looking at a page, you can switch to something called the "design" mode (as opposed to the "edit" or "preview" modes where you spend most of your time authoring the page). This design mode allows to define the per-template specific settings. It is accessed through the yellow ruler icon on the very bottom of the sidekick.
When in design mode, click on the "Edit" button that is on the blue toolbar called "Design of par", there you'll be able to enable the components you want to be able to use.
When you'll be building components, keep in mind that the design mode and the corresponding design dialogs of the components is a convenient way to define global per-template settings that you don't want to be required to be set specifically on each component instance.
As mentioned by Lee that there seems to be caching issue with Touch UI, try to restart the instance else adding component in classic UI could be use as workaround.