Help for Administrators

As an administrator for your Coders' Club, you are responsible for managing the membership of the club -- coders as well as coaches -- and the application also provides some support for carrying out other administrative tasks although most of these can be done "manually" too, with spreadsheets and word processors and e-mail.


The first big step for any club is promotion. There are lots of ways to get the word out: school newsletters, posters in the school, "take-home folders" with some help from homeroom teachers, etc.

first email newsletter blurb flyer welcome/orientation

Creating Your Club

Let's start this story at the beginning: there's a new Coders' Club, you are the administrator, or one of the administrators, and you currently have no coders or coaches registered: clean slate, and we'll assume that you've already promoted the idea locally and that there are some kids and parents intereste din participating. Here are the steps you'll usually take:

  1. Go to the main administration page: log into the application, and from the main coaches page click the link labeled Manage club membership. You'll see some buttons in a column on the left. The first few are useful for sorting and filtering the list of coders, but you don't have any coders yet. So we'll mostly use the lower set of buttons, which take you to other pages where you can build up the club.
  2. Register coder(s) takes you to a page where you can enter the first and last names, and parent e-mail addresses, of one or more coders to be members of the club. The parser is reasonably graceful, and for example if you have a spreadsheet with these three values in rows and three columns, you should be able to copy a grid of values from that sheet and paste it here. If a student has a first or last name with spaces in it, then add commas to separate out the names and email; otherwise whitespace usually works.
  3. Assign coders to groups is useful for two things. One, you can establish who attends which session, if you have enough members to meet at different times of the week. Even if your group all meets toegher, you should do this part, to create a "Main" group. Over time this will help to distinguish between active coders and those who maybe don't sign up the next time around but are still in the system. Groups are created simply by naming them and assigning coders (just first and last names in the main text area this time).
  4. On the main admin page you will now see your registered coders, color-coded by group or with white backgrounds if not assigned to a group. You can filter to only active coders, sort by group or not, show parent contacts or not.
  5. View coaches will show you the current coaches for your club. You can assign administrator privileges to coaches here, or revoke them. You can remove coaches -- but you can't remove yourself.
  6. From this page you can Register coach(es) which works a lot like registering coders -- except that when registered each coach has a generated password assigned to them, and you must copy these passwords off of the confirmation screen and transmit them to the coach(es) so that they can log in. Then they can change their passwords as they like.
  7. View attendance is more useful once you've started meeting. It can be helpful in getting a general sense of attendance rate, or in identifying coders who registered but aren't attending -- miscommunication somewhere, or change of situation? -- so that you can follow up.


Finally, the application will produce print-ready certificates for one or more coders. Click the link at the top of the progress-tracking page for an invididual coder or, often more useful, click the link next to the name of each group in the coach's home page, and get a document with a page for each coder in that group. There's a place for a coach to sign each certificate, and you might hand them out at the end of the season. We sometimes do colored pencils for each belt earned, as well.