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.
This collection is a set of Github repository archives from two major sets: A panic grab upon the acquisition by Microsoft, and a larger, ongoing set of Pretty Much Everything.
TIMESTAMPS
The Wayback Machine - https://web.archive.org/web/20200917024214/https://github.com/L13/vscode-css-snippets
The idea of those snippets is to create a property instantly based on some simple rules without selecting it by menu or auto completion. Write one to six characters and you get the property and the value.
Only a few prefixes are twice, because the rules are matching different properties like fs1 -> flex-shrink: 1; and font-size: 0;. Then you have to pick the right one.
The following prefixes are just examples to explain the rules. To see the complete list, please visit SNIPPETS.md. If a property or pattern might be missing, please open an issue on Github and make a suggestion.
Shortcut rules for CSS snippets
1. The first letter in a word or after a minus "-" defines the prefix.
Prefix
Snippet
di
display: inline;
dib
display: inline-block;
wa
width: auto;
2. Numbers are defined by the amount of numbers.
Prefix
Snippet
p1
padding: 0;
p2
padding: 0 0;
p3
padding: 0 0 0;
p4
padding: 0 0 0 0;
w1
width: 0;
zi1
z-index: 0;
3. Colors are defined with an underscore "_".
Prefix
Snippet
c_
color: #000000;
b_
background: #000000;
bs1_
border: solid 0#000000;
4. The order of a value list is [function call] [keyword] [numbers] [color].
Prefix
Snippet
bunr2_
background: url() no-repeat 00#000000;
5. Property prefixes are starting with a minus "-".
8. A number after the dollar sign "$" defines the amount of parameters.
Prefix
Snippet
r$3
rgb(0, 0, 0);
r$4
rgba(0, 0, 0, 1);
Shortcut rules for SCSS snippets
1. All CSS snippets are available in SCSS, too.
2. Rules are starting with an "@" symbol.
Prefix
Snippet
@c
@content;
3. An underscore "_" after a prefix defines a brace scope.
Prefix
Snippet
@i_
@if CONDITION { ... }
4. A dollar sign "$" defines also a mixin call.
Prefix
Snippet
@i$
@include NAME ();
@i$_
@include NAME (){ ... };
5. The number "1" defines a one liner.
Prefix
Snippet
@e1
@extend NAME;
Recommended Settings
It is recommended to exclude emmet support for CSS and SCSS in the settings.
"emmet.excludeLanguages": [
"css",
"scss"
],
And it is recommended to set the snippet suggestions to top.
"editor.snippetSuggestions": "top",
Recommended Keyboard Shortcuts
Please have the following keyboard shortcuts always in mind, because these are fundamental to get the most out of it. Every tab stop is used only if necessary, because it prevents VS Code to open the IntelliSense menu automatically. So sometimes DownArrow or Cmd/Ctrl + Enter can have the same effect.
macOS
Tab - Jump to the next tab stop of the snippet.
DownArrow - Move the caret down one line.
Cmd + Enter - Insert line below, even if the caret is in the middle of a line.
Cmd + Shift + Enter - Insert line above, even if the caret is in the middle of a line.
Windows / Linux
Tab - Jump to the next tab stop of the snippet.
DownArrow - Move the caret down one line.
Ctrl + Enter - Insert line below, even if the caret is in the middle of a line.
Ctrl + Shift + Enter - Insert line above, even if the caret is in the middle of a line.