WordPress Developer for Teacher Directory, Workshop System & Practitioner Records

WordPress Developer — Teacher, Workshop & Practitioner System We are developing the next stage of an existing educational WordPress website, Academy of Alchemists. We’re wanting this project to be finished by 15th of September and no longer than 35hours The website already uses: * WordPress * Tutor LMS * WooCommerce * FV Player We are looking for an experienced WordPress developer to build a connected system for: Teachers → Courses → Workshops → Attendance → Practitioners The goal is to enter information once and reuse it throughout the website, rather than maintaining separate duplicate records. You will be working alongside our existing website designer, so this is mainly a WordPress systems/development role, not a general redesign. ⸻ 
 1. Teacher & Course System Each teacher should have a reusable public profile containing information such as: * Name * Photo * Biography * City/town * Country * Languages * Website/contact * Courses they are authorised to teach * Upcoming workshops * Previous workshops Teachers should have a simple front-end account rather than normal WordPress admin access. Initially they need to be able to: * submit their own workshops; * edit their own workshops where allowed; * view submission status. Teachers should only manage their own authorised information. Course codes / abbreviations Each recognised course should have a central course record containing its full name and short code. For example: MR-EFCK = Mark Rasmus: Elastic Force Chi Kung A teacher submitting a workshop should be able to choose only courses they are authorised to teach. They may also request a new course/code, but Academy should be able to approve it and prevent duplicate/conflicting abbreviations. The course code and full course name should remain connected throughout the system. 
 ⸻ 
 2. Workshops & Events Teachers should submit workshops from a front-end form. Information may include: * Workshop title * Course / course code * Teacher * Description * Date/time/time zone * Online / in-person / hybrid * Venue, city and country * Price * Booking link * Featured image * Optional promotional video Teachers have to be approved by admins Once approved, the same workshop record should be reusable on: * Workshops/Events page * Calendar * Teacher profile * Related course * Homepage where appropriate Historical records Past or cancelled workshops should not simply be deleted. For example, if someone attended a workshop in 2025, their record should still be able to show: Practitioner → Course → Workshop → Teacher → Date even if that teacher is no longer active on the website. 
 ⸻ 
 3. Attendance & Practitioner Records We want attendance connected directly to the workshop system. The central attendance record should connect: Person → Course → Workshop → Teacher → Date → Verified Attendance Attendance may initially be entered through: * a simple teacher/admin front-end form; * Academy administration; * CSV/spreadsheet import where useful. We are happy to keep the first version simple. A teacher should only be able to enter attendance for workshops/courses they are authorised to teach. Academy should be able to verify attendance. A practitioner should not be able to edit their own verified training history. Workshop attendees become student/practitioner records — not teacher accounts. 
 ⸻ 
4. Public Practitioner Directory Once a person has verified attendance for an approved course/workshop, they should automatically have a basic practitioner record and appear in the public practitioner directory. This helps keep the public directory tied to verified Academy training records, rather than allowing people to simply claim that they completed a course themselves. Basic public information may include: * Name * City/town * Country * Languages * Verified courses completed * Optional website/contact information The verified course history should come from the Academy attendance system and must not be self-editable by the practitioner. Practitioners may later be able to add optional profile information such as: * Photo * Biography * Website * Contact details * Practice information A teacher or Academy admin should be able to hide/opt a practitioner out of the public directory if required. Search We want a simple practitioner search similar in concept to professional practitioner directories. Possible filters: Name | Course | Country | City | Language Example result: Jane Smith
Sacramento, USA
English, Spanish
MR-EFCK
View Profile We do not expect a custom search engine to be built from scratch. We are currently considering FacetWP for this. A useful reference for the general type of practitioner search we want is IAHP/Upledger: https://www.iahp.com/pages/search/index.php This is a UX/reference example only. We do not need their exact design or technical implementation copied 
 ⸻ 
 5. Simple Social-Media Workshop Queue We want a very simple private promotion workflow connected to workshops. If a teacher submits a promotional video, Academy should be able to see something like: * Teacher * Workshop * Course * Promotional video * Featured image * Event date * Workshop URL * Related course URL * Promotion status The status can simply be: Needs Editing → Ready → Posted Once posted, we can optionally save the final social-media URL. This does not need to be an advanced automation system. It is simply a small internal queue so our video editor can easily find upcoming workshop material. 
 ⸻ 
 6. Preferred WordPress Foundation We prefer to use reliable existing plugins where they reduce development cost and future maintenance rather than custom-coding standard WordPress functionality unnecessarily. Our current preferred foundation is: ACF Pro $49/year For: * teacher/course/practitioner fields; * relationships; * course codes; * attendance structure; * custom data. FacetWP Basic $99/year For: * practitioner search; * teacher/workshop filtering where useful; * course/location/language filters. The Events Calendar + Community Community: $129/year For: * workshop/event records; * calendar; * front-end teacher event submission; * event moderation/approval; * past events. We are open to your recommendations during the planning stage. We do not want to add additional paid plugins unless they genuinely reduce significant development or maintenance. For example, we currently believe attendance forms can be handled with ACF/front-end development rather than automatically purchasing a large form plugin. 
 ⸻ 
 7. Permissions & Data Rules The system should follow some basic rules: * Teachers cannot access WordPress administration unnecessarily. * Teachers only manage their own authorised workshops/courses and future learning centre posts. * Teachers cannot edit another teacher’s information. * Practitioners cannot edit verified attendance. * Deactivating a teacher must not delete their historical workshops. * Past/cancelled workshops retain useful historical records. * Avoid duplicate practitioner/student records. * Course codes are controlled centrally by Academy. * Important structural work should be tested on staging. * Backups should be taken before significant changes/imports. 
 ⸻ 
 8. Existing Systems The website already uses: * WordPress * Tutor LMS * WooCommerce * FV Player These should not be substantially replaced without discussion. The new system should work alongside them. We also intend to add CRM, multilingual and more advanced SEO systems separately later, so the structure should remain compatible with future integrations. 
 ⸻ Useful Experience Experience with the following would be particularly helpful: * WordPress custom development * ACF / custom post types * WordPress roles and permissions * FacetWP * Events Calendar / Community Events * front-end submissions * directories/member portals * attendance or record systems * WooCommerce/Tutor LMS compatibility * PHP/MySQL where custom work is required Please also show any similar systems or directories you have built. 
 ⸻ 
 Attached Examples We will attach images showing: * the type of course abbreviation/code system we have in mind, such as MR-EFCK; * examples of the practitioner search and search-result layout we would like. The IAHP/Upledger practitioner directory above is also included as a reference for the overall search concept. Thank you ————— Future Learning Centre — Not Required for Launch The Learning Centre does not need to be built as part of this project, but we would like the Teacher/Course/Workshop structure to be easy to connect to it later. The basic idea is: YouTube video → AOA website blog/Learning Centre post For example, when Academy publishes an educational YouTube video, we may create a related website post containing: * Embedded YouTube video * Written summary or transcript * Key points * Author/teacher * Related course * Related workshop where relevant In the future, approved teachers may also be able to submit videos/content through their account. For example: Teacher submits educational video → approved blog/Learning Centre post or: Teacher submits workshop/event with a useful video → that video may also be turned into a related website post We do not need this built now. We simply want the current Teacher, Course and Workshop structure designed so it can connect to this later without needing to rebuild everything. Thank you