Secure Drupal CMS Website Build
Budget / Salary$30–250
TypeFreelance project
LocationRemote
Posted1 hour ago
I already have the basic layout, images, and some starter code ready to go; what I need now is a Drupal specialist to turn it into a fully-functioning, modern-looking site. The overall aesthetic should stay modern and clean, matching the mock-ups I’m providing.
Core requirements
• Drupal is the chosen platform—please keep the build native to Drupal (latest stable release).
• The entire site (front end and back end) must be protected by a login wall.
• If a visitor is an active user, the login form will ask only for their registered e-mail address; the system then emails a one-time code they must enter before gaining access.
• A “COS” section exists that should remain visible to admins only. Regular users must never see or guess its path.
• Every element on the front end—including hero images, text blocks, menus, and even newly created pages—must be editable from the admin dashboard without touching code.
• Content type: an “Investment” type is required so I can publish, edit, and archive investment items as easily as I would blog posts. Please set up fields (title, summary, body, attachments, etc.) accordingly.
Deliverables
– Theme integration: apply the supplied HTML/CSS/images and keep the modern-clean feel.
– Custom modules or configuration for the e-mail code (OTP) login workflow.
– Role & permission setup that ensures only admins reach COS while authenticated users reach the standard front end.
– Flexible page builder or layout builder configuration so I can add pages later.
– Final testing on all common browsers and devices; no broken links, console errors, or permission leaks.
– Deployment instructions or a short hand-off call so I can maintain the site confidently.
Acceptance criteria
1. Logging in via e-mail + OTP works end-to-end with real e-mails (no dummy data).
2. Non-admin users cannot access /cos or any of its children URLs.
3. I can create, edit, and delete Investment items and see changes immediately on the front end.
4. All text and media shown on the mock-ups are editable from the admin UI.
5. No PHP notices, Drupal warnings, or console errors appear after a fresh cache rebuild.
If anything is unclear, tell me early so we can keep the project moving smoothly.
Core requirements
• Drupal is the chosen platform—please keep the build native to Drupal (latest stable release).
• The entire site (front end and back end) must be protected by a login wall.
• If a visitor is an active user, the login form will ask only for their registered e-mail address; the system then emails a one-time code they must enter before gaining access.
• A “COS” section exists that should remain visible to admins only. Regular users must never see or guess its path.
• Every element on the front end—including hero images, text blocks, menus, and even newly created pages—must be editable from the admin dashboard without touching code.
• Content type: an “Investment” type is required so I can publish, edit, and archive investment items as easily as I would blog posts. Please set up fields (title, summary, body, attachments, etc.) accordingly.
Deliverables
– Theme integration: apply the supplied HTML/CSS/images and keep the modern-clean feel.
– Custom modules or configuration for the e-mail code (OTP) login workflow.
– Role & permission setup that ensures only admins reach COS while authenticated users reach the standard front end.
– Flexible page builder or layout builder configuration so I can add pages later.
– Final testing on all common browsers and devices; no broken links, console errors, or permission leaks.
– Deployment instructions or a short hand-off call so I can maintain the site confidently.
Acceptance criteria
1. Logging in via e-mail + OTP works end-to-end with real e-mails (no dummy data).
2. Non-admin users cannot access /cos or any of its children URLs.
3. I can create, edit, and delete Investment items and see changes immediately on the front end.
4. All text and media shown on the mock-ups are editable from the admin UI.
5. No PHP notices, Drupal warnings, or console errors appear after a fresh cache rebuild.
If anything is unclear, tell me early so we can keep the project moving smoothly.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.