<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Project on Josh Wise</title>
    <link>https://jwise.dev/tags/project/</link>
    <description>Recent content in Project on Josh Wise</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 17 Nov 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://jwise.dev/tags/project/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Unboxed: Postmortem&#43;</title>
      <link>https://jwise.dev/posts/unboxed-a-postmortem-2/</link>
      <pubDate>Mon, 17 Nov 2025 00:00:00 +0000</pubDate>
      <guid>https://jwise.dev/posts/unboxed-a-postmortem-2/</guid>
      <description>&lt;h1&gt;&lt;/h1&gt;
&lt;p&gt;Earlier this month, I wrote about building &lt;a href=&#34;__GHOST_URL__/unboxing-vaults-mail/&#34;&gt;Unboxed&lt;/a&gt;, a native macOS app to convert Google Vault MBOX exports into PDFs. The goal was simple: make email archives accessible to non-technical staff handling open records requests. The app worked, but it had a problem—it was slow. Really slow. Large MBOX files would chug along, eating up memory and often crashing the app entirely. I suspect the culprit was PDFKit, Apple&amp;rsquo;s framework for generating PDFs, struggling to keep up with the workload.&lt;/p&gt;</description>
    </item>
    <item>
      <title>viewFMX</title>
      <link>https://jwise.dev/posts/viewfmx/</link>
      <pubDate>Thu, 30 Jan 2025 00:00:00 +0000</pubDate>
      <guid>https://jwise.dev/posts/viewfmx/</guid>
      <description>&lt;p&gt;My workplace recently adopted FMX as a platform for managing facility resources and availability. The platform provides robust scheduling capabilities and has proven invaluable for managing room bookings and resource allocation across our district.&lt;/p&gt;
&lt;p&gt;However, we quickly identified a gap in our implementation: the need for clear, real-time displays outside each conference room showing current and upcoming bookings. While there are commercial products available that offer this functionality, FMX doesn&amp;rsquo;t provide dedicated display hardware or a standalone display solution. What they do offer, though, is a comprehensive API - and that&amp;rsquo;s where my journey began.&lt;/p&gt;</description>
    </item>
    <item>
      <title>orgLink</title>
      <link>https://jwise.dev/posts/orglink/</link>
      <pubDate>Wed, 09 Oct 2024 00:00:00 +0000</pubDate>
      <guid>https://jwise.dev/posts/orglink/</guid>
      <description>&lt;p&gt;In today&amp;rsquo;s digital-first educational landscape, teachers are expected to navigate a complex web of online resources. From learning management systems and grading portals, to curriculum repositories and communication platforms, the number of essential links can be overwhelming.&lt;/p&gt;
&lt;p&gt;To address these issues, I developed an internal extension deployed via our Google Workspace account. This tool provides a centralized, easily accessible hub for all essential web resources used by teachers in our district. I decided recently that this extension could be improved upon, and made available for others to solve similar problems.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
