A bootcamp portal is where applicants apply from a public page, admissions moves each application to a decision, students hand in weekly projects, and instructors grade each one with written feedback.
Pattern: RequestsDescribe it to Pory
“We run a 12-week coding bootcamp. People apply publicly, admissions reviews applications, and once in, students hand in weekly projects that instructors grade with feedback.”
Apply
Applications & weekly submissions
Twelve weeks in our Deep Ellum studio, Monday to Friday, 9:30 to 5. Pick full-stack web, data analytics or UX design.
Applications close on November 20. We reply within a week, and every interview is 30 minutes with an instructor.
A bootcamp runs two cycles at once: admissions for the next cohort, and weekly work for the current one. Pory handles both. Applicants apply on a public page, your team moves applications across a board, and enrolled students hand in each week's work for instructors to grade.
In plain English
Pory gives every student, instructor and admissions a sign-in of their own. Each student sees only their own submissions. It covers applications & weekly submissions. Submissions, grades, applications, schedule, materials, curriculum, students and foundry team live in Pory's own database, so there's no spreadsheet to keep in sync.
What it does
Applications came through a form tool, then got pasted into a tracker by whoever had time on Friday. In Pory an applicant picks a track, says what they do now and why they want in, and the application lands as Applied. Admissions stops copying rows between two tools that never quite agree.
With applicants spread across an inbox and a spreadsheet, nobody was sure who had been interviewed. In Pory admissions sees every application as a card under its stage and moves it along: Applied, Interview booked, Interviewed, then Accepted or Declined. The Monday stand-up stops being a roll call of who emailed whom.
Weekly projects arrived as Slack links, zip files and the odd Drive folder nobody had permission to open. In Pory a student files the week's project with the repo link, any files and a line on what they'd do differently, then sees whether it's been graded. Instructors stop hunting three apps for Week 3.
Feedback used to live in a DM that scrolled away before the student had read it properly. In Pory the instructor opens the submission and files a result (Exceeds, Meets or Not yet) with written feedback that stays on that project's record. When Week 5 builds on Week 4, the Week 4 feedback is still right there.
Every person signs in to their own view. This is what each role in the demo gets.
Sees only their own submissions.
Sees every submission in the portal.
Sees every submission in the portal.
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How Pory builds a portal
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
An application page, a notice board, an open directory: pages and forms anyone can use without signing in, on your domain.
Cards in columns. Drag a record to move it along.
A reviewer's score, a coach's feedback, a clinician's note, kept on the record it belongs to.
Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. Pory sets this up from your description, and you can adjust it in the editor.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colors, your logo. Members see you.
Describe who signs in and what each person needs, and Pory builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited students.
