Last updated 10 February 2018.

Best first action you can take is to watch this Randy Fay's video tutorial

A sandbox project is a module or theme that contains experimental code that is not yet ready for general use. Full projects are for general use. Any user who has obtained basic Git access on can create sandbox projects. To create a full project, or to promote your existing sandbox project to a full project, you must go through a one-time approval process.

Sandbox projects have most of the features of full projects; for example, a project page, a Git repository, an issue queue, the ability to appoint co-maintainers, and so on. There are a few key differences whose main purpose is to steer hapless end users away from stumbling across potentially insecure code.

Key differences between "sandbox" and "full" projects

  • Sandbox project pages display an Experimental Project warning message with a yellow background.
  • Sandbox project URLs are /sandbox/username/node-id, rather than a human-readable short name such as /project/views.
  • You cannot create releases (downloadable files) of sandbox projects; the only way to obtain them is via Git.
  • Sandbox projects do not appear in the Main project issue drop-down. To add an issue to a sandbox project, you must do it directly from the project's own issue queue.


yktdan’s picture

of the code supported by the project on the sandbox page.

Walt Daniels

texas-bronius’s picture

Is it appropriate to, and if so is there a convention for, adding documentation as d.o handbooks for sandbox projects?

80s themed Drupal T-Shirts

Road Runner’s picture

I entered the following proximity then created a git access and tried some other stuff 404 error - can you provide some insight here. TIA
The above link doesn't work but I got it sorry for the trouble.

delacosta456’s picture


may be you should check here