Begin with the editing and user journeys
List who edits content, who uses private functions and which actions need approval. Ask someone to demonstrate a routine update. A marketing team publishing articles needs a different daily experience from staff managing quote revisions or customers checking account-specific records.
WordPress includes content-publishing tools, revisions and an extensible theme/plugin ecosystem. It can support more than brochure sites. Django provides an application framework with models, forms and an authentication foundation; the required public and workflow interfaces still need implementation.
Compare complete solutions, including extensions
For each option, identify what is available in the proposed configuration, what requires an extension and what must be custom-built. Check who maintains each dependency, how updates are tested and whether records can be exported in a usable form.
Illustrative example, not a client result: a consultancy mainly publishes service information and articles. Another team needs customer-specific quote versions, approver roles and integration failures routed to staff. Compare the actual solutions for those tasks rather than selecting a framework by popularity.
Test permissions and administration
Decide which records a customer, staff member and administrator may view or change. A hidden menu item is not sufficient access control. Test direct links and export endpoints as another user.
The Django admin is documented as an internal management tool. A customer portal or process-led approval screen may need dedicated views. On a WordPress proposal, inspect the actual roles and extension behaviour with the same scrutiny; do not assume a plugin label proves the complete policy.
Budget for operation rather than just launch
Compare hosting, backups, restore testing, dependency updates, monitoring, account access and the future maintainer's work. WordPress hardening guidance and Django's security guidance both make operating practices important. A platform name is not a security guarantee.
Search visibility also depends on the resulting site. Check actual public URLs, useful content, crawlable links, metadata and performance. Neither option guarantees a ranking, and a custom build is not automatically faster or cheaper.
Choose the smallest maintainable fit
Keep a working platform when it meets the requirements. Consider configuration or a connected service before rebuilding it. Document the reasons a chosen solution fits, the unresolved risks and how data and source access will be handed over.
The website versus application guide helps define the brief. For a justified custom build, the Django-fit guide focuses on records, rules and ownership.
Related service scope
- Web Development: Discuss the public website scope.
- Django development: Assess a custom Django application brief.