Convert barant.com JET 1.4 marketing pages to jetc/.jtc (local, non-production)

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.

jetc/barant-site/src/serverframework.page

@@ -0,0 +1,44 @@
+<page template="mainpagetemplate">
+<title>Server Core Framework</title>
+<contents>
+<sectionframe title="Server Core Framework">
+<p>It is finally here! The Server Core Framework is now available. The
+framework offers support for just about any server you can devise.</p>
+
+<p>Now why would I want to go and build a server when there are all
+sorts of frameworks out there for supporting server activity? All I
+can say is top notch performance. The Server Core is all C++ and is
+built on the epoll structure of the Linux operating system.</p>  
+
+<ul>
+<li>TCP and/or UDP server capabilities.</li>
+<li>Straight socket or TLS connections.</li>
+</ul>
+
+<p>Using the Server Core you can build out server elements for
+embedded systems or massively publicly accessible servers with simple
+code. Use the Server Core for:</p>
+<ul>
+<li>Micro-services engine for code generators.</li>
+<li>Game servers of all types.</li>
+<li>E-Mail services (checkout barantmail project).</li>
+<li>SIP telephony server.</li>
+<li>HTTP/HTTPS for embedded web sites.</li>
+<li>Streaming server for online radio stations.</li>
+<li>Any other TCP or UDP based server.</li>
+</ul>
+
+<p>For the game server we will be offering client modules for both
+Unty 3D and for the Unreal Engine 4 with drop in and play options that
+can be heavily modified to support unique game features. Offers
+support for mySQL backends.</p>
+
+<img src="images/ServerCoreMap.png" width="80%">
+<br>
+<code>
+git clone https://barant.com/git@ServerCore.git
+</code>
+
+</sectionframe>
+</contents>
+</page>