site-web

byNassim Riahi

Since Astra can’t access your PPTX, ask it to create the presentation from your description and screenshot. Paste this prompt: Create a polished 20-slide final-year internship presentation in French for **Nassim Riahi**, about **the creation and redesign of the Cléopâtre parapharmacy website** in Ezzahra / Hammam-Lif, Tunisia. Use the attached screenshot as the visual reference. Recreate its handmade collage style: charcoal textured backgrounds, torn off-white paper panels, bold hand-drawn headings, playful doodles and icons, with yellow, magenta, blue, and white accents. Keep the style consistent across every slide while varying layouts to suit the content. Make it look professionally designed and presentation-ready, with clear hierarchy, readable text, balanced spacing, and no overcrowding. ### Presentation structure 1. **Title slide** — “Création et refonte d’un site web”, “Parapharmacie Cléopâtre”, “Présenté par Nassim Riahi”. 2. **Sommaire** — Introduction, Problématique, Solution proposée, Spécification des besoins, Besoins fonctionnels, Besoins non fonctionnels, Conception UML, Diagrammes, Implémentation, Conclusion et perspectives. 3. **Introduction générale** — Briefly introduce the internship, Cléopâtre parapharmacy, the project, and its purpose. 4. **Problématique** — Explain the need for a modern online presence and a smoother way for customers to discover products and place orders, without inventing statistics. 5. **Solution proposée** — Present the redesigned website, online product catalogue, customer-facing space, ordering journey, and administration back-office. 6. **Spécification des besoins** — Introduce the functional and non-functional requirements. 7. **Besoins fonctionnels** — Summarize customer and administrator capabilities in two clear groups. 8. **Besoins non fonctionnels** — Cover usability, responsive design, security, performance, reliability, and maintainability. 9. **Conception UML** — Introduce the design phase and preview the UML diagrams used to describe the system. 10. **Diagramme de cas d’utilisation** — Create a clear, large placeholder area labeled “Insérer l’image du diagramme de cas d’utilisation”. Do not invent or draw the diagram. 11. **Diagramme de séquence : mise à jour du profil** — Create a large placeholder labeled “Insérer l’image du diagramme de séquence — Mise à jour du profil”. Do not invent or draw the diagram. 12. **Diagramme de séquence : suppression d’un produit** — Create a large placeholder labeled “Insérer l’image du diagramme de séquence — Suppression d’un produit”. Do not invent or draw the diagram. 13. **Diagramme de séquence : ajout d’une commande** — Create a large placeholder labeled “Insérer l’image du diagramme de séquence — Ajout d’une commande”. Do not invent or draw the diagram. 14. **Diagramme de classe** — Create a large placeholder labeled “Insérer l’image du diagramme de classe”. Do not invent or draw the diagram. 15. **Réalisation** — Introduce the implementation and show the transition from design to a working website. 16. **Environnement technique** — Present only these technologies: Next.js 16, React 19, TypeScript, Tailwind CSS, PostgreSQL, Drizzle ORM, Zod, Framer Motion, GSAP, and ScrollTrigger. Arrange them into clear categories and avoid adding technologies. 17. **Démonstration : espace client** — Create a large video placeholder labeled “Insérer la vidéo de démonstration — Espace client”. Leave it empty for me to add the recorded video. 18. **Démonstration : espace administrateur** — Create a large video placeholder labeled “Insérer la vidéo de démonstration — Espace administrateur”. Leave it empty for me to add the recorded video. 19. **Conclusion générale et perspectives** — Summarize the project outcome and suggest reasonable future improvements without claiming features that are not implemented. 20. **Merci** — A clean closing slide: “Merci pour votre attention” and “Questions ?” ### Transitions and motion Make the deck feel dynamic and premium, with a coherent **Morph-style transition plan** between slides: maintain shared visual anchors such as a small lightbulb, torn-paper edges, recurring accent strokes, or section markers, and move or transform these elements naturally between related slides. Use subtle, purposeful object animations for headings, cards, and icons. Keep motion smooth and restrained so it supports the presentation rather than distracting from it. If the presentation tool supports true Morph transitions, apply them where elements can visibly carry over between slides. If it does not, use the closest available smooth transition and keep recurring elements positioned consistently to suggest continuity. Do not claim Morph was applied if it is unavailable. ### Quality requirements - Keep all slide titles and body copy in French, with correct accents and spelling. - Preserve the exact 20-slide order above. - Use concise presentation text, not paragraphs copied onto slides. - Make the five UML slides and two video slides clear placeholders for my own images/videos. - Keep typography, colors, spacing, icon style, and footer treatment consistent throughout. - Ensure every slide is readable at presentation size and visually aligned with the screenshot’s handmade collage design.

No preview

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirement Document
📝

Requirements Not Generated Yet

The SRD will be automatically generated as you discuss your project with the Tech Lead Agent.

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.

No user flows yet.

The User Flow Agent will generate per-persona navigation diagrams after SRD updates.

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.

No user flows yet.

The User Flow Agent will generate per-persona navigation diagrams after SRD updates.