Difference between revisions of "New Authors landing page"
m (Gjennings moved page Category:Authors to New Authors landing page: (Main) seems to be the default? Don't want to create new "category")
Revision as of 14:09, 15 June 2021
Most people write problems starting from templates. Problems from the OPL can be modified to suit individual needs, or existing problem templates can be used to create new problems.
- Problem Techniques This page lists templates for WeBWorK problems in alphabetical order. This collection of templates can also be accessed through the associated category page: Category:Problem Techniques
- Subject Area Templates Some may find it useful to use this page where templates are ordered by subject area.
- Sample_Problems A third page with a collection of templates is this page of sample problems.
WeBWorK problems should be written with the use of MathObjects. Most of the templates mentioned above will include the MathObject Macros (recognizable by the line "MathObjects.pl" in the LoadMacros section of the code). For those who would like to read up on the basics of coding problems the following pages are recommended:
- Problem Authoring Background Information -- includes a PG language overview, some comments about editing problems and ensuring server access.
- MathObjects -- information on authoring problems using MathObjects.
- MathObjects reference table -- a quick reference.
- Introduction to Contexts -- how to use Numeric, Complex, Vector, Matrix, Interval, and other contexts in problems.
- Reduction rules for MathObject Formulas -- a table of The Reduction Rules and their Actions.
- Davide Cervone's presentation on MathObjects to PREP, June, 2014
- PGML -- information on authoring problem using the PGML markup language.
- Template 4 -- the standard outline of a problem using PGML, which includes a tagging and description section, an initialization section, a problem set-up section, a text section, and optional answer and solution sections.
- Davide Cervone's presentation on PGML to PREP, June, 2014
- PG-Labs -- try out code fragments on line including code fragments containing MathObjects and PGML. This is a quick way to learn the fine points of the MathObject and PGML syntax.
Templates, programming examples, and problem libraries from the University of Lethbridge
Sean Fitzpatrick (firstname.lastname@example.org) contributed the following:
This summer, one of my colleagues hired a student to help her go through all of the libraries, marcos, contexts, etc. and put together a collection of templates and programming examples. I got permission from her to put everything on a public GitHub repository; you can find the fruits of their efforts here:
The programming examples are not questions. They're an attempt at producing an exhaustive list of every possible way of inputting and evaluating something using the various contexts. In the documentation there's a nice flowchart for deciding which context to use for a given problem.
I hope this is useful. It's the beginnings of what will hopefully be a longer project (done mostly over summers), so it's not yet as polished as it could be.
Reference documents and manuals
- Problem Authoring Videos, recordings from the PREP 2015 Problem Authoring Workshop.
- Applets, how to embed Flash and Java applets into WeBWorK questions.
- SequentialProblems now replaced by Scaffold revealing the problem one step at a time
- POD -- POD (for WeBWorK/PG 2.15) = "plain old documentation" -- original documentation embedded in the code files -- this is the place to find the most complete and most technical description of macro behaviors.
- WeBWorK Problem Authoring Tutorial aimed at people who already know TeX, but need to learn about Perl, PG, and MathObjects (pdf file).
- Customize Course This page includes a bit of code that allows student to obtain a new version of a problem.
- Notes on training authors, and suggestions for further documentation-- Sam Hathaway
- The Good Questions project at Cornell University 
- Converting CAPA problems for use with WeBWorK (This article has been retained as a historical document.)