Organiser les images d'un site touristique avec Cloud Storage et Claude Code

Les sites touristiques mélangent souvent photos de saison, chambres, plats, événements, photos internes et assets de photographes dans un même dossier. Le prochain éditeur ne sait plus ce qui est autorisé, expiré ou soumis à crédit.

Cet article transforme Cloud Storage en workflow d’images vérifiable. Claude Code rédige les règles de nommage, champs metadata, alt text et checklist. Les humains confirment droits, personnes visibles, crédit, portée publique et marque.

Points Clés

• Start from a tourism page, image folder, and rights memo, not from a generic storage tutorial.
• Cloud Storage object names, metadata, public scope, alt text, and reviewer need one registry.
• Claude Code drafts names, metadata, alt text, and checklists; humans confirm legal and brand decisions.
• The main CTA is training because image rights and publishing workflow are site-specific.
• Measure ROI with image replacement time, missing alt text, rights review misses, and booking clicks.

Scène d’Échec

Les références officielles couvrent metadata objet, prévention d’accès public, hébergement statique, SEO Google Images et metadata de licence. Use Cloud Storage object metadata, Cloud Storage public access prevention, Cloud Storage static website hosting, Google Images SEO best practices, Google image license metadata as anchors. The platform can store and serve files, but it cannot decide if a tourism photo is licensed for the website, advertising, or social media.

The common failure is treating a file in a bucket as a file approved for publication. A better workflow separates storage, rights, page context, alt text, and reviewer approval.

Workflow Avant Publication

Collect the current bucket, object list, local photo folder, page URL, photographer memo, license email, current alt text, and publication plan. Mask private notes and do not publish images with people before review.

Create one registry row per image. The row should contain objectName, pageUrl, rights, credit, expiry, altText, publicScope, and reviewer. This is easier to review than a loose folder full of images.

Périmètre de Claude Code et Revue Humaine

Claude Code can create naming rules, custom metadata suggestions, alt text drafts, and missing-field questions. It can also mark unknown rights or visible people as review-needed.

Humans confirm rights, credits, people in the photo, public scope, deletion requests, and brand fit. If the rights field is blank, the image should not be published.

Trois Use Cases

Use case 1: Registre d’images relié aux objectName

• Input: Cloud Storage object list, image folder, location, season, page URL.
• Output: objectName, place, season, use, page URL, replacement candidate.
• Human review: location match, old facility photos, people in image, forbidden use.

Use case 2: Revue des droits et de la portée publique

• Input: photographer memo, license email, contract terms, target page, social media plan.
• Output: web allowed, ads allowed, social blocked, expiry, credit required, review-needed.
• Human review: license scope, people, credit, expiration date, deletion contact.

Use case 3: Alt text aligné sur le contexte de page

• Input: image, heading, nearby text, facility name, season, location.
• Output: alt text, caption draft, image replacement list.
• Human review: keyword stuffing, inaccurate location, invented content, brand wording.

Prompt à Copier

Act as a tourism image management reviewer.
Goal: create a Cloud Storage image registry with rights, public scope, alt text, page URL, and human review.
Inputs: bucket, object list, page URL, location, photographer, license note, current alt text, people in photo.
Outputs: registry columns, naming rule, metadata suggestion, alt text drafts, review-needed list, publishing checklist.
Rules: never mark unknown rights as public, avoid keyword stuffing, keep credit and expiry visible, use /training/ as CTA.

La première action consiste à choisir vingt images des principales pages touristiques et noter objectName, pageUrl, rights, credit, altText, publicScope et reviewer. Ne marquez pas une photo comme publique avant la revue humaine des droits.

Code de Vérification

const imageRecord = {
  bucket: "tourism-assets-prod",
  objectName: "kyoto/spring/kiyomizu-terrace-001.jpg",
  pageUrl: "/travel/kyoto/spring/",
  rights: "web use approved until 2027-03-31",
  creatorCredit: "Masa Photo",
  altText: "Spring view from Kiyomizu temple terrace in Kyoto",
  publicScope: "approved website pages only",
  reviewer: "content owner checks rights and people in photo",
  cta: "/training/"
};

const required = [
  "bucket",
  "objectName",
  "pageUrl",
  "rights",
  "creatorCredit",
  "altText",
  "publicScope",
  "reviewer",
  "cta"
];

const missing = required.filter((key) => !imageRecord[key]);

if (missing.length > 0) {
  throw new Error("Missing tourism image fields: " + missing.join(", "));
}

if (imageRecord.altText.length < 20 || imageRecord.altText.length > 125) {
  throw new Error("Alt text should be short but descriptive.");
}

if (!imageRecord.cta.startsWith("/")) {
  throw new Error("CTA must be an internal path.");
}

console.log("Tourism Cloud Storage image record is ready for rights review.");

The code checks whether the image registry has the minimum fields. A real implementation can run the same idea against exported object metadata, CMS image lists, or Markdown frontmatter.

Pitfall: Publier Avant la Revue des Droits

Cause: the team assumes bucket storage equals publishing approval. Fix: keep a separate rights field and reviewer. Cause: alt text becomes a keyword list. Fix: describe the actual image and its page context.

Cause: credit and expiry live only in a page draft. Fix: keep them in the registry or metadata plan so they travel with the image.

Questions Fréquentes

Q. Is an image public just because it is in Cloud Storage?

A. No. Storage location and publishing approval are different. Rights, public scope, credit, and people in the photo need review.

Q. What should alt text contain?

A. It should describe what is visible and why it relates to the page. Avoid keyword stuffing and invented details.

Q. Where should the conversion path go?

A. For image governance and publishing workflow, send readers to training. The reader often needs a review process, not only a storage snippet.

Chemin de Consultation

The business path is training or consultation. A tourism site with many photos needs a registry, rights workflow, alt text template, and publishing approval path. The article shows the first twenty-image step.

Résultat Vérifié

I verified the slug, frontmatter, internal CTA, external official references, executable JavaScript, code fence, FAQ, pitfall section, and human review path. The next action is to pick twenty live images and check blank rights or alt text fields.