Directoryz

Move a spreadsheet directory into a published site

Migration should preserve useful information while improving the visitor experience. Copying every spreadsheet column can expose internal notes or clutter the listing.

Directoryz editorial guide · Updated September 7, 2026

Put it into practice

Separate public fields from operating fields, define stable identities, and test a sample import. Keep the original sheet as a reference during review.

Worked example · illustrative

What this looks like

Internal review comments stay private while the product name, task, and documentation link become public listing fields.

Before you move on

Did the migration preserve meaning without publishing internal-only information?

Write down the evidence for your answer. If you cannot point to a concrete example, revise the work before treating it as ready.

A repeatable workflow

  1. Identify the current public destination.
  2. Test the new destination with representative pages.
  3. Record how visitors and editors will find the published directory.

Your working notes

Apply this guide to one real project. Notes stay in this page until you download them; they are not saved to your account.

Where Directoryz fits

Directoryz supports directory publishing, listings and custom fields, CSV imports, submission review, and workspace operations. These guides include editorial workflows you can carry out with a worksheet or your own tools. They do not imply that every audit, reminder, verification, or integration is automated by Directoryz.

Foundations and templates →