Pulls .page files and shared template infrastructure (mainpagetemplate.temp, menu.bar, barant.tag, opensource.menu, cart.menu, login.menu) read-only from barant.com via SFTP into jetc/barant-site/src, then convert.py mechanically flattens them into self-contained .jet files: linkbutton becomes a plain anchor link (the old SESSIONCTL PAGE/PROCESS form-postback model has no equivalent here - each page is its own real #api route now, not a shared single-form state machine), sectionframe is expanded per its barant.tag definition, /images/* references are fetched and inlined as data URIs (APIServer has no static-file serving), and session-gated chrome (cart, account/admin, login.menu) is resolved to its anonymous-visitor default state, since no session/DB backend is wired into this conversion. 17 pages convert and serve cleanly end-to-end (verified via a local apiserver-barant-site.json instance on :8081, kept separate from the existing demo server on :8080 to avoid a /main route collision with the earlier hand-cloned barant.jet). Two pages deliberately out of scope for this pass: davidarant.page (whiledir filesystem iteration) and the per-topic sub-pages of jet.page (dispatches on an ARGS query param this conversion does not populate - only the default overview state converts). vst.page/modular1.page/modular1_patches.page also deferred - they pull live product rows via sql, a real backend dependency beyond "pages and their template" scope. Nothing was written back to barant.com - SFTP access was read-only throughout, per explicit instruction to convert locally without touching the original site.
69 lines
3.3 KiB
Plaintext
Executable File
69 lines
3.3 KiB
Plaintext
Executable File
<page template="mainpagetemplate">
|
|
<title>Wordpress Plugins</title>
|
|
<contents>
|
|
<setenv name="_menubar"></setenv>
|
|
|
|
<sectionframe title="BARANT Shopping Cart for WordPress">
|
|
<div style="display: table; width: 100%;">
|
|
<div style="display: table-cell; vertical-align: top; padding-right: 20px;">
|
|
<p>WordPress has become the standard for building a website - but its usual
|
|
answer for selling anything is WooCommerce, a heavyweight, plugin-hungry
|
|
platform built mainly for shipping boxes. If what you actually sell is
|
|
<b>streaming video, digital access, or a mix of physical and digital
|
|
products</b>, you're bending a shipping cart into shapes it was never
|
|
designed for.</p>
|
|
|
|
<p><b>BARANT Shopping Cart</b> is a self-contained WordPress plugin built
|
|
from the ground up for exactly that mix. It runs today in production on
|
|
<a href="https://westcoastwingchun.com" target="_blank">westcoastwingchun.com</a>,
|
|
handling pay-per-view and rental video streaming, physical merchandise
|
|
with shipping calculation, and rank-gated class content - all through
|
|
Square, with no WooCommerce required.</p>
|
|
</div>
|
|
<div style="display: table-cell; vertical-align: top; width: 90px; text-align: center;">
|
|
<img src="/images/shopping_cart.png" width="64">
|
|
</div>
|
|
</div>
|
|
</sectionframe>
|
|
|
|
<sectionframe title="Built For Video & Mixed-Product Selling">
|
|
<ul>
|
|
<li><b>Streaming video access</b> - sell unlimited access, a timed rental
|
|
window, or a one-time purchase for any video, with signed, time-limited
|
|
playback links so a purchased video can't be shared as a plain URL.</li>
|
|
<li><b>Physical goods too</b> - the same cart handles shippable merchandise
|
|
alongside digital items, with weight/dimension-based shipping-rate
|
|
lookups built in.</li>
|
|
<li><b>Rank-gated content</b> - restrict a catalog of videos to logged-in
|
|
users whose account has been assigned a specific access tier, useful
|
|
for membership or class-based content of any kind, not just video.</li>
|
|
<li><b>Square payments</b> - card payments through Square's Web Payments
|
|
SDK, with a sandbox/production toggle and a built-in connection test
|
|
so you can verify credentials before ever taking a live payment.</li>
|
|
<li><b>A real admin section</b> - Dashboard, Inventory, Orders, Settings
|
|
and Payment Gateway screens, all inside WordPress's own admin UI. No
|
|
database edits required to configure or run the store.</li>
|
|
<li><b>Its own data model</b> - cart, inventory, and order data live in
|
|
the plugin's own tables, independent of WooCommerce or any other
|
|
e-commerce plugin you may already have installed.</li>
|
|
</ul>
|
|
</sectionframe>
|
|
|
|
<sectionframe title="See It Running Live">
|
|
<p>The best proof of a shopping cart plugin is a real store using it. Visit
|
|
<a href="https://westcoastwingchun.com" target="_blank">westcoastwingchun.com</a>
|
|
to see BARANT Shopping Cart handling real video-streaming sales, rentals, and
|
|
physical merchandise checkout end to end.</p>
|
|
</sectionframe>
|
|
|
|
<sectionframe title="Get It">
|
|
<p>BARANT Shopping Cart is headed for the official WordPress Plugin
|
|
Directory. In the meantime, if you'd like early access, help installing it
|
|
on your own site, or custom feature work, <a href="/contact">get in
|
|
touch</a> - BARANT Technology Group can also handle hosting and setup for
|
|
you directly.</p>
|
|
</sectionframe>
|
|
|
|
</contents>
|
|
</page>
|