Atelier | Décroche ton stage

We need to reformat the job posting (actually event posting) into clean semantic HTML. Use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the French event description. The event: "Atelier | Décroche ton stage" (Workshop: Get your internship). It's about BAIP offering workshops on internship search. Three themes: Cibler ses candidatures, Optimiser son CV et sa lettre de motivation, Préparer ses entretiens. Dates: Lundi 28 et mardi 29 septembre de 10h à 12h. Inscriptions obligatoires sur cette page, dans la limite des places disponibles! Lieu: Manufacture des Tabacs (la salle vous sera transmise par mail après votre inscription). Also mention: "À ne pas manquer aussi : apprenez à rédiger vos candidatures et à préparer vos entretiens en anglais avec l'atelier "It's time to apply!". Plus d'infos en cliquant ici." Then there is a list of registration options: "Je m'inscris à l'atelier décroche ton stage le 28/09 à 10h" etc. There's also a form for participant type: Etudiant / Ancien diplômé à l'université Jean Moulin, etc. Then fields: Prénom, Nom, Email, Téléphone, Numéro d'étudiant, Diplôme, Niveau d'étude (list), Entreprise, Comment avez-vous eu connaissance de l'atelier ?, Des informations complémentaires à nous soumettre ?, Quelles sont vos attentes par rapport à cet évènement ou cet atelier ?, Ajouter une pièce-jointe. We need to remove application instructions? The instruction says: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The registration form is essentially application instructions. Should we remove them? The instruction says remove application instructions. So we should not include the form fields. Also remove duplicated lines. Keep substantive info: description of event, themes, dates, location, note about English workshop, maybe mention places remaining? The "places restantes : 30" and then specific slots with 15 places each. That's substantive info about availability. Should we keep that? It's not boilerplate; it's info about capacity. Likely keep. We need to decide sections: Could have About the event (description), Themes (list), Date & Time (maybe Schedule), Location, Registration info (places left). Since we cannot create Pay/Benefits unless stated. No pay/benefits. Schedule: we have date and time. Could put under

  Schedule

  with

  or

  . The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use Schedule heading for date/time. Also maybe About the event heading (About the role analog). Themes could be under Requirements? Not exactly. Could use Skills? But better to use a generic heading like "Details" but they only gave examples; we can still use other headings? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Probably we should stick to those headings where applicable. We have no role, responsibilities, requirements, qualifications, skills, benefits, pay. We have schedule. So we can use

  Schedule

  . For other info, we could use

  without heading? But they said include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can have headings only for sections we have content. We could have

  About the event

  (though not in list, but similar to About the role). Might be acceptable. Or we could just use

  for description and then

  Schedule

  for date/time, and maybe

  Location

  (not in list but okay). The instruction didn't forbid other headings, just gave examples. Safer to use headings that make sense: About, Themes, Schedule, Location, Availability. We need to use
  • for any list of duties/requirements/benefits. Themes is a list, so use
    • . Also maybe list of study levels? That's part of form, which we remove. So not needed. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the description text exactly? We can rephrase? Probably we should keep the meaning but not necessarily verbatim? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep all info, but we can format it. We can keep the sentences. Let's extract substantive info: - Event: Atelier | Décroche ton stage - Organizer: Bureau d'Aide à l'Insertion Professionnelle (BAIP) - Purpose: participer à différents ateliers thématiques autour de la recherche de stage ! - Three themes available: 1. Cibler ses candidatures 2. Optimiser son CV et sa lettre de motivation 3. Préparer ses entretiens - Dates and hours: Lundi 28 et mardi 29 septembre de 10h à 12h. - Inscriptions obligatoires sur cette page, dans la limite des places disponibles ! - Lieu: Manufacture des Tabacs (la salle vous sera transmise par mail après votre inscription). - Also: À ne pas manquer aussi : apprenez à rédiger vos candidatures et à préparer vos entretiens en anglais avec l'atelier "It's time to apply!". Plus d'infos en cliquant ici. - Registration slots: - Je m'inscris à l'atelier décroche ton stage le 28/09 à 10h (La salle vous sera transmise par mail.) 28 septembre 2026 10h00 à 12h00 15 places restantes - Je m'inscris à l'atelier décroche ton stage le 29/09 à 10h (La salle vous sera transmise par mail.) 29 septembre 2026 10h00 à 12h00 15 places restantes - Total places restantes: 30 (maybe overall) - Participant type options (we may drop as application instructions) - Form fields (drop) - File upload instructions (drop) We should drop the registration form and participant type options as they are application instructions. Also drop the "Retour à la liste", "Lien De Partage", "Votre adresse e-mail :", "Ajouter l'événement à mon calendrier", "Inscription Déjà un compte sur U3e ? Identifiez-vous avant de réserver une place." etc. Those are navigation/UI. We need to keep the info about places restantes: 30 and each slot's 15 places restantes. We should not include the duplicated lines like "La salle vous sera transmise par mail." appears twice; we can keep once per slot. We need to avoid filler like "commensurate with experience". Not present. Now produce HTML. We'll start with

      About the event

      ... description ...

      Then

      Themes

      • ... etc
      Then

      Schedule

      Lundi 28 et mardi 29 septembre de 10h à 12h.

      Then

      Location

      Manufacture des Tabacs (la salle vous sera transmise par mail après votre inscription).

      Then maybe

      Availability

      Places restantes : 30. Deux créneaux disponibles : 28 septembre 2026 de 10h00 à 12h00 (15 places restantes) et 29 septembre 2026 de 10h00 à 12h00 (15 places restantes).

      Then maybe

      Additional workshop

      À ne pas manquer aussi : apprenez à rédiger vos candidatures et à préparer vos entretiens en anglais avec l'atelier "It's time to apply!". Plus d'infos en cliquant ici.

      We need to ensure we don't include application instructions like "Inscriptions obligatoires sur cette page, dans la limite des places disponibles !" That's substantive? It's instruction to register. Might be considered application instruction. The instruction says remove application instructions. That line is basically telling to register. Should we remove? It's part of event info. Might be considered necessary. But it's an instruction to register. The instruction says remove application instructions. I'd interpret that as things like "To apply, send your CV to..." etc. The line "Inscriptions obligatoires sur cette page, dans la limite des places disponibles !" is more like a note that registration is required and limited. Might be okay to keep as it's event info. However, it's borderline. To be safe, we could keep it as part of description. We also need to avoid duplicated lines. The phrase "La salle vous sera transmise par mail." appears in each slot; we can keep once per slot or combine. Let's craft HTML. We must not include markdown fences. Just raw HTML. Let's produce:

      About the event

      Atelier | Décroche ton stage organisé par le Bureau d'Aide à l'Insertion Professionnelle (BAIP) pour participer à différents ateliers thématiques autour de la recherche de stage.

      Themes

      • Cibler ses candidatures
      • Optimiser son CV et sa lettre de motivation
      • Préparer ses entretiens

      Schedule

      Lundi 28 et mardi 29 septembre de 10h à 12h.

      Location

      Manufacture des Tabacs (la salle vous sera transmise par mail après votre inscription).

      Availability

      Places restantes : 30. Deux créneaux disponibles : 28 septembre 2026 de 10h00 à 12h00 (15 places restantes) et 29 septembre 2026 de 10h00 à 12h00 (15 places restantes).

      Additional workshop