| Nov | DEC | Jan |
| 08 | ||
| 2018 | 2019 | 2020 |
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.
To use ArchiveBot, drop by #archivebot on EFNet. To interact with ArchiveBot, you issue commands by typing it into the channel. Note you will need channel operator permissions in order to issue archiving jobs. The dashboard shows the sites being downloaded currently.
There is a dashboard running for the archivebot process at http://www.archivebot.com.
ArchiveBot's source code can be found at https://github.com/ArchiveTeam/ArchiveBot.

Markdown
Markdown lets you compose posts and comments with links, lists, and other styles using regular characters and punctuation marks. Markdown is used by writers and bloggers who want a quick and easy way to write rich text, without having to take their hands off the keyboard, and without learning a lot of complicated codes and shortcuts.
NOTE: This guide only applies to posts created with the Classic Editor. See the Jetpack Markdown Block support guide for more information on how to use the Markdown block. The Markdown block currently follows the CommonMark spec.
You can use Markdown on your Jetpack-powered blog for posts, pages and comments. This document will detail how to enable Markdown on your blog, and how to write with it.
If you are already familiar with Markdown, just enable it on your blog and start writing; refer to the WordPress.com Markdown Quick Reference page for help. Jetpack uses Markdown Extra, which adds some features not originally available in Markdown. For best results, please use the Text tab in the Editor as the Visual editor can give unexpected results. See below for more details.
Enabling Markdown
From the Jetpack page in your Dashboard, go to Settings → Writing and activate the “Write posts or pages in plain-test Markdown syntax” option in the Composing section.
Once it is activated, Markdown is enabled for posts and pages and available to all users on your blog.
To enable Markdown for comments, go to Settings → Discussion → Comments in your dashboard, and toggle the option labeled Enable Markdown use for comments. Click on Save Settings to apply. Visitors to your blog will now be able to compose comments using Markdown.
Writing with Markdown
Markdown makes use of special characters and punctuation marks to indicate styles and links. The specific characters you use and how you place them in the document is key to how your document will be formatted. When the document is published, Markdown converts these special characters to the appropriate formatting. For best results, use the Text tab in the Editor. The Visual Editor can produce unexpected results.
For example, in Markdown, to emphasize a word, you wrap it with an asterisk on both ends, like this: *emphasized*. When your writing is published, it will instead look like this: emphasized. Similarly, two asterisks denote strong text: **strong** will be published as strong.
To indicate links, use regular and square parentheses. Wrap the text you want to link in square parentheses, and immediately after it, insert the link target, wrapped in regular parentheses. The actual Markdown could look like this: [Jetpack.com](https://jetpack.com/). When published, it will be a standard link: Jetpack.com.
The original Markdown text you write will always remain in Markdown, this way you can go back and edit it using Markdown. Only the published document – the post or the page – will be converted. If you write a post in Markdown, it will be published as a fully formatted post on your blog, but when you go back and edit, it’ll still be in Markdown.
The best way to get started with Markdown is to experiment. Open the Markdown Quick Reference guide, start a draft post on your blog, and try to use the different features.
Markdown Extra and Markdown in Jetpack
Jetpack uses Markdown Extra by Michel Fortin. It includes some features not originally available in Markdown, including improved support for inline HTML, code blocks, tables, and more. Code blocks can use three or more back ticks (
```), as well as tildes (~~~).See the WordPress.com Markdown Quick Reference page for the most useful formatting and features offered by Markdown Extra. For more detailed information, see the original reference guide for Markdown, and the Markdown Extra page.
However, the Markdown block currently follows the CommonMark spec. For more information you can refer to the official CommonMark spec.
About Markdown
Markdown was created by John Gruber and Aaron Swartz in 2004 as a solution for easily composing richly formatted text on the web. It employs plain text only and is based on conventions established in the computer and technology industry for writing emails and other documents with limited resources.
In plain text documents, the text you see on the screen represents all the information in the file, with essentially no formatting or other data hidden from view. Plain text documents have been used for decades for their simplicity, portability, and reliability. You can probably still open and edit any plain text document from the past 40 years in any computing device available today.
Markdown has seen popular adoption on the web since it was first introduced, and it is now included in many sites and software programs.
Add Markdown support to your Custom Post Types
There are 2 options to add Markdown support to a specific Custom Post Type on your site:
add_post_type_support()function. To do so, add the following code to a functionality plugin:You’ll need to replace “product” by your Custom Post Type name.
Add Markdown support to your Custom Fields
You can follow these instructions to add Markdown support to custom meta fields.
Privacy Information
This feature is deactivated by default. If you ever need to deactivate this feature, you can toggle the Write posts or pages in plain-text Markdown syntax setting in the Composing section from Jetpack — Settings — Writing in your dashboard.
For activity tracking (detailed below): IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID and URL, Jetpack version, user agent, visiting URL, referring URL, timestamp of event, browser language, country code.
None.
We track when, and by which user, the feature is activated and deactivated.
None.
We sync a single option that identifies whether or not the feature is activated.
None.
Related