File Structure

Here’s our specs wardrobe—how WordPress site files organized at Presslabs, e.g. themes, plugins, uploads, as well as the special location for the files served at the root of the domain.

Various parts of the site hosted with us are stored in different places and you can find here more details about it.

WordPress core files

The core files of WordPress are always read-only as the core should never be altered in any way. In case you need to alter various default behaviours of WordPress, please use hooks and filters . Besides being read-only, the core files are not visible through Gitea for the same reason as they are meant to be read-only. You can find more details about this on our security page.

Themes and plugins

The code of your site is stored on our Git stack . Besides themes and plugins, we also store here other folders such as languages or other folders that might be created by plugins. All changes done on these files, no matter if they’re done from Gitea or the WordPress Editor, are stored as Git commits.

Files and folders from the root folder

In case you need to place a file or folder directly in the root of your site, these files need to be added in the folder wp-content/root/. The content of this folder is stored on Git, therefore if you need to place files that are downloaded, or large attachments, then we recommend placing them inside a folder from wp-content/uploads/. That’s the place where static files should stay.

For example, in case you need to verify the domain ownership by placing a file called verify.html in the root of your site, then you need to copy this file in wp-content/root/verify.html and it will become available at Folders work too, but you can’t add a folder called root (e.g.

Images & attachments

These files are stored by WordPress in wp-content/uploads/ and the contents of this folder are stored in Persistent Volumes , which are are resources in Kubernetes similar to ssd/hdd disks. When a site is created, a Persistent Volume is created for it. The uploads files are automatically mounted in the site’s container. When a WordPress pod claims the Persistent Volume, it turns into a Persistent Volume Claim, which practically is a request for storage by a user.