Choosing Photographer vs Developer Mode

Pick the mode that matches your business model so the admin UI, portal emphasis, and documentation all line up.

Mankai loads the same core systems in both modes, but it changes the language, emphasis, and some route handling depending on whether you are a photographer or a developer.

Choose Photographer Mode If You Need

Session-based work instead of long-form projects
Session types with pricing, retainer, turnaround, and booking rules
Proofing galleries
Delivered photo downloads
Print ordering
Client questionnaires tied to session types

Choose Developer Mode If You Need

Traditional project records
Project summaries and scope notes
Billing plans, deposits, and project URLs
Files and asset submissions
Developer-style intake forms
Project updates and project-specific action items

What Changes in Photographer Mode

The client-facing and admin language shifts toward sessions and galleries. Additional routes for galleries, deliverables, and print orders are added to the portal. Session types become a major setup object instead of a side setting.

What Stays the Same

Quotes still exist
Documents still exist
Communication threads still exist
Billing still exists
Portal Foundation still controls branding and routing

Can You Switch Later?

Yes. The plugin stores mode in Portal Foundation settings. Switching later changes the shell emphasis and labels, but it does not rip out the underlying post types or core systems.

Practical Advice

If more than half of your real work revolves around sessions, questionnaires, proofing, delivery, and print sales, choose photographer mode. If more than half of your real work revolves around longer project timelines, scoped deliverables, and developer-style onboarding, choose developer mode.

Was this helpful? If something is missing or wrong, I want to know.

Send feedback