Demo Data
Documentation
You can find the documentation under this link: QUIQQER Demodata
How to provide demo data
Composer
Your package can tell the QUIQQER ecosystem it provides demodata by adding the following snippet in your composer.json
"extra": {
"quiqqer": {
"demodata": true
}
}XML
After this you need to create a demodata.xml file within your packages root.
CMS_DIR/packages/<vendor>/<package>/demodata.xmlThis file defines the demodata that QUIQQER can use during project creation.
Example: demodata.xml
<data>
<events>
<event on="onFinish" fire="\class\callback" />
</events>
<project>
<!-- Imports the data from the demoedata.sql file, this is optional -->
<sql file="demodata.sql"/>
<!-- You can tell QUIQQER set the following settings for the project -->
<settings>
<setting name="layout" value="layout/noSidebar"/>
<setting name="templatePresentation.settings.social.gitlab" value="https://dev.quiqqer.com/quiqqer/quiqqer"/>
</settings>
<!-- QUIQQER will create the given page structure-->
<sites>
<!-- This is the start page in QUIQQER-->
<site>
<!-- You can define the sites attributes here.-->
<attributes>
<attribute name="name">Demo Name</attribute>
<attribute name="title">Demo Titel</attribute>
<attribute name="short">Lorem ipsum</attribute>
<attribute name="type">standard</attribute>
<attribute name="bricks">Lorem ipsum</attribute>
<attribute name="content"><![CDATA[
<h1>HTML Ipsum Presents</h1>
<p><strong>Pellentesque habitant morbi tristique</strong> senectus et netus et malesuada fames ac turpis egestas. Vestibulum tortor quam, feugiat vitae, ultricies eget, tempor sit amet, ante. Donec eu libero sit amet quam egestas semper. <em>Aenean ultricies mi vitae est.</em> Mauris placerat eleifend leo. Quisque sit amet est et sapien ullamcorper pharetra. Vestibulum erat wisi, condimentum sed, <code>commodo vitae</code>, ornare sit amet, wisi. Aenean fermentum, elit eget tincidunt condimentum, eros ipsum rutrum orci, sagittis tempus lacus enim ac dui. <a href="#">Donec non enim</a> in turpis pulvinar facilisis. Ut felis.</p>
<h2>Header Level 2</h2>
<ol>
<li>Lorem ipsum dolor sit amet, consectetuer adipiscing elit.</li>
<li>Aliquam tincidunt mauris eu risus.</li>
</ol>
<blockquote><p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vivamus magna. Cras in mi at felis aliquet congue. Ut a est eget ligula molestie gravida. Curabitur massa. Donec eleifend, libero at sagittis mollis, tellus est malesuada tellus, at luctus turpis elit sit amet quam. Vivamus pretium ornare est.</p></blockquote>
<h3>Header Level 3</h3>
<ul>
<li>Lorem ipsum dolor sit amet, consectetuer adipiscing elit.</li>
<li>Aliquam tincidunt mauris eu risus.</li>
</ul>
]]></attribute>
</attributes>
<!-- Define the sites child pages in the same format-->
<children>
<site>
<attributes>
<attribute name="name">Subpage1</attribute>
<attribute name="title">Subpage1</attribute>
<attribute name="short">Lorem ipsum</attribute>
<attribute name="type">standard</attribute>
<attribute name="bricks">Lorem ipsum</attribute>
<attribute name="content"><![CDATA[
<h1>HTML Ipsum Presents</h1>
<p><strong>Pellentesque habitant morbi tristique</strong> senectus et netus et malesuada fames ac turpis egestas. Vestibulum tortor quam, feugiat vitae, ultricies eget, tempor sit amet, ante. Donec eu libero sit amet quam egestas semper. <em>Aenean ultricies mi vitae est.</em> Mauris placerat eleifend leo. Quisque sit amet est et sapien ullamcorper pharetra. Vestibulum erat wisi, condimentum sed, <code>commodo vitae</code>, ornare sit amet, wisi. Aenean fermentum, elit eget tincidunt condimentum, eros ipsum rutrum orci, sagittis tempus lacus enim ac dui. <a href="#">Donec non enim</a> in turpis pulvinar facilisis. Ut felis.</p>
<h2>Header Level 2</h2>
<ol>
<li>Lorem ipsum dolor sit amet, consectetuer adipiscing elit.</li>
<li>Aliquam tincidunt mauris eu risus.</li>
</ol>
<blockquote><p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vivamus magna. Cras in mi at felis aliquet congue. Ut a est eget ligula molestie gravida. Curabitur massa. Donec eleifend, libero at sagittis mollis, tellus est malesuada tellus, at luctus turpis elit sit amet quam. Vivamus pretium ornare est.</p></blockquote>
<h3>Header Level 3</h3>
<ul>
<li>Lorem ipsum dolor sit amet, consectetuer adipiscing elit.</li>
<li>Aliquam tincidunt mauris eu risus.</li>
</ul>
]]></attribute>
</attributes>
<children></children>
</site>
<site>
<attributes>
<attribute name="name">Subpage2</attribute>
<attribute name="title">Subpage2</attribute>
<attribute name="short">Lorem ipsum</attribute>
<attribute name="type">standard</attribute>
<attribute name="bricks">Lorem ipsum</attribute>
<attribute name="content"><![CDATA[
<h1>HTML Ipsum Presents</h1>
<p><strong>Pellentesque habitant morbi tristique</strong> senectus et netus et malesuada fames ac turpis egestas. Vestibulum tortor quam, feugiat vitae, ultricies eget, tempor sit amet, ante. Donec eu libero sit amet quam egestas semper. <em>Aenean ultricies mi vitae est.</em> Mauris placerat eleifend leo. Quisque sit amet est et sapien ullamcorper pharetra. Vestibulum erat wisi, condimentum sed, <code>commodo vitae</code>, ornare sit amet, wisi. Aenean fermentum, elit eget tincidunt condimentum, eros ipsum rutrum orci, sagittis tempus lacus enim ac dui. <a href="#">Donec non enim</a> in turpis pulvinar facilisis. Ut felis.</p>
<h2>Header Level 2</h2>
<ol>
<li>Lorem ipsum dolor sit amet, consectetuer adipiscing elit.</li>
<li>Aliquam tincidunt mauris eu risus.</li>
</ol>
<blockquote><p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vivamus magna. Cras in mi at felis aliquet congue. Ut a est eget ligula molestie gravida. Curabitur massa. Donec eleifend, libero at sagittis mollis, tellus est malesuada tellus, at luctus turpis elit sit amet quam. Vivamus pretium ornare est.</p></blockquote>
<h3>Header Level 3</h3>
<ul>
<li>Lorem ipsum dolor sit amet, consectetuer adipiscing elit.</li>
<li>Aliquam tincidunt mauris eu risus.</li>
</ul>
]]></attribute>
</attributes>
<children>
</children>
</site>
</children>
<!-- You can assign created bricks to the sites areas here-->
<bricks>
<!-- Use an area tag for each area.-->
<!-- The type attribute contains the areas name as defined by the template-->
<area type="headerSuffix">
<!-- Within the area tag you can put brick tags-->
<!-- They use an identifier, which can be found below in the bricks section -->
<!-- This will get replaces by the actual bricks ID after it was created-->
<brick identifier="brick.demo">
<!-- Within here you can assign the bricks attributes-->
<attributes>
<!-- This overwrites the bricks settings. Use a json string just like in the database-->
<attribute name="settings">
<![CDATA[{"classes":[],"width":"100","height":"100","title":"Boomerang","socialList":"[{\"url\":\"Test\",\"icon\":\"gitlab\",\"background\":\"#222222\"}]","brickFullWidth":[],"noPadding":false}]]>
</attribute>
</attributes>
</brick>
</area>
</bricks>
</site>
</sites>
</project>
<!-- This creates bricks for the given project-->
<bricks>
<!-- Each brick has an identifier which gets sued as reference in the brick-to-site association in the sites xml section-->
<!-- The identifier will get replaces by the bricks actual ID after it ws created-->
<brick identifier="brick.demo">
<!-- You can define the bricks attributes here -->
<!-- The possible attributes are defined by QUQIQER itself -->
<attributes>
<attribute name="title">Demo Brick</attribute>
<attribute name="type">\QUI\Bricks\Controls\SocialBox</attribute>
<attribute name="settings">
<![CDATA[{"classes":[],"width":"","height":"","title":"Testbaustein","socialList":"[{\"url\":\"Test\",\"icon\":\"gitlab\",\"background\":\"#333333\"}]","brickFullWidth":[],"noPadding":false}]]>
</attribute>
<attribute name="customfields">
<![CDATA[["width","height","classes","title","socialList","brickFullWidth","noPadding"]]]>
</attribute>
<attribute name="areas">
,noSidebar,header,headerSuffix,prefixContentBricks,leftSidebar,rightSidebar,suffixContentBricks,footerPrefix,footer,
</attribute>
</attributes>
</brick>
</bricks>
</data>