Blog Platform Feature Development
Budget / SalaryHourly project
TypeFreelance project
LocationRemote
Posted1 hour ago
I need a developer who can jump straight into the codebase of my blog-style website and handle both new feature development and any fixes that crop up. My priority is the technical layer—database calls, API endpoints, page-load optimisation, and anything else that keeps articles loading smoothly—so you’ll be writing or refactoring code rather than writing the actual posts.
Because this project centres on “building or fixing software or technical features,” I expect you to work comfortably with the usual stack for content-heavy sites (think PHP, Node, Python, or similar on the back end and a modern front-end framework if needed). If you have CMS experience (WordPress, Ghost, Strapi, custom builds) that’s a plus, since all changes must keep the publishing workflow for “blog posts or articles” intact.
Core objectives
• Diagnose and resolve the current issues affecting article pages (error logs and steps to reproduce provided once we start).
• Ship at least one requested enhancement—likely a new categorisation filter or an improved editor view—without interrupting live traffic.
• Write clean, documented code so future maintenance is straightforward.
When you hand over, I’ll test everything on staging first; final acceptance happens after it passes on production.
If you’re used to moving quickly, communicating clearly, and leaving the codebase better than you found it, I’d love to hear how you’d tackle this.
Because this project centres on “building or fixing software or technical features,” I expect you to work comfortably with the usual stack for content-heavy sites (think PHP, Node, Python, or similar on the back end and a modern front-end framework if needed). If you have CMS experience (WordPress, Ghost, Strapi, custom builds) that’s a plus, since all changes must keep the publishing workflow for “blog posts or articles” intact.
Core objectives
• Diagnose and resolve the current issues affecting article pages (error logs and steps to reproduce provided once we start).
• Ship at least one requested enhancement—likely a new categorisation filter or an improved editor view—without interrupting live traffic.
• Write clean, documented code so future maintenance is straightforward.
When you hand over, I’ll test everything on staging first; final acceptance happens after it passes on production.
If you’re used to moving quickly, communicating clearly, and leaving the codebase better than you found it, I’d love to hear how you’d tackle this.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.