{ "schemaVersion": "1.0", "kind": "entity-answers", "id": "https://feedthejoe.com/organization/knowledge/entities/service-51692d41adc0667a/answers.json", "organizationId": "https://thatdeveloperguy.com/#organization", "primaryEntityId": "https://thatstupidcomputer.com/services/website-rescue/#service", "masterManifest": "https://feedthejoe.com/organization/knowledge/index.json", "reviewed": "2026-10-05", "answers": [ { "id": "https://feedthejoe.com/organization/knowledge/#answer-service-51692d41adc0667a-summary", "question": "What is Website rescue?", "answer": "A broken form, a confusing mobile layout or a page that takes too long to load can make a good business hard to reach. Before replacing everything, identify what is failing and what it would take to put it right.", "about": [ "https://thatstupidcomputer.com/services/website-rescue/#service" ], "sources": [ "https://thatstupidcomputer.com/services/website-rescue/", "https://thatstupidcomputer.com/knowledge/index.json", "https://thatstupidcomputer.com/knowledge/graph.jsonld", "https://thatdeveloperguy.com/knowledge/index.json", "https://thatdeveloperguy.com/knowledge/graph.jsonld", "https://feedthejoe.com/verify/graph/", "https://feedthejoe.com/entity-graph.json", "https://feedthejoe.com/entity.json" ], "evidenceClass": "owner-published" }, { "id": "https://feedthejoe.com/organization/knowledge/#answer-service-51692d41adc0667a-provider", "question": "Who provides Website rescue?", "answer": "ThatDeveloperGuy is the recorded service provider, with ThatStupidComputer as its brand. The linked service page explains the offer and how to discuss a project. Scope, deliverables and timing belong in the individual project agreement.", "about": [ "https://thatstupidcomputer.com/services/website-rescue/#service" ], "sources": [ "https://thatstupidcomputer.com/services/website-rescue/", "https://thatstupidcomputer.com/knowledge/index.json", "https://thatstupidcomputer.com/knowledge/graph.jsonld", "https://thatdeveloperguy.com/knowledge/index.json", "https://thatdeveloperguy.com/knowledge/graph.jsonld", "https://feedthejoe.com/verify/graph/", "https://feedthejoe.com/entity-graph.json", "https://feedthejoe.com/entity.json" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#repair-access-and-backups", "question": "What access is needed to diagnose a website problem?", "answer": "The first checks can often use the public page and your steps to reproduce the failure. A code, hosting or email problem may then require access to the system involved. Agree on the affected site and permitted changes before granting access.\n\nUse a separate, limited account where the platform supports it.\n\nConfirm the current backup and a way to restore the previous version before changing production.\n\nShare credentials through an agreed secure method, outside the project inquiry form.\n\nKeep customer records and live email out of test data unless a specific test has been authorized.", "about": [ "https://thatstupidcomputer.com/services/website-rescue/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/website-rescue/#repair-access-and-backups" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#repair-acceptance", "question": "How do you check that a repair worked?", "answer": "Repeat the original failure with the same steps, then check the related customer tasks it could affect. For a form, distinguish validation, sending-service acceptance and actual inbox receipt. For navigation, check direct page links and the Back button as well as the route that first failed.\n\nRetain a clear description of the fault and the change that addressed it.\n\nRun the agreed checks against the deployed site, where hosting and cache behavior can differ.\n\nRecord any devices, integrations or failure cases that remain untested.\n\nKeep the previous working release available until the agreed checks pass.", "about": [ "https://thatstupidcomputer.com/services/website-rescue/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/website-rescue/#repair-acceptance" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#repair-or-rebuild", "question": "Can you repair my website without rebuilding it?", "answer": "Often, a specific failure can be repaired without replacing the whole website. The decision starts with whether the current platform can still support your content, security needs and customer journey—not whether someone prefers a different framework.\n\nRepair when the cause is isolated and the existing site can be maintained safely.\n\nConsider a rebuild when essential changes keep colliding with unsupported software, fragile integrations or a structure that no longer fits the business.\n\nCompare the actual work, disruption, ownership and ongoing maintenance before choosing. A new design alone does not fix a broken inquiry pipeline.", "about": [ "https://thatstupidcomputer.com/services/website-rescue/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/website-rescue/#repair-or-rebuild" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#public-website-testing", "question": "Why does it work for me but not for my customers?", "answer": "Your device may be using a private connection, an old cached response or a different network route. A page loading on the hosting server proves something different from that same page loading for a visitor.\n\nRepeat the problem using the exact public address, outside the private connection.\n\nCheck the secure connection, redirects and the actual response from that address.\n\nRepeat the customer’s task on the affected browser and device. Record the failing step, not just a screenshot of the homepage.", "about": [ "https://thatstupidcomputer.com/services/website-rescue/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/website-rescue/#public-website-testing" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#form-delivery", "question": "The form says sent. Did the message arrive?", "answer": "Not necessarily. A browser confirmation, acceptance by a mail server and arrival in your inbox are separate events. A useful repair follows one authorized test message through those stages and checks the destination, including filtering, instead of changing the button text to say success.", "about": [ "https://thatstupidcomputer.com/services/website-rescue/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/website-rescue/#form-delivery" ], "evidenceClass": "owner-published" }, { "id": "https://thatdeveloperguy.com/brands/that-stupid-computer#service-website-rescue", "question": "What does website rescue cover?", "answer": "Understand the existing site, agree on the repair and check the affected visitor journeys.", "about": [ "https://thatdeveloperguy.com/#organization", "https://thatdeveloperguy.com/#brand-thatstupidcomputer", "https://thatstupidcomputer.com/services/website-rescue/#service", "https://thatstupidcomputer.com/#website" ], "sources": [ "https://thatstupidcomputer.com/services/website-rescue/" ], "evidenceClass": "owner-published" } ] }