Reference
Frequently asked questions
Answers to the questions clients usually ask before using Devport.
Common questions
| Question | Answer |
|---|---|
| Do I need to know code? | No. Devport is built for approved client updates without code. |
| Can I change every part of my website? | No. You can change approved fields. Larger design and technical changes stay as developer service work. |
| Why are only some fields editable? | Approved fields protect layout, brand structure, and website behavior. |
| Can I replace images? | Yes, when the developer has approved the image slot for replacement. |
| Does save change the live website? | No. Save stores a draft so you can preview before publishing. |
| What happens when I publish? | Devport sends approved changes through the managed website update path and then shows deployment status. If your workspace requires paid access, Devport asks you to activate publishing before the change goes live. |
| Can my team use Devport? | Team access depends on the assigned workspace and users approved by the developer or Devport operator. |
| Can I access GitHub or Vercel? | No. Devport keeps repository, hosting, and provider settings managed by the developer or provider owner. |
| Is my site still custom-coded? | Yes. Devport is the safe editing layer attached to the coded site. |
| Who do I contact for help? | Email support@mydevport.com for Devport support. |
Still unsure?
If you are unsure whether a change belongs in Devport or should be handled as developer service work, contact support with the page, field, and change you want to make.
Related reading
What is Devport?Devport gives clients a safe way to edit approved words and images on custom-coded websites.SupportUse support@mydevport.com for access, billing, drafts, images, preview, publish, and deployment questions.GlossaryA plain-language reference for the words Devport uses in the portal and documentation.