-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* updated CTA button * updated email link * Update src/pages/sigcse2024/submit-questions.mdx Co-authored-by: Firas Moosvi <[email protected]> * Update src/pages/sigcse2024/index.tsx Co-authored-by: Nathan Sarang-Walters <[email protected]> * Update src/pages/sigcse2024/submit-questions.mdx Co-authored-by: Nathan Sarang-Walters <[email protected]> * Update src/pages/sigcse2024/submit-questions.mdx Co-authored-by: Nathan Sarang-Walters <[email protected]> * small updates sigcse event page --------- Co-authored-by: Firas Moosvi <[email protected]> Co-authored-by: Nathan Sarang-Walters <[email protected]>
- Loading branch information
1 parent
b7cc798
commit 8f5bdec
Showing
2 changed files
with
66 additions
and
12 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,7 @@ | ||
import React from "react"; | ||
import classnames from "classnames"; | ||
import Head from "next/head"; | ||
|
||
import Link from "next/link"; | ||
import { PageBanner } from "../../components/Banner"; | ||
import { Heading } from "../../components/Heading"; | ||
import Stack from "../../components/Stack"; | ||
|
@@ -10,7 +10,7 @@ export default function SIGCSE2024() { | |
return ( | ||
<React.Fragment> | ||
<Head> | ||
<title>SIGCSE 2024</title> | ||
<title>SIGCSE 2024 Spiffy PrairieLearn Questions</title> | ||
</Head> | ||
|
||
<PageBanner | ||
|
@@ -22,7 +22,7 @@ export default function SIGCSE2024() { | |
<div className="container-md pt-2"> | ||
<Stack spacing={4}> | ||
<Heading> | ||
Affiliated Event: Spiffy Assessments with PrairieLearn | ||
Affiliated Event: Spiffy Questions with PrairieLearn | ||
</Heading> | ||
|
||
<p> | ||
|
@@ -31,8 +31,7 @@ export default function SIGCSE2024() { | |
to practice with rapid feedback, a feature provided by | ||
autograders. PrairieLearn is an open-source assessment authoring | ||
system that empowers the development of exceptionally rich | ||
interactive STAR questions — Skill-specific, Tagged to | ||
course competencies, Auto-graded, and Randomizable. | ||
interactive questions. | ||
</p> | ||
<p> | ||
Questions are formulated as problem generators capable of | ||
|
@@ -46,14 +45,28 @@ export default function SIGCSE2024() { | |
</p> | ||
<p> | ||
Currently, PrairieLearn is actively adopted in over 800 courses | ||
across 20 universities. In this affiliated event, instructors from | ||
these courses will showcase the innovative online assessments | ||
they’ve created using PrairieLearn, and they are eager to share | ||
these resources with the broader instructor community. Presenters | ||
will also be happy to discuss their experience authoring these | ||
assessments. | ||
across 20 universities.{" "} | ||
<strong> | ||
In this affiliated event, instructors from these courses will | ||
showcase the innovative online assessments they’ve created using | ||
PrairieLearn, and they are eager to share these resources with | ||
the broader instructor community. | ||
</strong>{" "} | ||
Presenters will also be happy to discuss their experience | ||
authoring these assessments. | ||
</p> | ||
|
||
<div className={classnames("container-fluid py-2")}> | ||
<div className="d-flex flex-row justify-content-center flex-wrap"> | ||
<Link | ||
href="/sigcse2024/submit-questions" | ||
className="btn btn-warning btn-lg me-3 mt-3" | ||
> | ||
SUBMIT YOUR SPIFFY QUESTIONS TO THIS EVENT | ||
</Link> | ||
</div> | ||
</div> | ||
|
||
<h4>Organizers</h4> | ||
<ul> | ||
<li> | ||
|
@@ -63,6 +76,20 @@ export default function SIGCSE2024() { | |
https://mfsilva.web.illinois.edu/ | ||
</a> | ||
</li> | ||
<li> | ||
Prof. Craig Zilles, University of Illinois Urbana-Champaign,{" "} | ||
<a href="mailto:[email protected]">[email protected]</a>,{" "} | ||
<a href="https://mfsilva.web.illinois.edu/"> | ||
https://zilles.cs.illinois.edu | ||
</a> | ||
</li> | ||
<li> | ||
Prof. Armando Fox, UC Berkeley,{" "} | ||
<a href="mailto:[email protected]">[email protected]</a>,{" "} | ||
<a href="https://www2.eecs.berkeley.edu/Faculty/Homepages/fox.html"> | ||
www.cs.berkeley.edu/~fox | ||
</a> | ||
</li> | ||
<li> | ||
Prof. Firas Moosvi, University of British Columbia,{" "} | ||
<a href="mailto:[email protected]">[email protected]</a> ,{" "} | ||
|
@@ -117,7 +144,7 @@ export default function SIGCSE2024() { | |
|
||
<h4>Time and Location</h4> | ||
|
||
<p>TBA</p> | ||
<p>Friday, March 22, 12:00 pm to 13:30 pm, Rooms D137-138</p> | ||
</Stack> | ||
</div> | ||
</div> | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
import { MarkdownLayout } from "../../components/MarkdownLayout"; | ||
|
||
export const meta = { | ||
title: "Submit your PrairieLearn question", | ||
backText: "Back to sigcse affiliated event page", | ||
backHref: "/sigcse2024", | ||
}; | ||
|
||
## How does this work? | ||
|
||
One of the best things about PrairieLearn is how flexible and customizable it is. Over the past few years, we have seen tremendously creative and original question types! A group of PrairieLearn users are organizing an event at SIGCSE 2024 Technical Symposium in Portland OR, to showcase the kinds of cool questions one can build with PrairieLearn. It will be Friday, March 22nd from noon-1:30pm in Meeting Rooms D137-138. | ||
|
||
We’re looking for examples of engaging and interactive PrairieLearn questions (or assessments) that go beyond what you can do “out of the box” in some novel or creative way. Perhaps your questions assess an interesting topic in a novel way, or provide interactive assessments that are custom built, or use a new element type that can be used as a building block for other questions. We want to see them all! | ||
|
||
If you or your colleagues/students have developed PrairieLearn question(s) that might fit this description, we’d love to have you submit them for possible inclusion in our showcase. | ||
|
||
During the event itself, we will ask the authors/submitters of selected questions to give quick 3-5 minute "lightning talk" demos of their question, as time permits. But even if you or your delegate/student/representative cannot attend SIGCSE in person, we have other ways we’d be able to showcase your question(s). We will also make available to event participants a PrairieLearn "demo course" that includes all the questions accepted for the event, including the ones we don’t have time to present (the event itself is 90 minutes, and we’ll need 10-15 minutes of framing time). | ||
|
||
## What do you need to do? | ||
|
||
Complete this [Google Form](https://docs.google.com/forms/d/e/1FAIpQLScR6kmdgCAgcfax0j0RCUrFR46WTpy5hrhd5ZFghQcROz0Yng/viewform?usp=sf_link) if you’re interested in submitting a question for this showcase. Note that if your question is accepted as part of the event, it will be made available in a demo course that, for all practical purposes, will be public, with a [CC-BY-NC license](https://creativecommons.org/licenses/by-nc-sa/4.0/). So if you have "secret" questions you use on exams that you don’t want circulated, please don’t submit those (though we are planning to have time at the event where you can privately show such questions to other participants and make them selectively available to other instructors). | ||
|
||
Reach out to either Armando Fox ([[email protected]](mailto:[email protected])) or Firas Moosvi ([[email protected]](mailto:[email protected])) if you have any questions! | ||
|
||
export default ({ children }) => ( | ||
<MarkdownLayout meta={meta}>{children}</MarkdownLayout> | ||
); |