| Sep | OCT | Nov |
| 05 | ||
| 2019 | 2020 | 2021 |
COLLECTED BY
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.
Collection: Archive Team: The Github Hitrub
npm install hyperhtml-element
hyperHTML methods to itself,
with the only exception of the define method,
used in here to define Custom Elements instead.
To have same define functionality,
please use HyperHTMLElement.intent(...) which provides exact same API.
const HyperHTMLElement = require('hyperhtml-element'); class MyElement extends HyperHTMLElement { // observed attributes are automatically defined as accessors static get observedAttributes() { return ['key']; } // boolean attributes are automatically defined as accessors // and will set or remove the passed value static get booleanAttributes() { return ['active']; } // invoked once the component has been fully upgraded // suitable to perform any sort of setup // granted to be invoked right before either // connectedCallback or attributeChangedCallback created() { // triggers automatically attributeChangedCallback this.key = 'value'; } attributeChangedCallback(name, prev, curr) { // when invoked, attributes will be already reflected // through their accessor this.key === curr; // true, and curr === "value" this.getAttribute('key') === this.key; // always true this.render(); } render() { // lazily defined, this.html property points to an hyperHTML bound context // which could be the element shadowRoot or the element itself. // All events can be handled directly by the context, thanks to handleEvent // https://medium.com/@WebReflection/dom-handleevent-a-cross-platform-standard-since-year-2000-5bf17287fd38 return this.html` Hello <strong onclick=${this}>HyperHTMLElement</strong> ( ${this.state.clicks} )`; } // using the inherited handleEvent, // events can be easily defined as methods with `on` prefix. onclick(e) { // `this` refers to the current custom element console.log(this, 'click', e.target); // state handling, updates the view this.setState({clicks: this.state.clicks + 1}); } // alternatively, you can specify a `data-call` // attribute with the name of the method to invoke // this.html`<i data-call=onAnyEvent onclick=${this}>try</i>`; onAnyEvent(e) { // `this` still refers to the current custom element console.log(this, e.type, e.currentTarget, e.target); } // you can also use Preact-like events handling // this is less efficient, but migration friendly. // The method is bound once per instance so that // this.handleClick === this.handleClick is always true // this.html`<i onclick=${this.handleClick}>try</i>`; handleClick(e) { // `this` still refers to the current custom element console.log(this, e.type, e.currentTarget, e.target); } // define a default state to use whenever this.state is accessed // it can create states from observed properties too get defaultState() { return {clicks: 0, key: this.key}; } // this method is Preact friendly, once invoked // as this.setState({new: 'value'}); // it will shallow copy properties over // and it will invoke this.render() right after setState(objOrFn) // all other native Custom Elements method works as usual // connectedCallback() { ... } // adoptedCallback() { ... } } // classes must be defined through their public static method // this is the moment the class will be fully setup once // and registered to the customElements Registry. MyElement.define('my-element');
class MyLink extends HyperHTMLElement { created() { this.render(); } render() { return this.html`hello there!`; } } MyLink.define('my-link', {extends: 'a'});
HyperHTMLElement is compatible with every mobile browser and IE11 or greater.
There is a native live test page also transpiled for ES5 browsers.