<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hypermedia on psLens</title><link>https://pslens.com/tags/hypermedia/</link><description>Recent content in Hypermedia on psLens</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 13 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://pslens.com/tags/hypermedia/index.xml" rel="self" type="application/rss+xml"/><item><title>Why psLens Runs on Go, a Hypermedia UI Stack, and SWS Instead of Living Inside PeopleSoft</title><link>https://pslens.com/blog/why-pslens-runs-on-go-hypermedia-and-sws/</link><pubDate>Mon, 13 Jul 2026 00:00:00 +0000</pubDate><guid>https://pslens.com/blog/why-pslens-runs-on-go-hypermedia-and-sws/</guid><description>&lt;p&gt;When I started building psLens, I was not trying to create another PeopleSoft bolt-on. I wanted a tool that could sit beside PeopleSoft, search metadata fast, run audits, monitor Process Scheduler and Integration Broker, and stay easy to deploy and maintain.&lt;/p&gt;
&lt;p&gt;That requirement set ruled out a lot of obvious choices.&lt;/p&gt;
&lt;p&gt;psLens now runs as a standalone &lt;a href="https://github.com/golang/go"&gt;Go&lt;/a&gt; application with server-rendered UI components built in &lt;a href="https://github.com/a-h/templ"&gt;templ&lt;/a&gt;, live updates handled by &lt;a href="https://data-star.dev"&gt;Datastar&lt;/a&gt; (&lt;a href="https://github.com/starfederation/datastar"&gt;GitHub&lt;/a&gt;), and a PeopleSoft-side access layer provided by &lt;a href="https://sws.books.cedarhillsgroup.com/docs/"&gt;SWS&lt;/a&gt;. That combination is not accidental. Each part solves a specific problem that PeopleSoft teams run into when they try to build admin and security tooling the old way.&lt;/p&gt;</description></item></channel></rss>