A Website Change Log That Helps the Next Maintainer
Record meaningful website changes, reasons and verification results. Keep routine maintenance summaries clear without exposing credentials.
Read the guideThe NithuDev journal
Understand the everyday work behind a reliable website: hosting responsibilities, renewals, handover, monitoring and controlled releases.
Practical advice
41 published guides
Record meaningful website changes, reasons and verification results. Keep routine maintenance summaries clear without exposing credentials.
Read the guideSend the affected URL, steps and safe evidence when requesting website support. Keep passwords and private customer information out of public messages.
Read the guideInvestigate uploads, backups, logs and generated assets when hosting storage fills. Avoid deleting unknown folders or current recovery copies.
Read the guideReview scheduled tasks, timing assumptions and failure visibility. Keep cron configuration tied to the actual host and workflow requirements.
Read the guideInventory DNS records before moving hosting or nameservers. Keep email, verification and external services in the migration plan.
Read the guideReview current WordPress and extension requirements before a PHP change. Test important functionality and retain a supported rollback arrangement.
Read the guideRecord why each plugin exists, who maintains it and what depends on it. Review licences without deleting unfamiliar components blindly.
Read the guideKeep a concise record of symptoms, decisions and recovery checks during website incidents. Avoid filling logs and support messages with private data.
Read the guideChoose monitoring checks that reflect important public functions and a practical response plan. A successful homepage request does not prove every integration works.
Read the guideSet clear boundaries between development copies and the live website. Review indexing, emails, payments and private data before using staging.
Read the guidePlan a controlled restore rehearsal that verifies files, database content and recent business data. A backup archive alone does not prove recovery.
Read the guidePlan website updates with backup, access and relevant regression checks. Consider orders and bookings before choosing when to deploy.
Read the guide