Skip to content

Conversation

@perktime
Copy link
Contributor

This pull request updates documentation and environment configuration to consistently use "Microsoft Foundry" instead of "Azure AI Foundry" across all student and coach materials. It also introduces a new development container configuration for improved setup consistency. The most important changes are grouped below:

Dev Environment Setup

  • Added a new .devcontainer.json file to define a standardized development container with pre-installed Azure CLI, Node.js, Python, and recommended VS Code extensions for a smoother onboarding experience.

Documentation Updates: Foundry Naming and Instructions

  • Refactored all references from "Azure AI Foundry" to "Microsoft Foundry" in student and coach guides, including setup steps, resource deployment instructions, and troubleshooting sections, ensuring consistent terminology throughout the hackathon materials. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14]

Student Guide Enhancements

  • Updated step-by-step instructions for resource creation and configuration to reflect the new Microsoft Foundry workflow, including automated and manual deployment processes, resource naming conventions, and credential retrieval. [1] [2] [3]

Resource Credential and Environment File Clarifications

  • Clarified instructions for populating the .env file, specifying where to find credentials in the Microsoft Foundry and Azure Portal, and updated language to avoid confusion regarding file renaming and resource verification. [1] [2] [3]

Troubleshooting and Known Bugs

  • Updated troubleshooting steps to reference Microsoft Foundry for model deployment adjustments and kernel restarts in VS Code, providing clearer guidance for common issues encountered during the hackathon. [1] [2]

Let me know if you'd like a walkthrough of any specific section or further details on the new dev container setup!

perktime and others added 30 commits September 19, 2025 11:00
- Add generic .devcontainer/devcontainer.json at repo root
- Updated Challenge-00-lab.md with working Dev Containers button
- Root devcontainer uses universal image for broad compatibility
- Allows users to start with generic container, then reopen specific folders in their specialized containers
- Updated URL to include ref=TestCodespaceButton parameter
- Ensures testing uses the branch with the root devcontainer
- Users can now test the full dev container workflow
…ve elements

✨ Key Enhancements:
- 🎨 Changed Jekyll theme from midnight to modern cayman theme
- 💅 Comprehensive custom CSS with modern styling and animations
- 📊 Interactive elements: progress bars, alerts, status badges
- 📁 Collapsible sections for better content organization
- 📈 Mermaid diagram support for visual workflows
- 🌙 Dark mode support and responsive design
- 📱 Mobile-optimized experience
- ♿ Improved accessibility features

🚀 Challenge-00 Improvements:
- Added technology badges and progress indicators
- Enhanced navigation with visual hierarchy
- Interactive validation checklists
- Collapsible help sections
- Modern card-based layout

📝 Template Creation:
- Created enhanced challenge template for consistency
- Includes all new visual elements and best practices
- Created demonstration page showing all enhanced visual elements
- Includes examples of alerts, badges, progress bars, cards, buttons
- Shows Mermaid diagrams, collapsible sections, and enhanced tables
- Provides reference for content creators using the new styling
- Documents the complete visual enhancement system
✨ Theme Changes:
- 🎨 Switched from dark Cayman to bright, clean Minima theme
- 🌈 Redesigned entire color palette with bright, friendly colors
- ☀️ Light background with colorful gradients throughout
- 🎯 Maintained all interactive elements with brighter styling

🎨 Visual Improvements:
- 💙 Bright blue primary colors instead of dark themes
- 🌸 Colorful gradients in alerts, cards, and buttons
- 🌅 Light backgrounds with subtle gradients
- 🔆 Enhanced contrast for better readability
- 🎨 Colorful progress bars with rainbow gradients
- ✨ Bright, cheerful badge designs

🎯 Enhanced Elements:
- 📊 Redesigned all components for brightness
- 🎪 More colorful and engaging visual elements
- 📱 Maintained mobile responsiveness
- ♿ Kept accessibility features with better contrast
…re AD token provider, enhance error handling, and improve environment setup. Add Bicep module for Foundry project deployment with role assignments and diagnostic settings.
…s; clarify resource creation process and troubleshooting steps for students.
…e challenge documents for consistency and clarity.
…can be used prior to getting the PR approved in the main repo
Removed temporary steps for accessing the Content Safety service as they are no longer necessary because they are done in the deployment script.
Removed setup instructions for deploying the model. gpt-4o-mini is already deployed through the deployment script.
Removed reference to 'Hub' in project verification steps.
Changed Codespace link
@perktime perktime requested a review from a team as a code owner January 21, 2026 15:06
…es and environment setup. Add easy.txt for quick fixes.
@jrzyshr jrzyshr changed the title [Hack Update] AI fundamentals 0126 [Hack Update] 066-AI fundamentals 0126 Jan 21, 2026
…streamline HTML elements and remove unnecessary includes.
…resources and update API versions

- Updated `deploy.sh` to derive deployment name from template filename and corrected environment variable for project endpoint.
- Removed parameters and modules related to Application Insights and Container Registry from `main.bicep`.
- Updated AI Services resource to use the latest API version and added project management properties.
- Deleted unused modules for Application Insights, Container Registry, Foundry Project, and Hub.
- Added new notebook for building a Research Assistant Agent using the Microsoft Agent Framework.
@jrzyshr jrzyshr self-assigned this Jan 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants