GitBook: [2.0.0] 29 pages modified

README.md

@@ -1,26 +1,30 @@
-# FAQ
+# About Us
 
-## What is JOLT _Digest_?
+## What is JOLT Digest?
 
-The [_JOLT Digest_](http://jolt.law.harvard.edu/digest) is the online companion to the Harvard Journal of Law & Technology \([JOLT](http://jolt.law.harvard.edu/)\). It is intended to serve as a one-stop source of legal news to professors, practitioners, law students, and the general public on issues at the intersection of law and technology.
+[JOLT Digest](http://jolt.law.harvard.edu/digest) is the online companion to the Harvard Journal of Law & Technology \([JOLT](http://jolt.law.harvard.edu/)\). It is intended to serve as a one-stop source of legal news to professors, practitioners, law students, and the general public on issues at the intersection of law and technology.
 
-The Digest features short articles on new, precedential, or interesting cases; new legislation; administrative developments of note; and other interesting happenings. By applying JOLT’s traditionally high editing standards to the Digest, we create a uniquely useful and trustworthy resource.
+Digest features short articles on new, precedential, or interesting cases; new legislation; administrative developments of note; and other interesting happenings. By applying JOLT’s traditionally high editing standards to the Digest, we create a uniquely useful and trustworthy resource.
 
-## Do you conform with the Oxford Comma?
+## Meet the team!
 
-Yes. Read more [here](reports/reportstylecitation/#commas).
+**Digest Executive Editor** \(Mindy Nam\) supervises the entire Digest team, which is comprised of the Digest Reports program, the Federal Circuit Panel program, the Digest Notes and Comments, and the JOLT Digest Podcast. She also creates the Digest publication schedule, and provides an additional layer of editing for all publications.
 
-## Meet the editing team!
+**Digest Engagement Editor** \(Alicia Loh\) oversees all Digest Reports: assisting the SMCs to generate topics and schedule assignments, coordinating the assignment process, and providing a final layer of editing.
 
-**Contributors** write the Report articles for _JOLT Digest_ and also suggest sources of online commentary that can be linked from Digest articles.
+**Subject Matter Coordinators \(SMCs\)** \(Sam Santopaolo, Justin Fishman, and Andrew Distell\) assign topics to and work closely with Contributors and Report Editors on their subject matter teams to publish Digest Reports. 
 
-**Report Editors** supervise the Contributors. Report Editors are responsible for editing article drafts and adding additional relevant materials.
+**Report Contributors** and **Editors** work together to publish Digest Reports that provide overviews on important new developments in law and technology. 
 
-**Subject Matter Coordinators** \(Mindy Nam and Stella Mao\) assign topics to Contributors and Report Editors on their subject matter teams. Assignments include the topic and links to sources that help Contributors to understand the issue and links to relevant online commentary.
+**Digest Content Editors** \(Or-el Vaknin and Anita Liu\) take the lead on seeing Digest Student Notes and Comments from submission to publication. This involves back-and-forth on substantive edits with the authors to make sure their pieces meet Digest standards. 
 
-**Digest Content Editors** \(Brian Kulp and Phillip Takhar\) take the lead on seeing Digest Student Notes and Comments from submission to publication. This involves back-and-forth on substantive edits with the authors to make sure their pieces meet Digest standards.
+**Federal Circuit Panel Writers** \(Hye Yoon Hwang, Meera Midha, Kaye Horstman, and Will Czaplyski\) write Notes on current issues in the Federal Circuit. 
 
-**Digest Submissions Editor** \(Wendy Chu\) oversees and assists the Coordinators to generate topics and schedule assignments, coordinates the assignment process, provides a final layer of editing for entries, upload posts into WordPress, and ensure that the entries remain up-to-date as new developments occur.
+**Podcast Content Team** \(Flora Wang, Minnie Che, Nick Berk, and Coco Zhang\) leads the creation of podcast episodes and researches the subject material. 
 
-**Digest Executive Editor** \(Peter Zhu\) supervises the Digest Content Editor and other Digest team members, creates the Digest publication schedule, and provides an additional layer of editing for entries.
+**Podcast Production Team** \(Nick Curry and Bowen Wang\) manage recording logistics and finalize the production of each episode. 
+
+\*\*\*\*
+
+\*\*\*\*
 

SUMMARY.md

@@ -1,24 +1,13 @@
 # Table of contents
 
-* [FAQ](README.md)
+* [About Us](README.md)
+* [FAQ](about-us.md)
 
 ## Reports
 
 * [Contributor's Guide](reports/reportcontributorguide.md)
 * [Editor's Guide](reports/reporteditorguide.md)
-* [Style & Citations Guide](reports/reportstylecitation/README.md)
-  * [Requirements](reports/reportstylecitation/requirements.md)
-  * [Style](reports/reportstylecitation/style.md)
-  * [Commas](reports/reportstylecitation/commas.md)
-  * [Symbols](reports/reportstylecitation/symbols.md)
-  * [Quotations](reports/reportstylecitation/quotations.md)
-  * [Citations](reports/reportstylecitation/citations.md)
-  * [Substance](reports/reportstylecitation/substance.md)
-
-## Flash Digest
-
-* [Contributor's Guide](flash-digest/flashdigestcontributorguide.md)
-* [Editor's Guide](flash-digest/flashdigesteditorguide.md)
+* [Style & Citations Guide](reports/reportstylecitation.md)
 
 ## Notes
 

about-us.md

@@ -0,0 +1,26 @@
+# FAQ
+
+## How can I get involved with Digest? 
+
+**Harvard Law Students** can write Reports, Notes, or Commentary. Sign up to write or edit a Report at the beginning of each semester. Join the [JOLT mailing list](https://test.us9.list-manage.com/subscribe?u=fd5e177723c7929c4cc46bab1&id=dacf20620a) to know when to sign up. 
+
+**Other Law Students and Recent Graduates** can write Notes or Comments. 
+
+**Academics, Practitioners, and Other Professionals** can write Comments. 
+
+We accept submissions for Notes and Comments all year round. Please fill out [this form](https://forms.gle/mC9Tw2sRYxHjA2JV9), and we will contact you. 
+
+If you have any questions, please email [email protected].
+
+## What is the difference between Reports, Notes, and Comments? 
+
+**Reports** are short objective overviews, 500–700 words in length, of recent court opinions or pieces of legislation.
+
+**Notes** provide a novel analysis on an issue related to law and technology. These are formal pieces that include Bluebooked citations and published in PDF format. They are comparable to JOLT's print publication student notes but shorter in length \(1,500–2,000 words for a Digest note, 4,000–6,000 words for a print note\). 
+
+**Comments** are about 2,000 words and can come in several general forms: opinion pieces, primers, or responses. They allow the author to participate in ongoing discussions about cutting-edge legal issues without the formality of our Notes or the impartiality of our Reports.
+
+## Do you conform with the Oxford Comma?
+
+Yes. Read more [here](reports/reportstylecitation.md#commas).
+

comments/commentcontributorguide.md

@@ -6,7 +6,7 @@ The JOLT _Digest_ Commentary section is a new platform for professionals, academ
 
 _Digest_ Comments are about 2,000 words and can come in several general forms: opinion pieces, primers, or responses. This guide will provide an overview of your responsibilities as the author of a _Digest_ Comment.
 
-## Writing Process in a Nutshell {#nutshell}
+## Writing Process in a Nutshell <a id="nutshell"></a>
 
 The Commentary writing process can be broken down into the following steps.
 
@@ -15,7 +15,7 @@ The Commentary writing process can be broken down into the following steps.
 * [Step 3](commentcontributorguide.md#step3): Digest Masthead Edits
 * [Step 4](commentcontributorguide.md#step4): Finalizing the Comment
 
-## Step 1: Getting Started {#step1}
+## Step 1: Getting Started <a id="step1"></a>
 
 You, the Comment author, are hoping to publish a Comment with JOLT _Digest_. Your first task is to come up with a topic. Because Comments should be timely and related to law and technology, you can run your topic by the Digest Executive Editor. However, you can also submit a draft without asking us beforehand.
 
@@ -43,19 +43,19 @@ A primer can also address several issues related to the topic. For example, you
 
 Response pieces must reply to a JOLT publication. We strongly favor responses to articles published in our print edition. Authors should clearly identify the contested article, acknowledge where they agree with the JOLT publication and where they disagree. JOLT _Digest_ will inform the author of the contested article that a response is being drafted so that he or she has the option to draft a rebuttal.
 
-## Step 2: Drafting the Comment {#step2}
+## Step 2: Drafting the Comment <a id="step2"></a>
 
 If seeking our approval for your topic, you must send us a draft within two \(2\) weeks of receiving our confirmation. The Comment must be consistent with the [Digest Commentary Style Guide](commentstylecitation/).
 
 The final Comment should be around 2,000 words in length. Because Digest’s readership varies in terms of familiarity, you should assume the reader knows very little about the chosen subject. Comments should thus include a brief introduction to the problem, explain why the topic is important, and provide links to foundational knowledge.
 
 You may include a short biography at the end of the Comment, as well as links to your social media accounts.
 
-## Step 3: Digest Masthead Edits {#step3}
+## Step 3: Digest Masthead Edits <a id="step3"></a>
 
 Please send your completed draft to the Digest Executive Editor \(currently Filippo Raso\). The Digest Executive Editor will review the Comment for factual accuracy, compliance with the style guide, and organization. The Digest Executive Editor will only reject claims that are patently untrue, though he may request additional sources to establish the validity of a claim.
 
-## Step 4: Finalizing the Comment {#step4}
+## Step 4: Finalizing the Comment <a id="step4"></a>
 
 The Digest Executive Editor will return the Comment to you for your final review. Please address his comments. With your approval, he will post the final article on the Digest Commentary page.
 

comments/commentstylecitation/README.md

@@ -4,11 +4,11 @@
 
 Authors should review the Style and Citation Guide before they begin drafting their Comment.
 
-## Requirements {#requirements}
+## Requirements <a id="requirements"></a>
 
 All Comments should hyperlink to the original source material, preferably a PDF \(e.g., court opinion or filing, legislation. Points should generally be well supported and should link to related content whenever possible.
 
-## Style {#style}
+## Style <a id="style"></a>
 
 As an online program, Digest Comments have unique formatting requirements distinct from other legal journal writings. Below are some common items to check:
 
@@ -19,21 +19,21 @@ As an online program, Digest Comments have unique formatting requirements distin
 * Do not hyphenate the following words: decisionmaker, factfinder
 * Italicize or bold for emphasis, as underlines look like a broken link.
 
-## Commas {#commas}
+## Commas <a id="commas"></a>
 
 When listing three or more things, separate each pair with a comma, including the last pair. The last comma precedes the coordinating conjunction \(e.g. _and_ or _or_\).
 
 > **Example:** Lions, tigers, and bears.
 
-## Symbols {#symbols}
+## Symbols <a id="symbols"></a>
 
 Outside of citations, do not use "§" and "¶." Instead, always spell out and capitalize "Section" and "Paragraphs" in place of symbols.
 
-## Quotations {#quotations}
+## Quotations <a id="quotations"></a>
 
 **Avoid block quotations to the extent possible.** You should be linking to sources, so there’s no need to quote in length. The exception to this rule, though, is the situation when you are analyzing statutory language; in that case, having the statute conveniently displayed in the body of the article is encouraged.
 
-## Citations {#citations}
+## Citations <a id="citations"></a>
 
 _Digest_ Comments need not follow Bluebook citation format. Indeed, you should cite sources primarily through hyperlink. Please archive your links to prevent linking to sources that later become unavailable. The Editing Team can also help out with this during the editing process. Please use \(recommended\) or  to archive your links.
 

comments/commentstylecitation/citations.md

@@ -1,2 +1,4 @@
 # Citations
 
+
+

comments/commentstylecitation/commas.md

@@ -1,2 +1,4 @@
 # Commas
 
+
+

comments/commentstylecitation/quotations.md

@@ -1,2 +1,4 @@
 # Quotations
 
+
+

comments/commentstylecitation/requirements.md

@@ -1,2 +1,4 @@
 # Requirements
 
+
+

comments/commentstylecitation/style.md

@@ -1,2 +1,4 @@
 # Style
 
+
+

comments/commentstylecitation/symbols.md

@@ -1,2 +1,4 @@
 # Symbols
 
+
+

notes/notecontributorguide.md

@@ -2,15 +2,20 @@
 
 ## Welcome to the Note Contributor's Guide!
 
-A _Digest_ Note proffers a **novel analysis** on an issue related to law and technology. It contributes something new and interesting to the field. While a Note may include economic, cultural, or other types of arguments, it must revolve around the law.
+A Digest Note proffers a **novel analysis** on an issue related to law and technology. It contributes something new and interesting to the field. While a Note may include economic, cultural, or other types of arguments, it must revolve around the law.
 
 You should make sure that your Note idea is not preempted; do some background research and work with your Note Editor on refining the idea.
 
-**Your Tasks** 1. Come up with a **novel analysis** related to law and technology. 2. Provide an outline. 3. Write a 1500-2000 word analysis piece on the topic.
+{% hint style="success" %}
+**Your Tasks**
 
-1. Respond to suggestions from the [Note Editor](noteeditorguide.md).
+1. Come up with a **novel analysis** related to law and technology. 
+2. Provide an outline. 
+3. Write a 1500-2000 word analysis piece on the topic.
+4. Respond to suggestions from the [Note Editor](noteeditorguide.md).
+{% endhint %}
 
-## Requirements {#requirements}
+## Requirements <a id="requirements"></a>
 
 ### Novelty
 
@@ -28,13 +33,13 @@ Possible topics include
 
 ### Length
 
-Your Note should be within 1500-2000 words. You may go over 2000 words but only if both you and your Note Editor agree that your thesis requries the extra space. Every Note will have an objective portion, that sets up the context of your piece, and a subjective portion, that lays out your argument. There is no required distribution of words between the two portions -- the only requirement is that there is a subjective portion.
+Your Note should be within 1500-2000 words. You may go over 2000 words, but only if both you and your Note Editor agree that your thesis requries the extra space. Every Note will have an objective portion, that sets up the context of your piece, and a subjective portion, that lays out your argument. There is no required distribution of words between the two portions — the only requirement is that there is a subjective portion.
 
 Citations will not count towards the word limit.
 
 ### Citations
 
-Notes are more formal pieces than [_Digest_ Reports](../reports/reportcontributorguide.md). And so, you will need to provide pincites for every statement you attribute to someone else. **Follow the Bluebook whitepages subject to the rules laid out in the** [**Notes Style and Citation Guide**](notestylecitation/)**.** When submitting drafts, provide citations in endnotes rather than footnotes.
+Notes are more formal pieces than [Digest Reports](../reports/reportcontributorguide.md). And so, you will need to provide pincites for every statement you attribute to someone else. **Follow the Bluebook whitepages subject to the rules laid out in the** [**Notes Style and Citation Guide**](notestylecitation/)**.** When submitting drafts, provide citations in endnotes rather than footnotes.
 
 ## Logistics
 
@@ -56,7 +61,7 @@ Please submit drafts as either .doc or .docx files. Label drafts in the followin
 > `contributor_name` `draft_version` `date_emailed`  
 > **Example:** Fishwick First Draft 2017-06-30.doc
 
-## Writing Process in a Nutshell {#nutshell}
+## Writing Process in a Nutshell <a id="nutshell"></a>
 
 The process can be broken down into the following steps.
 
@@ -65,13 +70,13 @@ The process can be broken down into the following steps.
 3. [Second Draft](notecontributorguide.md#second)
 4. [Submission](notecontributorguide.md#submission)
 
-## Outline/Rough Draft {#outline}
+## Outline/Rough Draft <a id="outline"></a>
 
 This is an opportunity for the Note Editor to provide feedback on the Note in the early stages of writing it, so that you can tailor, structure, and address issues. The outline/draft should be more than the proposal, and should reflect some research, but it needn’t be a complete article. The Note Editor should be available in case you have questions or would like help with the direction of the Note.
 
 There may be multiple back-and-forths with the Note Editor on the outline. This is ok: you want to minimize the number of major substantive edits once you start writing.
 
-## First Draft {#first}
+## First Draft <a id="first"></a>
 
 **Your Tasks**
 
@@ -98,7 +103,7 @@ If at any point the Note Editor has a question or concern regarding the Note or
 
 In between the first and second drafts, feel free to reach out to the Note Editor for any substantive or grammatical questions. The editing process for the second draft should adhere to the same guidelines as the editing process for the first draft. By the time the second draft is formally submitted, the Note should be organized and coherent. Most if not all sources should be found.
 
-## Second Draft {#second}
+## Second Draft <a id="second"></a>
 
 **Your Tasks**
 
@@ -118,7 +123,7 @@ If all the necessary changes are grammatical and there are only very minor subst
 
 If the Note requires substantial change, the Note Editor should email \[Submissions Editor email\] and [email protected] a copy of the Note and a description of these proposed major changes. The Digest Masthead will look at the Note and determine whether these major changes can be made in time for publication or if publication of the Note’s publication needs to be delayed. You should be working closely with the Note Editor throughout the editing process so that substantive changes will not be necessary at this point.
 
-## Submission {#submission}
+## Submission <a id="submission"></a>
 
 After both you and your Note Editor agree on the final draft, the Note Editor will email this finalized draft to