Back to projects
Enoria showcase

Enoria

Collaborative church management application. I conducted the rework of the UI during my internship, now I work there as a freelance to implement new features and resolve bugs

|
  • PHP
  • Symfony
  • Bootstrap
  • twig
  • git

Overview

Enoria is a comprehensive church management platform designed to help parishes and dioceses manage their administrative tasks efficiently. The application handles member management, event scheduling, communication, and various parish-related activities.

My Role

I joined Enoria during my internship where I was tasked with conducting a complete UI/UX overhaul of the existing application. The goal was to modernize the interface and improve the overall user experience for parish administrators.

After my internship, I continued working with Enoria as a freelance developer, where I:

  • Implement new features based on client feedback
  • Fix bugs and resolve technical issues
  • Maintain and improve existing functionality
  • Collaborate with the team on architectural decisions

Technical Challenges

Legacy Code Migration

One of the main challenges was working with a legacy codebase while gradually introducing modern practices. This required careful planning to ensure backward compatibility while improving code quality.

User Experience

Designing an intuitive interface for users who may not be tech-savvy was crucial. The application needed to be accessible and easy to use for parish volunteers and administrators of all ages.

Key Features

  • Member Management: Track parishioners, families, and their participation
  • Event Scheduling: Organize masses, ceremonies, and parish events
  • Communication Tools: Send newsletters and announcements
  • Financial Tracking: Manage donations and parish finances
  • Document Generation: Create certificates and official documents

What I Learned

Working on Enoria taught me the importance of:

  • Working with legacy systems and migrating them gradually
  • Understanding user needs in specialized domains
  • Balancing technical debt with feature development
  • Communicating with non-technical stakeholders