<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Antiphona changelog</title>
  <id>https://antiphona.app/changelog/</id>
  <link href="https://antiphona.app/changelog/"/>
  <link rel="self" href="https://antiphona.app/feed.xml"/>
  <updated>2026-10-20T00:00:00Z</updated>
  <author><name>The Doodle Project</name></author>
  <entry>
    <title>v1.0.1: Confirmation milestones</title>
    <id>https://antiphona.app/changelog/v1.0.1/</id>
    <link href="https://antiphona.app/changelog/v1.0.1/"/>
    <updated>2026-10-20T00:00:00Z</updated>
    <summary>Confirmation Milestone 3, &quot;The Call&quot;, moves into the app. Staff also get smaller fixes that make milestone work easier.</summary>
    <content type="html">&lt;h2 id=&quot;new&quot;&gt;New&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Confirmation Milestone 3, &amp;quot;The Call&amp;quot;.&lt;/strong&gt; Candidates fill in the form in English or Spanish. Staff review it in the app. Parents get a confirmation email.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The next milestone opens on its own.&lt;/strong&gt; When staff approve a milestone, the next one opens for the candidate if it has a form. When a child completes First Communion Milestone 1, Milestone 2 opens.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;improved&quot;&gt;Improved&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Staff open Milestone 2 from the review queue or from the milestone grid. Staff approve it in its review.&lt;/li&gt;
&lt;li&gt;A milestone that waits for review shows &amp;quot;Pending&amp;quot; in yellow. Staff mark a milestone as printed by hand, and it turns blue.&lt;/li&gt;
&lt;li&gt;Children in grades 2 to 5 who enroll in a sacrament program pay the kids&amp;#39; sacrament fee.&lt;/li&gt;
&lt;li&gt;An email about a care request now links straight to that request in Outreach and Care.&lt;/li&gt;
&lt;li&gt;A form link that a person cannot open now shows a clear &amp;quot;no access&amp;quot; notice.&lt;/li&gt;
&lt;li&gt;A very large email blast now works in small batches. If it fails, it says why in plain words.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <title>v1.0.0: The 1.0 release</title>
    <id>https://antiphona.app/changelog/v1.0.0/</id>
    <link href="https://antiphona.app/changelog/v1.0.0/"/>
    <updated>2026-10-20T00:00:00Z</updated>
    <summary>Antiphona can now be set up for more than one parish. The guides were refreshed, and the whole app was checked and corrected before release.</summary>
    <content type="html">&lt;h2 id=&quot;new&quot;&gt;New&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Made for more than one parish.&lt;/strong&gt; A parish&amp;#39;s name, colors, email addresses and modules now come from one configuration file. A new parish can be set up without changes to the code.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Refreshed guides.&lt;/strong&gt; The step-by-step guides were refreshed and are published on the docs site.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;improved&quot;&gt;Improved&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;A full check before release.&lt;/strong&gt; We walked through the whole app on a test system and corrected 19 problems before it went live.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Working data in one place.&lt;/strong&gt; Sign-in sessions and other working data moved into the main parish database.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Shared building blocks.&lt;/strong&gt; Code that several modules need now lives in shared packages, and the build tools were upgraded. Families see no new screens from this work. It makes later releases faster and safer.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;fixed&quot;&gt;Fixed&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;The human check on public forms could fail to finish for some visitors. It now completes.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <title>The road to 1.0</title>
    <id>https://antiphona.app/changelog/before-1-0/</id>
    <link href="https://antiphona.app/changelog/before-1-0/"/>
    <updated>2026-10-19T00:00:00Z</updated>
    <summary>From January to October 2026, Antiphona grew from a sign-in and a profile page into a full parish platform. Here are the main steps.</summary>
    <content type="html">&lt;p&gt;This page lists the main steps from the first release to version 1.0. The app had many more small releases than this. Each line says what became possible.&lt;/p&gt;
&lt;h2 id=&quot;january-and-february-2026&quot;&gt;January and February 2026&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;The first release.&lt;/strong&gt; Families could sign in, read their profile and see their household.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;English and Spanish.&lt;/strong&gt; A language switch arrived, and the app remembers the choice.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Vacation Bible School.&lt;/strong&gt; Camper registration, adult volunteers and teen volunteer applications.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Giving history.&lt;/strong&gt; A page for each family to read its own gifts.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;march-2026&quot;&gt;March 2026&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Guest registration.&lt;/strong&gt; Visitors could register for an event without becoming parishioners.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;One home for staff tools.&lt;/strong&gt; Admin tools for several modules moved to one admin page.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Payments with Stripe.&lt;/strong&gt; Families paid by card. Staff created payment links.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Email and text notifications,&lt;/strong&gt; payment plans in installments, a way to change your password, and a way to add a family member.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Clearance badges&lt;/strong&gt; on profiles for safe environment training and background checks.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;april-to-june-2026&quot;&gt;April to June 2026&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Security hardening.&lt;/strong&gt; More checks on who may see which record.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A rebuilt payments module,&lt;/strong&gt; and a second round of work on volunteer sign-up.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;OCIA and Faith Formation.&lt;/strong&gt; Baptism records were joined into one record, and the intake wizard was polished.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;july-and-august-2026&quot;&gt;July and August 2026&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;A quality pass on several modules,&lt;/strong&gt; including Ministries, Events and Conferences.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A rebuilt Faith Formation console,&lt;/strong&gt; designed around how the parish office works.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The fall program opens.&lt;/strong&gt; Class check-in, a welcome table for guests, a class board, name badges and meeting RSVPs. Card sales now match the bank deposit.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;september-2026&quot;&gt;September 2026&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;One set of consent rules for every message,&lt;/strong&gt; and one preference screen for families. The privacy policy went live in the app.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Help desk auto-close.&lt;/strong&gt; A request that waits on a reply closes by itself, unless staff keep it open.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A youth discernment application&lt;/strong&gt; (Acts 29) for teens, filled in with a parent.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Volunteers&lt;/strong&gt; could sign up as guests, and edit their sign-up notes.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;october-2026&quot;&gt;October 2026&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Faith Formation office tools.&lt;/strong&gt; A student drawer to edit student and parent details, a milestone tracker with printed labels, and a view of which families owe money.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Safer refunds.&lt;/strong&gt; A refund is recorded only after Stripe confirms it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Forms&lt;/strong&gt; can send answers to a SharePoint list. Payment links can ask for a deposit.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Easier to read.&lt;/strong&gt; Color contrast and screen reader labels improved across the app.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
</feed>
