{"id":6340,"date":"2023-06-09T10:55:29","date_gmt":"2023-06-09T10:55:29","guid":{"rendered":"https:\/\/forest-1041a2.ingress-bonde.ewp.live\/why-web-developers-charge-for-small-website-changes\/"},"modified":"2023-06-09T10:55:29","modified_gmt":"2023-06-09T10:55:29","slug":"why-web-developers-charge-for-small-website-changes","status":"publish","type":"post","link":"http:\/\/benrmatthews.local\/why-web-developers-charge-for-small-website-changes\/","title":{"rendered":"Why web developers charge for small website changes"},"content":{"rendered":"
Just from a technical perspective, this might look like a simple change but the process may involve a number of steps. If the text is written into the code (we call it \u201chard coded\u201d) then the code needs updating. The code is probably \u201cversion controlled\u201d (revisioned) to keep it safe. If the code has not been touched for a while then someone may need to start by downloading a copy of it. They then need to make the change and test it to make sure they changed the right thing. Then \u201ccommit\u201d the change (save a new version of the code with your change in it) and re-upload it to where the code is stored. They may then need to \u201cdeploy\u201d the change using some process to send it to the hosting server and check\/test again once it\u2019s there.<\/p>\n<\/div>\n<\/div>\n