feat: VivesPOS landing on Winter CMS 1.2 — theme + plugin + Dockerfile

- Base: wintercms/winter branch 1.2 (full framework)
- Theme vivespos: Canvas 7 + Bootstrap 5 CDN, custom CSS
- Layout: deferred GTM/GA4 tracking, JSON-LD SoftwareApplication
- Partials: hero (offline-first), features, modes (offline/nube toggle),
  screenshots, pricing (3 planes), comparison, FAQ, CTA
- Plugin VivesPOS.Site with ContactForm
- Dockerfile: PHP 8.2 Apache, port 80, healthcheck
- Added winter/wn-pages, blog, sitemap, seo plugins
- Active theme set to vivespos

themes/demo/pages/home.htm

@@ -0,0 +1,120 @@
+title = "Demonstration"
+url = "/"
+layout = "default"
+==
+<div class="jumbotron">
+    <div class="container">
+        {% content "welcome.htm" %}
+    </div>
+</div>
+
+<div class="container">
+
+    <div class="page-header">
+        <h2>Overview <small>Basic concepts</small></h2>
+    </div>
+    <p>
+        This page demonstrates the basic CMS features.
+        Usually each page built with Winter is a combination of a layout, page, partials and content blocks,
+        although in simple cases you can just use a page without anything else.
+    </p>
+
+    <!-- Layouts -->
+    <h3>Layouts</h3>
+    <p class="lead">
+        <i class="icon-th-large"></i> &nbsp; Layouts define the page scaffold.
+    </p>
+    <p>
+        The layout file <code>layouts/default.htm</code> defines the page scaffold &mdash;
+        everything that repeats on each page, such as the HTML, HEAD and BODY tags, StyleSheet and JavaScript references.
+    </p>
+    <p>The page menu and footer in the Demo theme are defined in the layout as well.</p>
+
+    <hr />
+
+    <!-- Pages -->
+    <h3>Pages</h3>
+    <p class="lead">
+        <i class="icon-copy"></i> &nbsp; Pages hold the content for each URL.
+    </p>
+    <p>
+        The page file <code>pages/home.htm</code> defines the page URL (<code>/</code> for this page) and the page content.
+        Pages are rendered inside layouts with this function that should be called in the layout code:
+    </p>
+    <pre>{{ "{% page %}" }}</pre>
+    <p>Using a layout for pages is optional &mdash; you can define everything right in the page file.</p>
+
+    <hr />
+
+    <!-- Partials -->
+    <h3>Partials</h3>
+    <p class="lead">
+        <i class="icon-tags"></i> &nbsp; Partials contain reusable chunks of HTML markup.
+    </p>
+    <p>
+        Partials are chunks of HTML defined in separate files that can be included anywhere.
+        Partials are rendered with:
+    </p>
+    <pre>{{ "{% partial \"partial-name\" %}" }}</pre>
+    <p>You may place partials inside folders too. In this example we placed the footer content to the <code>partials/site/footer.htm</code> partial.</p>
+    <pre>{{ "{% partial \"site/footer\" %}" }}</pre>
+    <p>Partials can be used inside pages, layouts or other partials.</p>
+
+    <hr />
+
+    <!-- Content blocks -->
+    <h3>Content blocks</h3>
+    <p class="lead">
+        <i class="icon-font"></i> &nbsp; Content blocks are text or HTML blocks that can be edited separately from the page or layout.
+    </p>
+    <p>
+        The introductory text used on this page is defined in the <code>content/welcome.htm</code> file.
+        Content blocks are defined and rendered with:
+        <pre>{{ "{% content \"content-name.htm\" %}" }}</pre>
+    </p>
+
+    <hr />
+
+    <!-- Placeholders -->
+    <h3>Placeholders</h3>
+    <p class="lead">
+        <i class="icon-bookmark"></i> &nbsp; Placeholders allow pages to inject content to a layout.
+    </p>
+    <p>
+        The common use is injecting page-specific links to StyleSheet or JavaScript files to the HEAD tag defined in the layout.
+        Placeholders are defined in the layout file and they have names so that they can be referred in the page.
+        Example:
+    </p>
+    <div class="row">
+        <div class="col-md-6">
+            <p>Layout file:</p>
+            <pre>{% content "placeholder/layout.txt" %}</pre>
+        </div>
+        <div class="col-md-6">
+            <p>Page file:</p>
+            <pre>{% content "placeholder/page.txt" %}</pre>
+        </div>
+    </div>
+
+    <hr />
+
+    <!-- Assets -->
+    <h3>Assets</h3>
+    <p class="lead">
+        <i class="icon-picture"></i> &nbsp; Assets are resource files like images and stylesheets.
+    </p>
+    <p>This theme stores its asset files (JavaScript, StyleSheet, images, fonts, etc) in the <code>themes/demo/assets</code> directory. This theme is also packaged with these useful 3rd party tools:</p>
+    <ul class="list-inline">
+        <li><a target="_blank" href="http://getbootstrap.com/">Twitter Bootstrap</a></li>
+        <li><a target="_blank" href="http://fontawesome.io/3.2.1/">Font Awesome</a></li>
+        <li><a target="_blank" href="http://www.google.com/fonts/specimen/Lato">Lato webfont</a></li>
+    </ul>
+    <p>You might prefer to remove them for your website implementation.</p>
+
+    <br />
+
+    <div class="text-center">
+        <p><a href="{{ 'ajax'|page }}" class="btn btn-lg btn-default">Continue to AJAX framework</a></p>
+    </div>
+
+</div>