Document a one-time project ZIP

Upload a project ZIP when you cannot connect a supported Git provider. DocuWriter imports the archive as a source snapshot for Full Tree Documentation.

Prepare the archive

Include the project's meaningful source and configuration files. Exclude credentials and unnecessary generated or dependency directories. A ZIP containing only images, documentation or other non-source assets cannot provide the source evidence needed for this workflow.

Upload and generate

  1. Open Full Tree Documentation.
  2. Select Can't connect a repository? Upload a ZIP instead.
  3. Choose a .zip file within the size limit shown in the upload control.
  4. Select Upload Project ZIP and wait for validation and import.
  5. Review the documentation outline and continue with complete documentation generation.

The same alternative is available in onboarding's Connect code step. Large archives take time to upload and inspect. An upload finishing does not mean its source import or documentation generation has finished.

What a snapshot does not do

A ZIP does not authorize a Git provider. It has no ongoing webhook delivery, code-change detection, Autopilot repository sync, pull-request comments or branch-comparison release notes. To document newer source, upload a newer snapshot and run the workflow again.

If the archive is rejected

Read the validation message and rebuild the archive from the intended project root. Check that it is a valid, unencrypted ZIP with actual project source, rather than a package of compiled assets or documentation alone. Avoid repeating the same rejected upload unchanged.

Prefer a Git connection when ongoing maintenance is part of your goal.

Updated