
Webflow developer for ongoing magazine website maintenance
- or -
Post a project like this- Posted:
- Proposals: 61
- Remote
- #4521981
- Open for Proposals








Description
The site is already live. We need a developer who is comfortable taking over an existing Webflow project and helping when technical work comes up.
This may include small changes to the site, work on the CMS and article templates, fixing layout or responsive issues, checking custom code and integrations, and making sure the technical SEO is properly set up. We also need someone who checks their work carefully before and after publishing.
The website is content-heavy, so strong experience with Webflow CMS is important. Experience with magazines, publications or other editorial websites would be especially useful.
We would prefer to work with an independent developer or a small studio on an hourly or ad hoc basis. We do not need a large monthly retainer.
If you are interested, please send:
• two or three recent Webflow projects relevant to this kind of work
• an example of a website you took over from another developer, if you have one
• a few lines about your experience with Webflow CMS and technical SEO
• your hourly rate and any minimum charge
• confirmation of whether you would be doing the work yourself
Please only apply if you are comfortable working with an existing build. We are not looking for a new website or a redesign.
Ivan N.
100% (4)New Proposal
Create an account now and send a proposal now to get this project.
Sign upClarification Board Ask a Question
-

Could you share the Webflow project access or website URL for the initial review?
-

Questions
Could you share the Webflow project URL for the initial review?
Are there any known CMS, SEO, or responsive issues you want checked first?
Do you prefer the review and ongoing work to be billed hourly? -

For the initial 1–2 hour review, would you like me to assess the site broadly across CMS/article templates, responsive issues, custom code, integrations, and technical SEO, or is there a particular area or recurring issue you’d like me to investigate first?
-

When you hand over the site, what is the one recurring Webflow issue you most want to stop having to think about?
-

Hi Ivan,
I have a question: during the initial review, would you like the focus to be primarily on the CMS/article structure and technical SEO, or should I assess the entire site for any technical or responsive issues?
Best regards,
Jitendra -

A few things I’d like to clarify:
1. Could you share the live website and Webflow project access so I can understand the current CMS structure and implementation before the paid review?
2. Are there any known technical issues or priority fixes you would like me to investigate first?
3. How is your editorial content structured in Webflow such as single CMS collection for articles or multiple collections/templates?
4. Are there any existing custom integrations or code snippets that are particularly important to the publication?
5. Would you prefer the work to be handled directly by me, including communication and testing, rather than through another developer?
-

- How is your current Webflow CMS structured for articles and other editorial content? For example, do you have multiple CMS collections, authors, categories/tags, related articles, featured content, scheduled publishing, or other relationships between the collections that I should be aware of?
- Are there any recurring technical or responsive issues that your team currently experiences? If so, could you share a few examples of the pages or situations where they occur, including whether the issue is specific to desktop, tablet, mobile, or particular browsers?
- How would you prefer the ongoing workflow after the initial paid review? For example, should I review and estimate each task before starting, work directly from a shared task list, or handle small fixes immediately and provide an update once they are completed?