
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
While reviewing tutorials for #262, I found a lot of them use the REPL at the start. A typical example:
Some of them use multiline expressions:
I think new learners find those are easier to approach than full scripts, but they don't fit with the live coding approach. A hybrid approach would be to add a REPL mode that lets the user type new lines at the end of each code sample. Ideally, the up arrow would even let them cycle through the lines in the sample.
The
codemodule has tools to emulate a REPL, including help deciding when an expression is complete and when you should ask for another line.It might be possible to fit this into the live tutorial model using cloze tests. The goal could be a REPL session with blanks, and the student has to follow the pattern and fill in the blanks. For example, a goal might look like this:
The student would need to replace the
?with*. I guess a rewind button would be needed to fix mistakes.To define a REPL section, end the code with
>>>. The goal can contain lines that start with^^^to mark clozes.The text was updated successfully, but these errors were encountered: