Reformed Heritage Study Center

The Reformed Heritage Study Center is an independent Christian educational organization, set up to teach the Reformed tradition rigorously outside a conventional college.

They needed an identity, a public presence, and software the institution could operate: a course catalog, student accounts, enrollment, payments, and access to the educational material. I was the only designer and the only developer. The timeline was short, and there would be no full-time engineer afterward, so the platform had to be something the people running the place could live with. I owned the visual identity and the brand, the user experience, the application architecture, the frontend and the backend, payment processing, the enrollment workflows, deployment, and production support.

The identity

It had to communicate intellectual seriousness, continuity with a centuries-old tradition, theological conviction, and academic credibility to a contemporary audience. The commitments are old. Instruction, enrollment, and the course itself are on the web.

The easy references were a university clone or a parchment-and-gilt costume. I took the direction from the institution’s character and its educational mission: type, color, imagery, composition, and the language on the page. It had to be recognizable as this Study Center, and it had to work as software. That system runs through the public site, the way courses are presented, the navigation, the hierarchy, and the communications around them.

The imagery

I researched and chose historical artwork for the courses and the subjects: illustrations, manuscripts, paintings, engravings, and other sources. A piece had to support the subject, fit the theological commitments, and hold up on a screen. I checked provenance and usage rights, then crop, legibility, and how the image sat in the interface. Courses can look distinct, and the institution still reads as one place.

Where students actually see it

Students meet the Study Center in the catalog, on the registration form, in the account, during enrollment, on the payment screen, and in the resources. I carried the same type, layout, components, and hierarchy through those screens. The catalog can be distinctive and still scannable. The enrollment form matches the site without decoration it does not need. Admin and student screens stay plain where the public pages are more expressive. I was writing the software at the same time, so the visual calls were made against how the interface behaves.

One person on both sides

There was nobody to hand a mockup to. I checked a visual idea against the technical constraint, changed an interaction once the application’s behavior was clear, and kept the public site and the platform consistent. If an element is hard to maintain, or a custom interaction is more machinery than the task needs, it goes. A simpler component was often the better experience and the shorter build. The brand, the interface, and the software are one product, shaped around the institution’s identity and what it takes to run it.