CMS, Frameworks & Git Source

WordPress: themes are one part of the site

A WordPress project combines files with database content and settings. The WordPress theme architecture documentation describes how server-side code, database information, and theme assets work together. Versioning a custom theme or plugin does not capture every post, setting, and uploaded image on the live site.

Decide which custom code belongs in Git, how dependency versions are recorded, and how content moves between environments. Avoid overwriting active editorial changes during a code deployment. Our WordPress and CMS workflow guide explains how to keep those responsibilities visible.

Hugo: source becomes published files

With Hugo, content, layouts, configuration, and assets form the build inputs. The build produces a static site, normally in a public directory. Decide where that build runs and publish its intended output. A contributor should be able to identify the source revision and tool configuration used for a release.

Review draft handling, internal links, and generated feeds before publishing. Include a process for obsolete output so a deleted source page does not remain online accidentally. The static deployment guide connects this build workflow with shared hosting, servers, and managed deployment services.

Django: application code needs an environment

A Django repository can include Python application code, templates, dependency declarations, tests, and database migrations. The running application also needs configured services and operational settings. The Django deployment checklist distinguishes deployment settings, static files, and uploaded media, including the need to protect and back up user uploads.

Plan code releases and database changes together. Explain whether a migration is compatible with the previous application version and what recovery requires. Store example settings without real credentials, and document the environment needed to reproduce a useful local or staging instance.

LAMP describes a serving stack

LAMP refers to a Linux, Apache, database, and PHP stack, commonly using MySQL. It describes an operating environment rather than a Git repository layout. Identify the PHP code, server configuration, database state, and uploaded files your project needs. Then decide which parts can be deployed from source and which require separate administration.

A repository checkout alone does not establish that the server has the right runtime, extensions, permissions, or data. The Hugo, Django, and LAMP comparison helps you write an explicit deployment inventory instead of treating every website as interchangeable files.

Create one release inventory

1. List the editable source and the team responsible for reviewing it.
2. Record build inputs and the output directory that may be published.
3. Identify databases, uploads, and other persistent runtime state.
4. Document environment configuration and credential handling.
5. Test a release and recovery procedure in a disposable environment.

Use the backup and security hub to complete the recovery side. A working source checkout is valuable evidence, but a usable site may need several restored components.