Loading...
Community presentation
Create a 20-slide presentation titled "ITI Weekly Checkpoint 2: What I Learned". PRESENTER: Micheal EL-Amir Fawzy Hakeem AUDIENCE: ITI supervisors reviewing what I benefited fro…
Create your own version
Use this visual direction as inspiration for a new Presenton deck.
Use this designCreator prompt
Create a 20-slide presentation titled "ITI Weekly Checkpoint 2: What I Learned". PRESENTER: Micheal EL-Amir Fawzy Hakeem AUDIENCE: ITI supervisors reviewing what I benefited from over the past weeks. PURPOSE: A student progress summary for the 2nd weekly checkpoint. Topics: SFML, Math, Physics (game physics), Git & GitHub. LANGUAGE: English. TONE: Simple, clear, student-friendly. EXPORT: PPTX and PDF. DESIGN BRIEF (apply to EVERY slide): - 16:9, dark navy background, white text, one teal accent color, one clean sans-serif font. - Title at the top of every slide in large text. Body text large and readable at presentation distance. - Maximum 6 bullets per slide, maximum 8 words per bullet. No paragraphs, no text overflow. - Simple icons only. No stock photos, no invented statistics, no speaker notes. - Every content slide ends with one short line starting with "Takeaway:" stating what I gained from that topic. SLIDES (use ONLY these topics; do not add anything outside them): 1. Title slide: "ITI Weekly Checkpoint 2: What I Learned", "Presented by Micheal EL-Amir Fawzy Hakeem", and the four topics: SFML | Math | Physics | Git & GitHub. 2. Agenda: SFML, Math, Physics, Git & GitHub. 3. SFML: what it is and how I used it (keep general, no invented details). 4. Math 1 - Functions: Function Inverse; Visualizing Functions (Graphs); Families of Functions: Absolute Value, Linear, Quadratic, Cubic, Exponential. 5. Math 2 - Matrices: 0 and I; Addition/Subtraction; Scalar Multiplication; Matrix Multiplication; Determinant (square matrices only); Transpose; Inverse; Systems of Linear Equations. 6. Math 3 - Transformations I: Linear Transformation; Shear; Isometric Coordinates in 2D games; Translation of a Point; Making Translation Linear. 7. Math 4 - Transformations II: Scaling Matrix; Skewing Matrix; Rotation Matrix; Euler Angles (Yaw, Pitch, Roll); Projection Matrix and making it linear. 8. Math 5 - Trigonometry: Angles; Polar Coordinates; Triangles; Trig Functions and Graphs; Modeling Waves; Circle and Ellipse; Inverse Trig Functions; Identities. 9. Math 6 - Trigonometry in Games: Projecting 3D Geometry onto a 2D Screen; Rotating Points. 10. Math 7 - Quaternions: Imaginary Numbers (i); Complex Numbers Geometric Representation; Intro to Quaternions; Pure Quaternions; Quaternion Algebra; Gimbal Lock; Quaternion Rotation. 11. Math 8 - Vectors: Unit Vector; Direction/Normalization; Addition/Subtraction; Dot Product; Cross Product; Lerp; Kinematic Motion. 12. Physics 1 - Ch01 Vector Math Foundations: vector operations, Vector2 implementation, Dot Product for player facing detection, C# demo. Ch02 Graphics Libraries: installing SFML, SFML basic structure, setting up Raylib, simple Raylib demo. 13. Physics 2 - Ch03 Collision and Physics Systems: Motion and Integration; Time Steps and Euler Integration; Fixed Timestep and Fixed Delta Time; Game Loop in C++ and C#; Visualizing with Raylib. 14. Physics 3 - Ch04 Forces, Restitution, Newton's Laws: Types of Forces; Applying Forces on a Physics Body; Restitution in C++ and C#; Visualizing Forces; Newton's Law. 15. Physics 4 - Ch05 Collision Detection & Resolution: Collider Shape Costs; Circle Collision; AABB Collision; Circle-AABB Collision (C++ and C#). Ch06 Rigidbodies & Velocity: Rotation and Rigidbodies; Linear and Angular Velocity; Engine Reality. 16. Git & GitHub 1 - Basics: Create GitHub Profile; Git Workflow; git commit; .gitignore; git revert. 17. Git & GitHub 2 - Branching and Merging: Branches; Branch Visualization; Fast-Forward Merge; 3-way Merge; Squash Merge; Merge Conflicts; Rebase. 18. Git & GitHub 3 - Remote and Tools: Remote Repository; Private Repository; Pull and Fetch; Clone and Fork; Git Graph; GitLens. 19. Summary "What I Benefited": one bullet per topic (SFML, Math, Physics, Git & GitHub) stating the main skill gained. 20. Closing: "Thank you", "Questions?", Micheal EL-Amir Fawzy Hakeem. CONSTRAINTS: Exactly 20 slides. Keep the presenter name exactly as written. Vary layouts slightly (list, two-column, icon row) while keeping one consistent visual system. I would cut the deck to 9 slides to meet your “less than 10” limit: Title SFML Math 1: Functions & Matrices Math 2: Transformations & Trigonometry Math 3: Quaternions & Vectors Physics 1: Vectors, Graphics Libraries & Game Loop Physics 2: Forces, Collisions & Rigidbodies Git & GitHub Summary: “What I Benefited” and closing (Thank you / Questions? / your name) With only 9 slides, the topics in each slide would be grouped into short bullets, so some of the detailed items from your 20-slide plan would be combined. Do you want me to build it this way, or would you rather connect Presenton and retry?
Presentation overview
This community presentation was shared by Micheal Hakeem as a complete 9-slide example. Create a 20-slide presentation titled "ITI Weekly Checkpoint 2: What I Learned". PRESENTER: Micheal EL-Amir Fawzy Hakeem AUDIENCE: ITI supervisors reviewing what I benefited fro… The preview lets you review the full sequence in order, rather than judging the design from a single cover image.
Use it as a reference for planning your own deck: notice how the amount of information changes from slide to slide, where visual emphasis appears, and how repeated design choices help the presentation feel connected. Community examples are inspiration, not locked templates, so you can keep the ideas that fit your audience and replace anything that does not.
Learn from the example
Look at the job each slide performs. Identify where the deck introduces its subject, develops the main points, adds evidence or examples, and moves toward a conclusion.
Notice which element attracts attention first and how headings, supporting text, images, and data are separated. Strong hierarchy makes the intended reading order obvious.
Compare spacing, typography, color, and repeated components across the slides. Consistent rules help varied content feel like one presentation instead of unrelated screens.
Make it your own
Begin with your audience and the decision, lesson, or action the presentation should support. Replace the topic, examples, evidence, and visuals with material you can verify, then edit every slide for one clear takeaway. You can borrow the visual direction without copying the creator's wording or message. Presenton will use this community deck as a design reference while you develop content for your own purpose.
