Skip to content
Tomer Naydnov
arc / explorer

Read-only portfolio demo · Fictional data

Original app recordings
Explore administration / Connected tools

Run the learning platform

Specialist tools, connected to learning context.

Programming, gaming and API access have their own explicit integration boundaries.

31 / 33

Browser Coder

>_

Run and inspect programming work while Arc retains the lesson and assignment context.

Explore Browser Coder ↗

Arc Gaming

◇

Selected games connect to class assignments, roster provisioning and a scoped launch.

Source-supported integration. No external game is launched here.

Developer access

{ }

API documentation and permission-scoped tokens support external integration workflows.

Connection settings
Owned by the platform administrator
Assignment
Classroom, selected task and timing are part of the launch context
In this explorer
No credentials, external service calls or writable connection fields
What this part of Arc does
  • Browser Coder learning-platform integration
  • Arc Gaming connection settings, assignments and directory access
  • OpenAPI reference and scoped API tokens
  • No external runtime, credentials or service calls are used by this explorer

This is a browsable portfolio interpretation of Arc’s workflows with fictional examples. Navigation, filtering and theme previews work here; editing, execution and platform services belong to the original application.

Inside the original application.

This demo view is grounded in Arc’s source. Explore the recorded workflows for a look at the original interface.

All original recordings ↗
Source references & review notes
  • app/Platform/Portals/Admin/Controllers/AdminArcGamingSettingsController.php
  • app/Platform/Domain/ArcGaming/ArcGameLaunchService.php
  • routes/api.php
Read the portal research & evidence boundaries ↗

Source reviewed at development revision 5549bf96. Original captures have their own pinned revisions; the live platform has a separate release.