53 | {description}
57 |{siteConfig.tagline}
72 |
53 | {description}
57 |{siteConfig.tagline}
72 |
56 | {description}
60 |{siteConfig.tagline}
75 |
56 | {description}
60 |{siteConfig.tagline}
75 |})
11 |
12 | The United States has an access to justice crisis. The "access to justice gap" is the
13 | name for the difference between the 14%[^1] of Americans who get help for their
14 | legal problems in court and the vast majority, 86% of Americans, who do not.
15 |
16 | In courts around the country (and the world), people do their best to solve
17 | problems on their own without the help of an attorney in a legal system that is
18 | designed to be used exclusively for and by attorneys. In some cases they fare
19 | badly, and in other cases they do not get help for a problem at all.
20 |
21 | This problem is not evenly distributed. In landlord-tenant cases, landlords are
22 | represented as much as 90% of the time, for example,
23 | with tenants only represented 10% of the time.[^2]
24 |
25 | Not every problem needs an attorney, and not every litigant wants an attorney.
26 | But it is challenging for people with legal problems to find solutions without
27 | an attorney, too. Regulatory barriers, including state rules that purport to
28 | regulate the unauthorized practice of law, can stop people with legal problems
29 | from solving their problems in less expensive or more accessible ways.
30 |
31 | ## A latent legal market?
32 |
33 | Some authors, including [Richard Granat](https://www.richardgranat.com/) and [Clio](https://clio.com)'s
34 | Jack Newton[^3],
35 | believe that this "access to justice gap" is also an opportunity. This is often
36 | called the latent legal market. In other words: some fraction of the people who
37 | have legal problems but do not currently use an attorney to solve those problems
38 | may be willing and able to pay for **something**. Chances are, that
39 | **something** will not look much like the traditional legal services that are
40 | already offered today.
41 |
42 | ## Footnotes
43 |
44 | [^1]: LEGAL SERVICES CORPORATION, [The Justice Gap: Measuring the Unmet Civil Legal Needs of Low-income Americans](https://www.lsc.gov/our-impact/publications/other-publications-and-reports/justice-gap-report) (2017). This number has been persistent across decades.
45 |
46 | [^2]: AMERICAN CIVIL LIBERTIES UNION, [Tenants' Right to Counsel is Critical to Fight Mass Evictions and Advance Race Equity During the Pandemic and Beyond](https://www.aclu.org/news/racial-justice/tenants-right-to-counsel-is-critical-to-fight-mass-evictions-and-advance-race-equity-during-the-pandemic-and-beyond/), January 12, 2021. [perma.cc](https://perma.cc/WXH9-N7AR)
47 |
48 | [^3]: Merken, Sara. ["Why Clio's Jack Newton sees profits and progress in the 'latent legal market'"](https://www.reuters.com/legal/legalindustry/why-clios-jack-newton-sees-profits-progress-latent-legal-market-2021-08-12/), Reuters, August 12, 2021, [perma.cc](https://perma.cc/W99F-J8FV)
--------------------------------------------------------------------------------
/docs/about-legal-tech-class.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: about-legal-tech-class
3 | title: About this text book
4 | sidebar_label: About
5 | ---
6 |
7 | The aim of this living "textbook" is to help you, the student, to learn the
8 | fundamentals of legal technology. You may read this "book" completely on your
9 | own or with a professor in a formal setting.
10 |
11 | This is meant to be a collection of material covering the very wide and diverse
12 | topic of legal technology. As such, any given class may zero in on a small
13 | subset of the material. For the most part, the materials are aimed at "doers",
14 | but there are plenty of links and materials aimed at thinking about legal
15 | technology.
16 |
17 | You can use this material to to learn how to become a developer in an open
18 | source expert system called [Docassemble](https://docassemble.org), as well as
19 | view links to materials for learning other platforms, including [A2J
20 | Author](https://a2jauthor.org), [QnA Markup](https://qnamarkup.org), and
21 | [HotDocs](https://hotdocs.com).
22 |
23 | There are plenty of practical tips for becoming an effective developer of expert
24 | systems and document automation platforms: from design thinking to project
25 | management and using plain language.
26 |
27 | You can also learn about the theory and principles that we feel every legal
28 | technologist should know. For example:
29 |
30 | * What is the [access to justice problem](a2j/a2j.md), and how can technology help address it?
31 | * How do existing legal service delivery models serve users of the legal system?
32 | * How does law regulating lawyers address legal technology?
33 | * How can technology be a tool for perpetuating and exacerbating existing
34 | injustices?
35 | * What special risks come with legal technology that aren't present in
36 | one-to-one representation?
37 |
38 | By the end of a class or a self-guided learning session using the materials
39 | here, you should be a confident legal technologist. You will have a sense of
40 | where to go next in your learning journey. Legal technology is an exciting
41 | field; an area that changes constantly in a legal industry that is otherwise
42 | built so much on the past.
43 |
44 | [Quinten Steenhuis](https://nonprofittechy.com) is the author and editor of
45 | almost all of the content as of 2020, so the material reflects his interests and
46 | biases. However, he hopes to encourage collaboration from many sources, and the
47 | material will start to become a centralized library reflecting many overlapping
48 | goals. Several people have contributed thoughts and ideas on [this Trello
49 | board](https://trello.com/b/Fz9PIm2g/project-materials).
50 |
51 | All content is released under a Creative Commons [Non-commercial
52 | Attribution/Share-alike
53 | license](https://creativecommons.org/licenses/by-nc-sa/2.0/).
54 |
55 | Quinten Steenhuis, June 2020
--------------------------------------------------------------------------------
/docs/appendices/editing-docusaurus.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: editing-docusaurus
3 | title: Editing
4 | sidebar_label: Editing
5 | ---
6 |
7 |
8 | Recommend enable Windows feature Windows Subsystem for Linux and then the Ubuntu image from Microsoft Store.
9 |
10 | In VS Code, you can install the plugins:
11 |
12 | Remote - WSL
13 | Markdown Preview Enhanced
14 | Markdown Preview Mermaid
15 |
16 | To see what you are doing as you work.
17 |
18 | ## Quick start
19 |
20 | git clone
21 |
22 | install yarn, node and npm
23 |
24 | run `yarn` inside the git repository to download all Node dependencies.
25 |
26 |
27 | ## Installing the remark-mermaid plugin
28 |
29 | You don't need to re-do this. But here are my configuration notes:
30 |
31 | to create mermaid graphs, use remark-mermaid plugin. This should install when you run `yarn`
32 |
33 | To build on your environment, you need to install dependencies for chrome-headless
34 |
35 | ```
36 | sudo apt-get install gconf-service libasound2 libatk1.0-0 libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgcc1 libgconf-2-4 libgdk-pixbuf2.0-0 libglib2.0-0 libgtk-3-0 libnspr4 libpango-1.0-0 libpangocairo-1.0-0 libstdc++6 libx11-6 libx11-xcb1 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxext6 libxfixes3 libxi6 libxrandr2 libxrender1 libxss1 libxtst6 ca-certificates fonts-liberation libappindicator1 libnss3 lsb-release xdg-utils wget
37 | ```
38 |
39 | ### How I enabled the mermaid plugin (don't need to re-do this step)
40 |
41 | edit docusaurus.config.js
42 | At top of file, add
43 | `const mermaid = require('remark-mermaid')`
44 |
45 | In the "docs" block, add `remarkPlugins: [mermaid],`
46 | See https://mdxjs.com/advanced/plugins which explains how remark plugins work. Not explained in Docusaurus documentation.
--------------------------------------------------------------------------------
/docs/appendices/stub.md:
--------------------------------------------------------------------------------
1 | ---
2 | # slug: id
3 | # title:
4 | # sidebar_label:
5 | ---
6 | This is a stub
7 |
--------------------------------------------------------------------------------
/docs/avoiding-failure/avoiding-failure.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: avoiding-failure
3 | title: Learning to Fail
4 | sidebar_label: Learning to Fail
5 | ---
6 |
7 |
8 |
9 | Something that I emphasize at the beginning of every class is the importance of
10 | cultivating what experts call a "growth mindset". Having a growth mindset means:
11 |
12 | 1. Recognizing that computer programming is a learnable, practiceable skill.
13 | 1. Understanding that [there is no "coding
14 | gene."](https://cacm.acm.org/blogs/blog-cacm/179347-anyone-can-learn-programming-teaching-genetics/fulltext),
15 | [perma.cc](https://perma.cc/D5PF-FFKY). Comfort, practice, and interest make
16 | up the bulk of being a good programmer.
17 | 1. Allowing yourself to be comfortable failing repeatedly and recognizing that
18 | failure is part of the learning process.
19 | 1. Treating yourself kindly.
20 |
21 | ## Software development gives you multiple chances
22 |
23 | Lawyers and law students often find that they have to redefine the meaning of
24 | being a successful learner when they tackle coding the first time. In many law
25 | school classes, you get a single high stakes test at the end of the semester. As
26 | a litigator, you may also have a single opportunity to make your case.
27 |
28 | ## Errors are normal in software development
29 |
30 | Software development is not like that. The process of computer programming often
31 | involves repeatedly running into errors. Errors are an opportunity to learn. In
32 | addition, [creating a successful product requires
33 | iteration](https://en.wikipedia.org/wiki/Software_prototyping). The first draft
34 | is often the first chance to do real discovery about what works and what does
35 | not work.
36 |
37 | ## Fluency comes with practice; Memorizing is harmful
38 |
39 | Law students, especially coming out of the first year, get used to a Socratic
40 | method of instruction. Students are given written decisions and expected to
41 | synthesize and puzzle out rules. Being called on unexpectedly is a chance to
42 | shine or to be embarassed in front of a hundred peers. Questions in class are
43 | given cryptic responses. As a result, students learn to keep questions to
44 | themselves, and to wait to ask or share what they learn until they are sure
45 | that their answer is right.
46 |
47 | In programming, in contrast, the art of looking up answers is a
48 | [meme](https://www.google.com/search?q=stack+overflow+meme) that never dies.
49 | Programming rewards efficiency, and re-writing a solution that already exists is
50 | discouraged. It is not just okay, but expected to use libraries, prewritten
51 | code, and samples to reduce reinvention of basic components of your product.
52 | There is plenty of room to demonstrate your individual learning while using
53 | the available resources to:
54 |
55 | 1. Look up model answers to similar problems;
56 | 1. Try and fail and try and fail until something works;
57 | 1. Ask for help when you are stuck, even if you think the problem is
58 | embarassingly simple.
59 |
60 |
61 | Software development is a creative endeavor that can be truly exhilarating.
62 | There is the struggle of creation and then the excitement and joy of producing
63 | something that can live on in the world. Most of all, it should be fun.
64 |
65 | [Learn more about growth
66 | mindset](https://abaforlawstudents.com/2017/09/12/growth-mindset-law-school-success/)
67 |
--------------------------------------------------------------------------------
/docs/changing-legal-profession/changing-legal-profession.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: changing-legal-profession
3 | title: The Changing Legal Profession
4 | sidebar_label: Changing Legal Profession
5 | ---
6 |
7 | ## Reading list
8 |
9 | * Richard Susskind, [Upgrading Justice](https://www.youtube.com/watch?v=Vd0PhomzT7g)
10 | * John O. McGinnis & Russell G. Pearce, [The Great Disruption: How Machine Intelligence Will Transform the Role of Lawyers in the Delivery of Legal Services](http://papers.ssrn.com/sol3/papers.cfm?abstract_id=2436937)
11 |
12 | ### Future of law
13 | * David Weinberger, [Would a Google Car Sacrifice You for the Sake of the Many?](https://medium.com/@dweinberger/would-a-google-car-sacrifice-you-for-the-sake-of-the-many-e9d6abcf6fed)
14 | * David Colarusso, [Driverless Cars Poised to Undermine War on Drugs](https://lawyerist.com/driverless-cars-war-drugs/)
15 | * Nick Szabo, [Smart Contracts: Building Blocks for Digital Markets](http://www.fon.hum.uva.nl/rob/Courses/InformationInSpeech/CDROM/Literature/LOTwinterschool2006/szabo.best.vwh.net/smart_contracts_2.html)
16 | * Lauritsen and Steenhuis, [Substantive Software Quality: a Gathering Storm?](https://static1.squarespace.com/static/571acb59e707ebff3074f461/t/5cfe69e4a851d80001bdf162/1560177127345/Substantive+Legal+Software+Quality+-+A+Gathering+Storm.pdf)
17 |
--------------------------------------------------------------------------------
/docs/changing-legal-profession/stub.md:
--------------------------------------------------------------------------------
1 | ---
2 | # slug: id
3 | # title:
4 | # sidebar_label:
5 | ---
6 | This is a stub
7 |
--------------------------------------------------------------------------------
/docs/choosing-project/choosing-project.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: choosing-project
3 | title: Choosing the right project
4 | sidebar_label: Choosing a project
5 | ---
6 |
7 | Not every project is a good one. Before you start putting hands on the keyboard, think carefully about whether the project you're going to embark on will succeed.
8 |
9 | Interview authors need to think about:
10 |
11 | 1. Whether they are just automating a bad process, which will remain as painful on the computer as it is on paper
12 | 1. Whether they chose the right part of the project to automate (scope)
13 | 1. Whether automation will significantly improve the process in some way
14 | 1. Whether the project has a chance of succeeding in the real world.
15 |
16 | ## Paving cow paths
17 |
18 | It's [apocrypha](https://www.bostonmagazine.com/news/2018/03/06/boston-streets-cow-paths/), but rumor has it that the famously confusing streets of Boston are a result of letting cows wander and then paving the very paths that they created into streets. In the IT world, _paving a cow path_ means taking an existing process and replicating it in code, without considering if the process itself can be improved.
19 |
20 | App developers can be guilty of this, sometimes as innocent bystanders who are trying to improve a process created by the courts, a legislator, or a government agency. Still, sometimes energy is better spent lobbying one of those groups to improve the process than automating it as-is.
21 |
22 | When you are assembling a particularly bad form, it's worth talking to court clerks or agency representatives to find out if they'd accept your alternative version of it that makes it work better.
23 |
24 | If your job is automating forms, try getting a seat on the court's form committee. These tend to open up regularly. They may appreciate hearing from someone who has thought about the forms in such depth.
25 |
26 | ## Scope
27 |
28 | It's best to start with a small scope, and then build out. Even then, take time to give yourself a reality check every so often. If the project is never-ending, see if there are features you should eliminate or postpone to get something out into the real world. A feature freeze is a healthy thing in every project. There is no substitute for the feedback of real users. Delaying your project to add a "critical" feature has less value than releasing a smaller project and seeing how your users react.
29 |
30 | Choose a reasonable scope, and then communicate it clearly throughout your app. Over-broad projects can:
31 |
32 | 1. Never be completed
33 | 1. Be very difficult to maintain and update when law changes
34 | 1. Mislead users, if they seem to cover an edge-case that they really don't
35 |
36 | ## Value add
37 |
38 | Is your project greatly improving the user's experience? Or is it simply letting someone use a keyboard instead of a pen? Keep in mind that a pen is a very intuitive user interface, and even the best computer interface takes more cognitive load. An app with no value add can in fact be a negative.
39 |
40 | Good apps:
41 |
42 | 1. Save the user significant time and effort
43 | 1. Eliminate redundant steps
44 | 1. Hide confusing and irrelevant branches when they don't apply to the user's situation
45 | 1. Provide guidance along the way
46 | 1. Make use of external knowledge about the world, where appropriate. For example, matching addresses to courts, or auto-completing fields based on the user's location.
47 |
48 | ## Feasibility
49 |
50 | Sometimes even the best app will wither on the vine. Think about whether your app will succeed.
51 |
52 | Do you:
53 |
54 | 1. A place to host the app at a reasonable cost and with a reasonable amount of staff time required to up keep?
55 | 1. Have a client base that can access the platform you chose to use? For example, does it work on a mobile phone (which is the only way many Americans can access the Internet)
56 | 1. Have buy-in from the communities that can help promote your app, such as third-party vendors or social service agencies?
57 | 1. A way to keep the app up to date when the law changes in a year?
58 |
59 | ## Further reading
--------------------------------------------------------------------------------
/docs/classes/class-overview.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: class-overview
3 | title: Overview of Classes
4 | sidebar_label: Overview of Classes
5 | ---
6 |
7 | This section of the textbook contains curated class materials, including
8 | exercises organized in a logical order for each individual class.
9 |
10 |
--------------------------------------------------------------------------------
/docs/classes/docacon-2020/customizing-appearance.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: customizing-appearance
3 | title: Customizing Appearance
4 | sidebar_label: Customizing Appearance
5 | ---
6 |
7 | ## Creating a custom title and subtitle for your interview
8 |
9 | You can customize almost everything about a docassemble interview's
10 | appearance right out of the box. Something you may want to do early on
11 | is to change the title that appears in the navigation bar. You do this
12 | by customizing the [Metadata](https://docassemble.org/docs/initial.html#metadata)
13 | block.
14 |
15 | ```yaml
16 | ---
17 | metadata:
18 | title: |
19 | Bill and Ted's Excellent Title
20 | short title: |
21 | Excellent
22 | ---
23 | question: Hello, World
24 | mandatory: True
25 | ```
26 |
27 | ## Using a pre-built Bootstrap theme
28 |
29 | A website's appearance is often controlled with a CSS (cascading style sheet)
30 | file. Docassemble allows you to use your own CSS to change the appearance of
31 | interviews. A common way to change the appearance of docassemble is with a
32 | pre-built [Bootstrap](https://getbootstrap.com/) theme.
33 |
34 | Bootstrap is currently the world's most popular framework for layout and style
35 | of a website. That makes it easy to find a style that someone else created and
36 | adapt it to your needs.
37 |
38 | A good source for free, pre-built themes is [Bootswatch](https://www.bootstrapcdn.com/bootswatch/).
39 |
40 | Add a custom CSS file to your interview with the
41 | [Features](https://docassemble.org/docs/initial.html#javascript) block, and add
42 | a custom Bootstrap theme with the [bootstrap
43 | theme](https://docassemble.org/docs/initial.html#bootstrap%20theme) directive.
44 |
45 | ```yaml
46 | ---
47 | features:
48 | bootstrap theme: https://stackpath.bootstrapcdn.com/bootswatch/4.5.0/cerulean/bootstrap.min.css
49 | ---
50 | question: Hello, World
51 | mandatory: True
52 | ```
53 |
54 | You may find yourself wanting to build a theme with custom colors and more. Try experimenting
55 | with one of these tools:
56 |
57 | * [Bootstrap.build](https://bootstrap.build/)
58 | * [Bootstrap Magic](https://pikock.github.io/bootstrap-magic/)
59 |
60 | The number and variety of options, even with a builder, can be overwhelming. The
61 | docassemble documentation includes some
62 | [tips](https://docassemble.org/docs/config.html#bootstrap%20theme) to help.
63 |
64 | ## Decorating your interview with images
65 |
66 | One of the cool features of docassemble is the ability to natively
67 | access a massive set of free icons called [Font-Awesome](https://fontawesome.com/icons?d=gallery&m=free).
68 |
69 | To insert an icon into your interview, just reference it using the shorthand
70 | `:icon-name:` syntax.
71 |
72 | Try running the interview below in your docassemble playground.
73 |
74 | ```yaml
75 | ---
76 | question: |
77 | What is the weather like today?
78 | fields:
79 | - no label: weather
80 | datatype: radio
81 | choices:
82 | - Sunny
83 | - Rainy
84 | - Snowy
85 | - Cloudy
86 | ---
87 | question: |
88 | Hello, World
89 | subquestion: |
90 | Have a
91 | % if weather == 'Sunny':
92 | :sun:
93 | % elif weather == 'Rainy':
94 | :cloud-rain:
95 | % elif weather == 'Snowy':
96 | :snowflake:
97 | % elif weather == 'Cloudy':
98 | :cloud-sun:
99 | % endif
100 | day!
101 | mandatory: True
102 | ```
103 |
104 | You can also add a Font-Awesome icon as a "decoration" that appears in the
105 | top right corner of the interview.
106 |
107 | ```yaml
108 | ---
109 | mandatory: True
110 | decoration: globe-africa
111 | question: |
112 | Hello, World
113 | ```
114 |
115 | And use a Font-Awesome icon as a button:
116 |
117 | ```yaml
118 | ---
119 | question: |
120 | What is the weather like today?
121 | field: weather
122 | buttons:
123 | - Sunny: Sunny
124 | image: sun
125 | - Rainy: Rainy
126 | image: cloud-rain
127 | - Snowy: Snowy
128 | image: snowflake
129 | - Cloudy: Cloudy
130 | image: cloud-sun
131 | ---
132 | question: |
133 | Hello, World
134 | subquestion: |
135 | Have a
136 | % if weather == 'Sunny':
137 | :sun:
138 | % elif weather == 'Rainy':
139 | :cloud-rain:
140 | % elif weather == 'Snowy':
141 | :snowflake:
142 | % elif weather == 'Cloudy':
143 | :cloud-sun:
144 | % endif
145 | day!
146 | mandatory: True
147 | ```
148 |
149 | Quinten Steenhuis, June 2020
--------------------------------------------------------------------------------
/docs/classes/explorations/explorations.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: exploration-functions
3 | title: Exploration in Functions
4 | sidebar_label: |
5 | Experimenting with functions
6 | ---
7 |
8 | * make text use sentence case
9 | * Show a map of an address
--------------------------------------------------------------------------------
/docs/classes/other-classes.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: other-classes
3 | title: Other Classes
4 | sidebar_label: Other Classes
5 | ---
6 |
7 | ## Links to general legal tech syllabi at other locations
8 |
9 | [The master list](https://techforlawstudents.classcaster.net/syllabi-commons/),
10 | maintained by [John Mayer](https://www.cali.org/user/138) at the [Center for
11 | Computer Asssisted Legal Instruction](https://cali.org).
12 |
13 | ### Docassemble-specific courses
14 |
15 | * [University of Alberta, Coding the Law](https://github.com/Gauntlet173/CodingTheLaw)
16 | * [Flinders University, Adelaide, Law in a Digital Age](https://github.com/LLAW3301)
17 |
18 | ## Other Open Course Concepts
19 |
20 | * [A2J Author Course Project](https://a2jclinic.classcaster.net/)
--------------------------------------------------------------------------------
/docs/classes/resources.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: resources
3 | title: Resources for Instructors
4 | sidebar_label: Teaching Resources
5 | ---
6 |
7 | ## Instructional Tools
8 |
9 | * [CALI Instapoll](https://www.cali.org/content/cali-instapoll)
10 | * [Repl.it](http://repl.it/) for an online collaborative editor environment
11 | * [Trinket.io](https://trinket.io) for an online editor/run-time environment
12 |
13 | ## Further Reading
14 |
15 | * [10 Quick Tips for Teaching Programming](https://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1006023)
16 |
--------------------------------------------------------------------------------
/docs/classes/small-firms/2020/2020-legal-tech-small-firms.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: 2020-legal-tech-small-firms
3 | title: Fall 2020, Legal Technology for Small Firm Practice
4 | sidebar_label: |
5 | Suffolk Law School Fall 2020: Legal Technology for Small Firm Practice
6 | ---
7 |
8 | ## Course number
9 |
10 | LAW-2156-AD
11 |
12 | ## About the Instructor
13 | Quinten Steenhuis, QSteenhuis@suffolk.edu
14 |
15 | [Twitter](https://twitter.com/qsteenhuis)
16 | [Website](https://nonprofittechy.com)
17 |
18 | Meeting time: 2 PM - 3:50 PM, Mondays, Fall 2020
19 |
20 | The practice of law is increasingly built around digital tools. Lawyers who
21 | understand technology have an advantage in the marketplace, both to reduce their
22 | operating costs and to help more people. Lawyers today use technology to:
23 |
24 | * Run the business side of the law firm, including
25 | * Tracking client information
26 | * Reaching new clients
27 | * Help make decisions
28 | * Reduce repetitive tasks through automation and templates
29 | * Deliver legal services directly to litigants
30 |
31 | This class will provide you a survey of the world of legal technology, with
32 | special attention to tools that are free or low cost and useful to owners and
33 | practitioners in small firms. In the second half of the class, you will produce
34 | a final project using one of the tools that we learned in class to solve a legal
35 | problem.
36 |
37 | ## Class Materials
38 |
39 | * [Syllabus](2020-legal-tech-small-firms-syllabus.md)
40 | * [Final Project](2020-legal-tech-small-firms-rubric.md)
41 | * [Weekly Reading List and Assignments](2020-legal-tech-small-firms-assignments.md)
42 | * [Class Zoom
43 | session](https://sumail-my.sharepoint.com/:w:/g/personal/qsteenhuis_adm_suffolk_edu/EXqiagBAmUVDgsfJD-VGzRMBGNyQe45bZ7AMhpfPBL2gNw?e=iyfWTc)
44 | (Must be logged in with Suffolk University account to view)
45 | * [Class Notebook](https://sumail-my.sharepoint.com/:o:/g/personal/qsteenhuis_adm_suffolk_edu/Eh87_fq9XfpItNZonOuSA7gBv-7xNlePabE_CihbzmcCuw?e=GNAtgS)
46 | * [Slack](https://suffolklitlab.slack.com/) (Join the channel `#2020-legal-tech-small-firm-practice`)
47 | * [Textbook](about-legal-tech-class.md)
48 |
49 | ## Resources
50 |
51 | * [Clio](https://www.clio.com), [Clio University](https://cliouniversity.learnupon.com/)
52 | * [CaseText](https://www.casetext.com)
53 | * [LIT Lab Docassemble Server](https://apps-dev.suffolklitlab.org) (For Suffolk Law School students only)
54 | * [Community.Lawyer](https://community.lawyer)
55 | * [QnAMarkup.org](https://www.qnamarkup.org/)
56 | * [Legal Tech Assessment](https://ltaweb.azurewebsites.net/)
--------------------------------------------------------------------------------
/docs/classes/small-firms/2021/2021-legal-tech-small-firms.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: 2021-legal-tech-small-firms
3 | title: Fall 2021, Legal Technology for Small Firm Practice
4 | sidebar_label: |
5 | Suffolk Law School Fall 2021: Legal Technology for Small Firm Practice
6 | ---
7 |
8 | ## Course number
9 |
10 | LAW-2156-AD
11 |
12 | ## About the Instructor
13 | Quinten Steenhuis, QSteenhuis@suffolk.edu
14 |
15 | [Twitter](https://twitter.com/qsteenhuis)
16 | [Website](https://nonprofittechy.com)
17 |
18 | Meeting time: 2 PM - 3:50 PM, Mondays, Fall 2021, Sargent Hall Room 305
19 |
20 | The practice of law is increasingly built around digital tools. Lawyers who
21 | understand technology have an advantage in the marketplace, both to reduce their
22 | operating costs and to help more people. Lawyers today use technology to:
23 |
24 | * Run the business side of the law firm, including
25 | * Tracking client information
26 | * Reaching new clients
27 | * Help make decisions
28 | * Reduce repetitive tasks through automation and templates
29 | * Deliver legal services directly to litigants
30 |
31 | This class will provide you a survey of the world of legal technology, with
32 | special attention to tools that are free or low cost and useful to owners and
33 | practitioners in small firms.
34 |
35 | Grading is based on two independent learning modules, a critique, and a final
36 | project which will make up the majority of your grade. You will use one of the
37 | technologies that we learned in class for your final project. Students will also
38 | complete weekly short reflections on the nightly reading.
39 |
40 | ## Class Materials
41 |
42 | * [Syllabus](2021-legal-tech-small-firms-syllabus.md)
43 | * [Final Project](2021-legal-tech-small-firms-rubric)
44 | * [Weekly Reading List and Assignments](2021-legal-tech-small-firms-assignments.md)
45 | * [Class Zoom
46 | session](https://sumail-my.sharepoint.com/:w:/g/personal/qsteenhuis_adm_suffolk_edu/EXqiagBAmUVDgsfJD-VGzRMBGNyQe45bZ7AMhpfPBL2gNw?e=iyfWTc)
47 | (Must be logged in with Suffolk University account to view)
48 | * [Class Notebook](https://sumail-my.sharepoint.com/:o:/g/personal/qsteenhuis_adm_suffolk_edu/Eh87_fq9XfpItNZonOuSA7gBv-7xNlePabE_CihbzmcCuw?e=GNAtgS)
49 | * [Textbook](about-legal-tech-class.md)
50 |
51 | ## Resources
52 |
53 | * [Clio](https://www.clio.com), [Clio University](https://cliouniversity.learnupon.com/)
54 | * [LIT Lab Docassemble Server](https://apps-dev.suffolklitlab.org) (For Suffolk Law School students only)
55 | * [Community.Lawyer](https://community.lawyer)
56 | * [QnAMarkup.org](https://www.qnamarkup.org/)
57 | * [Legal Tech Assessment](https://ltaweb.azurewebsites.net/)
--------------------------------------------------------------------------------
/docs/classes/smart-machines/2020/asssignment-repeated-information.md:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/SuffolkLITLab/legal-tech-class/54b8f644bedf5da562a559bb91d385c57ebfcbbb/docs/classes/smart-machines/2020/asssignment-repeated-information.md
--------------------------------------------------------------------------------
/docs/classes/smart-machines/2021/2021-smart-machines.md:
--------------------------------------------------------------------------------
1 | ---
2 | id: 2021-smart-machines
3 | slug: 2021-smart-machines
4 | title: Lawyering in the Age of Smart Machines
5 | sidebar_label: |
6 | Lawyering in the Age of Smart Machines (2021)
7 | ---
8 | ## Course number
9 | LAW-2156-AM
10 |
11 | ## About the Instructor
12 | Quinten Steenhuis, QSteenhuis@suffolk.edu
13 |
14 | [Twitter](https://twitter.com/qsteenhuis)
15 | [Website](https://nonprofittechy.com)
16 |
17 | ## Course information
18 | ### Meeting Time
19 |
20 | 6 PM-7:50 PM, Wednesdays, Spring 2021 Via Zoom
21 |
22 | ### Syllabus
23 | [Syllabus](2021-smart-machines-syllabus.md)
24 | ### Weekly Assignments
25 |
26 | [Assignments](2021-smart-machines-assignments.md)
27 | ### Final project
28 |
29 | [Final Project](2021-smart-machines-rubric.md)
30 | ## About the class
31 |
32 | The practice of law is increasingly built around digital tools. Lawyers who
33 | understand technology have an advantage in the marketplace, both to reduce their
34 | operating costs and to help more people. Lawyers today use technology to:
35 |
36 | * Run the business side of the law firm, including
37 | * Tracking client information
38 | * Reaching new clients
39 | * Help make decisions
40 | * Reduce repetitive tasks through automation and templates
41 | * Deliver legal services directly to litigants
42 |
43 | This class will provide you a survey of the world of legal technology, with
44 | special attention to the use of technology to serve underserved markets and to
45 | address the access to justice gap. In the second half of the class, you will
46 | produce a final project using one of the tools that we learned in class to solve
47 | a legal problem.
48 |
49 | We will have a variety of guest speakers in this class, representing the public
50 | interest, corporate, and academic perspectives on legal technology. Guest names
51 | and bios will be provided in advance.
52 | No programming experience or other technical background is required.
53 |
54 | ## Textbook/Course Materials
55 |
56 | All readings and course materials will be available online. You may choose to
57 | download and print various articles. You will be expected to sign up for free
58 | accounts on publically hosted websites, while other accounts will be provided
59 | for you. Students are expected to bring an Internet-connected laptop with a
60 | modern web browser to each class session.
61 |
62 | Consider a second monitor, which will cost less than any of your required
63 | textbooks. This will allow you to watch a screenshare while following along on
64 | your own computer. I recognize most students will not have this, and I do not
65 | expect anyone to buy one if it does not feel affordable. Please let me know when
66 | you need me to slow down so you can switch back and forth between the two views.
67 |
68 | ## Software tools
69 | We may make use of some of the following free websites and software applications:
70 |
71 | * GitHub (https://github.com)
72 | * Trello (https://trello.com)
73 | * Teams (https://www.microsoft.com/en-us/microsoft-teams/)
74 | * Docassemble (https://docassemble.org) (Instructor will provide server information)
75 | * QnAMarkup (https://qnamarkup.org)
76 | * Documate (https://documate.org)
77 |
78 | Required software will not need to be installed on your computer. You can use a Windows, Macintosh or Linux computer for all course assignments.
79 |
80 | ## Resources
81 |
82 | * [LIT Lab Docassemble Server](https://apps-dev.suffolklitlab.org) (For Suffolk Law School students only)
83 | * [Documate.org](https://documate.org)
84 | * [QnAMarkup.org](https://www.qnamarkup.org/)
85 | * [Legal Tech Assessment](https://ltaweb.azurewebsites.net/)
86 |
87 | ## Independent reading
88 |
89 | If you would like to stay up to date with the legal tech world, I recommend:
90 |
91 | * [Reimagining Justice](http://www.andreaperrypetersen.com.au/), podcast from Andrea Perry Petersen
92 | * [Lawtomatic](https://tinyletter.com/gteninbaum/archive), curated news by Dean Teninbaum
93 | * [Justice Tech Download](https://www.justicetech.download/), curated news from former ABA Journal reporter Jason Tashea
94 | * [LawSites](https://www.lawsitesblog.com/), blog by Bob Ambrogi, former editor-in-chief of The National Law Journal
95 | * [Law-tech-A2j](https://law-tech-a2j.org/), blog by Roger Smith (UK)
96 | * [Kristen Sonday](http://kristensonday.com/press), COO of Paladin sometimes writes on legal tech and A2J Tech. See also: [70 Female Founders in Legal Tech](https://kristensonday.medium.com/fifty-female-founders-in-legaltech-2d1b32020919).
97 |
--------------------------------------------------------------------------------
/docs/document-assembly.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: document-assembly
3 | title: What is Document Assembly?
4 | sidebar_label: Document Assembly
5 | ---
--------------------------------------------------------------------------------
/docs/ethical-issues/ethical-issues.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: ethical-issues
3 | title: Ethical issues in legal technology
4 | sidebar_label: Ethical issues
5 | ---
6 |
7 | ### Legal ethics and technology
8 | * New York State Bar Association, [Ethics Opinion No. 1132](http://www.nysba.org/EthicsOpinion1132/)
9 | * Will Hornsby, [Unauthorized Practice of Law in the 21st Century ](http://tdlp.classcaster.net/2012/03/30/tdlp-class-8-will-hornsby-unauthorized-practice-of-law-in-the-21st-century/0)
10 | * David Colarusso, [“Portland’s Precrime Experiment and the Limits of Algorithms”](https://lawyerist.com/precrime-in-portland-a-canary-in-the-data-mine/)
11 | * Mike Lissner, [“More Details on the PACER Vulnerability We Shared with the Administrative Office of the U.S. Courts”](https://free.law/2017/08/09/more-details-on-the-pacer-vulnerability-we-shared-with-the-administrative-office-of-the-courts/)
12 |
13 |
--------------------------------------------------------------------------------
/docs/ethical-issues/ethics-regulation.md:
--------------------------------------------------------------------------------
1 | * Lauritsen, [Liberty, Justice, & Legal Automata](http://scholarship.kentlaw.iit.edu/cgi/viewcontent.cgi?article=3983&context=cklawreview)
--------------------------------------------------------------------------------
/docs/feedback/feedback.md:
--------------------------------------------------------------------------------
1 | ---
2 | # slug: id
3 | # title:
4 | # sidebar_label:
5 | ---
6 | This is a stub
7 |
--------------------------------------------------------------------------------
/docs/forming-team/forming-team.md:
--------------------------------------------------------------------------------
1 | ---
2 | # slug: id
3 | # title:
4 | # sidebar_label:
5 | ---
6 | This is a stub
7 |
--------------------------------------------------------------------------------
/docs/gaining-audience/gaining-audience.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: gaining-audience
3 | title: Driving user acceptance of your application
4 | sidebar_label: Driving User Acceptance
5 | ---
6 |
7 | Whether you are building an application for profit or giving it away for free,
8 | the perfect app won't help someone who either does not know about or who
9 | does not think it is for them.
10 |
11 | ## Who is your audience?
12 |
13 | When I developed [MADE](https://www.gbls.org/MADE), my audience was tenants facing eviction,
14 | most of whom were low income. I also knew that they had only about 3 weeks, on average,
15 | to find my app before they could use it to fight their eviction. Most of my clients, as well,
16 | would only use my app once in their lives.
17 |
18 | Because of this, I decided to focus my outreach on social workers, other legal aid providers,
19 | and the court service centers, rather than direct outreach to tenants. Put simply, these
20 | third-parties were likely to become familiar with MADE over time and be able to recommend it
21 | to many tenants. What's more, tenants were likely to reach out to these providers at an early
22 | stage when their housing was at risk, in time to use the app.
23 |
24 | ## Increasing your search ranking
25 |
26 | ### Earning placement on existing highly-ranked sites
27 |
28 | In Massachusetts, the existing state-wide legal aid website, https://masslegalhelp.org, has a very
29 | high search ranking. In recent years, a new government-run website, https://mass.gov, has
30 | gained an even higher ranking. Getting placement on both of these sites for MADE required building
31 | relationships and earning trust of decision makers. There is no free lunch here. The result, however,
32 | is that both websites drive a significant fraction of our traffic.
33 |
34 | ### Gaining earned media
35 |
36 | ### Creating a content funnel
37 |
38 | UpSolve is one non-profit that has [very successfully driven growth](https://segment.com/blog/how-a-brooklyn-nonprofit-used-data-and-segment-s-help-to-find-a-path-for-scale-and-fight-poverty/) using the strategy of
39 | the content funnel.
40 |
41 | ## Keeping your users happy
42 |
43 | ### Net promoter score
44 |
45 | ## Further reading
46 |
47 | ## Contributors and acknowledgments
--------------------------------------------------------------------------------
/docs/ila.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: ilas
3 | title: What are interactive legal applications?
4 | sidebar_label: Interactive Legal Applications
5 | ---
--------------------------------------------------------------------------------
/docs/jinja2.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: jinja2
3 | title: The Jinja2 Templating Language
4 | sidebar_label: Jinja2
5 | ---
6 |
7 | Jinja2 plays the same role inside Microsoft Word docx templates that
8 | [Mako](mako.md) plays inside the interview file.
9 |
10 | Jinja was originally created as a [templating language for Django](https://jinja.palletsprojects.com/en/2.9.x/).
11 | Docassemble's version of Jinja is not quite the same; it's a variation built for
12 | [docx-template](https://docxtpl.readthedocs.io/en/latest/). It's useful to keep this in mind if you are
13 | trying to use an advanced feature and find that it doesn't work.
14 |
15 | Jinja statements allow you to:
16 |
17 | 1. Insert variables
18 | 1. Use conditional text
19 | 1. Use control structures to display repeated variables
20 |
21 | ## Insert variables
22 |
23 | To insert a variable into your document, surround it with double curly braces, like this: `{{ variable_name }}`.
24 |
25 | It's also possible to include Python code in the place of the variable name. For example, if you had
26 | assigned the value of `my_variable` as below:
27 |
28 | ```python
29 | my_variable = "lowercase name"
30 | ```
31 |
32 | Then you could use the `.capitalize()` [method of a string](https://docs.python.org/2.5/lib/string-methods.html)
33 | inside Jinja tags to make sure that it started with a capital letter, regardless of how the user entered it inside
34 | your application:
35 |
36 | ```jinja
37 | Dear {{ my_variable.capitalize() }}:
38 |
39 | I am writing to tell you...
40 | ```
41 |
42 | ## Use conditional text
43 |
44 | One of the most common uses of Jinja tags inside a docx template is to insert conditional text. There are two types
45 | of conditionals: in-line, and paragraph/bullet level conditionals.
46 |
47 | ### In-line conditional statements
48 |
49 | Jinja in-line conditionals are started with a curly brace and a % symbol, like `{% if condition %}` and closed with `{% endif %}`. You can optionally include both `{% elif %}` and `{% else %}` tags.
50 |
51 | ```jinja
52 | You are {% if person.age_in_years() < 13 %} a child {% elif person.age_in_years() < 20 %} a teenager {% else %} an adult. {% endif %}
53 | ```
54 |
55 | ### Paragraph-level conditional statements
56 |
57 | Sometimes you want to hide an entire paragraph if a certain condition is met. One time you may want to use this when several optional items are shown on a list. In this case, you use a slight variation: `{%p if... %}`.
58 |
59 | ```jinja
60 | * Apple
61 | * {%p if likes_bananas %}
62 | * Bananas
63 | * {%p endif %}
64 | ```
65 |
66 | If you leave out the `p`, you would have an empty line after `Apple`. Using `p` tells Docassemble to remove that line from the document.
67 |
68 | Make sure you use the `{%p endif %}` form to close the statement. Otherwise, Docassemble will raise an error that there is an unmatched if statement.
69 |
70 | ## Use control structures
71 |
72 | Control structures use the same syntax as conditional statements, surrounded by `{% %}` or `{%p %}`. You can use the same control structures (`for` and `while`) in Jinja that you can use in Python and wherever you can use Mako statements.
73 |
74 | ```jinja
75 | {%p for fruit in fruits %}
76 | * {{ fruit }}
77 | {%p endfor %}
78 | ```
79 |
80 | ## Further reading
81 |
82 | * https://docassemble.org/docs/documents.html#docx%20template%20file
--------------------------------------------------------------------------------
/docs/legal-tech-overview/examples.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: examples
3 | title: Examples of Legal Technology
4 | sidebar_label: Examples
5 | ---
6 |
7 | ## Some examples of legal tech
8 |
9 | This is not an attempt to create a list of all of the legal technology in the world.
10 | Think of this as a curated walkthrough of some popular legal technology tools.
11 |
12 | ### The OGs
13 |
14 | * [LexisNexis](https://www.lexisnexis.com/en-us/gateway.page)
15 | * [Westlaw](https://westlaw.com/)
16 |
17 | ### Innovative legal research alternatives to "Wexis"
18 |
19 | * [RossIntelligence](https://www.rossintelligence.com/)
20 | * [CaseText](https://casetext.com/)
21 |
22 | ### Innovative tools that help lawyers
23 |
24 | * [Wordrake](https://www.wordrake.com/)
25 | * [Litera](https://www.litera.com/)
26 |
27 | ### Contract management
28 |
29 | 30 | 31 | ### Innovative Legal Practice Management tools 32 | 33 | * [Clio](https://clio.com) 34 | * [Salesforce](https://salesforce.com) is the best-known web-based tool for 35 | managing customer contacts, although not legal-focused 36 | * Popular alternatives include [Hubspot](https://www.hubspot.com/products/crm), [Zoho](https://www.zoho.com/crm/), and [Lexicata](https://www.lexicata.com) (now owned by Clio) 37 | 38 | ### Best of breed client-facing applications 39 | 40 | * [UpSolve](https://upsolve.org) 41 | * [Rentervention](https://www.theoryandprinciple.com/rentervention-new/) 42 | 43 | ### Platforms to know for document assembly 44 | 45 | * [HotDocs](https://hotdocs.com) remains popular with a big installed base, 46 | although long in the tooth 47 | * [Docassemble](https://docassemble.org), a powerful open source alternative 48 | built on Python with strong customizability and expert system capabilities 49 | * [Documate](https://documate.org), a frontend for Docassemble that exposes 50 | most of its power 51 | * [Afterpattern](https://afterpattern.com/), a frontend for Docassemble 52 | with a free tier + marketplace 53 | * [A2JAuthor.org](https://a2jauthor.org), a popular non-commercial frontend to 54 | HotDocs which also includes limited document assembly capabilities that don't 55 | rely on HotDocs 56 | * [Neota Logic](https://www.neotalogic.com/), a powerful and popular system for 57 | building expert systems 58 | 59 | ### Chatbots 60 | 61 | * [QnAMarkup.org](https://qnamarkup.org) is a tool for rapidly building 62 | interactive flowcharts, with some advanced add-ins to support form filling as 63 | well 64 | 65 | ### Working with large datasets / E-discovery 66 | * [DataShare](https://datashare.icij.org/) 67 | 68 | ### Projects involving the author 69 | 70 | I think these are good examples, but I can't be objective! 71 | 72 | * [MADE](https://gbls.org/MADE). [Read more](https://www.nonprofittechy.com/2019/05/12/making-made-user-centered-design-in-practice/) 73 | * [MassAccess](https://massaccess.suffolklitlab.org) 74 | 75 | ## Further readings 76 | 77 |Here's how many law firms have done signings for the last 20 years. All this is changing because people don't have access to printers and scanners right now. Instead, they are forced to use e-signatures - and discover by accident all the inefficiencies of the last 20 years... pic.twitter.com/YRiqujrS7C
— Jack Shepherd (@jackwshepherd) April 30, 2020
78 | 79 | Author: Quinten Steenhuis, updated August 2020. -------------------------------------------------------------------------------- /docs/legal-tech-overview/substantive-vs-non-substantive.md: -------------------------------------------------------------------------------- 1 | --- 2 | slug: substantive-vs-non-substantive 3 | title: Substantive vs Non-Substantive Apps 4 | sidebar_label: Substantive Apps 5 | --- 6 | 7 | ## Substantive vs. Non-Substantive applications 8 | 9 | We can distinguish between _substantive_ apps that replace a traditional 10 | legal advice role, from non-substantive apps that simply make the job of a 11 | litigant or lawyer simpler. 12 | 13 | Substantive apps: 14 | * Gather facts from the user 15 | * Provide information that is tailored to the user's situation 16 | * May provide final documents that are similarly tailored to the user's 17 | situation 18 | 19 | In short, they act a lot like a lawyer who meets with a client. And users often 20 | treat these apps like lawyers. 21 | 22 | Substantive apps include: 23 | * Expert systems 24 | * Form and template filling applications 25 | -------------------------------------------------------------------------------- /docs/maintenance/maintenance.md: -------------------------------------------------------------------------------- 1 | --- 2 | # slug: id 3 | # title: 4 | # sidebar_label: 5 | --- 6 | This is a stub 7 | -------------------------------------------------------------------------------- /docs/mako.md: -------------------------------------------------------------------------------- 1 | --- 2 | slug: mako 3 | title: The Mako templating language 4 | sidebar_label: Mako 5 | --- 6 | 7 | Docassemble uses Mako for formatting throughout the interview file. Mako is also used inside [Markdown](markdown.md) templates. 8 | 9 | Inside docx template files, you will instead use the [Jinja](jinja2.md) templating language. 10 | 11 | You can read a full reference of Mako at the [project website](https://docs.makotemplates.org/en/latest/syntax.html). 12 | 13 | Mako statements allow you to: 14 | 15 | 1. Insert variables 16 | 1. Use conditional text 17 | 1. Use control structures to display repeated variables 18 | 19 | ## Insert variables 20 | 21 | To insert a variable into your document, start with a `$` and surround it with curly braces, like this: `${ variable_name }`. 22 | 23 | It's also possible to include Python code in the place of the variable name. For example, if you had 24 | assigned the value of `my_variable` as below: 25 | 26 | ```python 27 | my_variable = "lowercase name" 28 | ``` 29 | 30 | Then you could use the `.capitalize()` [method of a string](https://docs.python.org/2.5/lib/string-methods.html) 31 | inside Mako tags to make sure that it started with a capital letter, regardless of how the user entered it inside 32 | your application: 33 | 34 | ```mako 35 | Dear ${ my_variable.capitalize() }: 36 | 37 | I am writing to tell you... 38 | ``` 39 | 40 | ## Use conditional text 41 | 42 | You start conditional text with a % symbol at the beginning of the line. If you want to include a literal % symbol instead, use %%. Just like in Python, you need to include a : at the end of the conditional. The text underneath doesn't need to 43 | be indented. 44 | 45 | ```mako 46 | % if person.age_in_years() > 18: 47 | You are an adult 48 | % else: 49 | You are a child 50 | % endif 51 | ``` 52 | 53 | ## Use control structures 54 | 55 | Control structures start the same way as conditional statements, beginning with a % symbol at the start of the line. 56 | 57 | ```mako 58 | % for fruit in fruits: 59 | ${fruit} 60 | % endfor 61 | ``` 62 | -------------------------------------------------------------------------------- /docs/markdown.md: -------------------------------------------------------------------------------- 1 | --- 2 | slug: markdown 3 | title: The Markdown formatting language 4 | sidebar_label: Markdown 5 | --- 6 | 7 | ## The Markdown formatting language 8 | Like YAML, [Markdown](https://daringfireball.net/projects/markdown/) is meant to be a concise, human readable way to represent information: in this case, it represents elements such as font size, headers, bold, italic, formatted lists, and even links to resources on the WWW. Many forums, including the popular Reddit, allow you to format your comments using Markdown. However, it is not quite as expressive as an OOXML, Word, or RTF file would be. 9 | 10 | ```markdown 11 | #### Heading level 4 12 | **Bold text** 13 | _italic text__ 14 | 15 | 1. Numbered item 1 16 | 1. Numbered item 2 17 | 1. Numbered item 3 18 | ``` 19 | Turns into: 20 | 21 | #### Heading level 4 22 | 23 | **Bold text** 24 | 25 | _italic text_ 26 | 27 | 1. Numbered item 1 28 | 2. Numbered item 2 29 | 3. Numbered item 3 30 | 31 | ## Including variable text 32 | 33 | In order to add variable text, Docassemble uses the [Mako templating language](mako.md) which 34 | can be inserted directly almost anywhere Docassemble expects text, such as under a 35 | `question`, `subquestion`, `content` or `template` block. 36 | 37 | The [Docassemble documentation](https://docassemble.org/docs/markup.html) covers Markdown fairly well, with examples. 38 | 39 | This section was originally posted as a blog on [Nonprofittechy.com](https://www.nonprofittechy.com/2020/01/17/understanding-docassembles-yaml-interview-format/). -------------------------------------------------------------------------------- /docs/mdx.md: -------------------------------------------------------------------------------- 1 | --- 2 | slug: mdx 3 | title: Powered by MDX 4 | --- 5 | 6 | You can write JSX and use React components within your Markdown thanks to [MDX](https://mdxjs.com/). 7 | 8 | export const Highlight = ({children, color}) => ( {children} ); 14 | 15 |If you were to introduce someone to legal tech who knew nothing about it. What would be the best of breed apps you would showcase that let them understand what it is all about?#legaltech
— Quinten Steenhuis (@QSteenhuis) August 19, 2020
})
26 |
27 | ### Preparing the included interview
28 |
29 | 1. remove all mandatory blocks in the child interview
30 | 1. add a "named block" to the interview order block in the child interview
31 | 1. give each attachment a `variable name` if it does not already have one
32 |
33 | ### Reference the included interview in the umbrella interview
34 |
35 | 1. add a reference to the `named block` in the umbrella interview
36 | 1. add the new `variable name` to the download screen using `attachment code` or
37 | `ALDocumentBundle`
38 |
39 | ## Read more
40 |
41 | 1. https://docassemble.org/docs/logic.html#multiple%20interviews
42 | 1. [Naming your modular interview files](https://suffolklitlab.org/docassemble-AssemblyLine-documentation/docs/coding_style_guide/yaml#use-clear-filenames-for-modular-interview-files)
--------------------------------------------------------------------------------
/docs/practical-guide-docassemble/img/error_mandatory.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/SuffolkLITLab/legal-tech-class/54b8f644bedf5da562a559bb91d385c57ebfcbbb/docs/practical-guide-docassemble/img/error_mandatory.png
--------------------------------------------------------------------------------
/docs/practical-guide-docassemble/img/error_missing_question.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/SuffolkLITLab/legal-tech-class/54b8f644bedf5da562a559bb91d385c57ebfcbbb/docs/practical-guide-docassemble/img/error_missing_question.png
--------------------------------------------------------------------------------
/docs/practical-guide-docassemble/img/error_missing_template.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/SuffolkLITLab/legal-tech-class/54b8f644bedf5da562a559bb91d385c57ebfcbbb/docs/practical-guide-docassemble/img/error_missing_template.png
--------------------------------------------------------------------------------
/docs/practical-guide-docassemble/img/error_reading_yaml_file.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/SuffolkLITLab/legal-tech-class/54b8f644bedf5da562a559bb91d385c57ebfcbbb/docs/practical-guide-docassemble/img/error_reading_yaml_file.png
--------------------------------------------------------------------------------
/docs/practical-guide-docassemble/img/show_paragraph_marks.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/SuffolkLITLab/legal-tech-class/54b8f644bedf5da562a559bb91d385c57ebfcbbb/docs/practical-guide-docassemble/img/show_paragraph_marks.png
--------------------------------------------------------------------------------
/docs/practical-guide-docassemble/practical-guide-docassemble.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: practical-guide-docassemble
3 | title: What should you use Docassemble for?
4 | sidebar_label: What should you use Docassemble for?
5 | ---
6 |
7 | ## What should you use Docassemble for?
8 |
9 | If we look over our [legal technology taxonomy](legal-tech-overview/legal-tech-overview.md),
10 | which of these tasks is Docassemble best suited for?
11 |
12 | Docassemble's main metaphor is a linear series of step-by-step questions. Many of the things Docassemble does best are controlled by that choice:
13 |
14 | * Expert systems
15 | * Filling forms and templates (document assembly)
16 | * Referral and triage
17 | * Intake tools
18 | * Tickler/reminder systems
19 | * Gathering digital signatures, documents, or more from participants in litigation (i.e., collecting your client's documents that must be provided in discovery, getting a signature on a retainer or release, etc)
20 | * Database frontends (i.e., traditional create/read/update/delete systems)
21 |
22 | ## Examples
23 |
24 | Most expert systems built-on Docassemble also include filling forms and templates, but they don't need to.
25 |
26 | The [Court Forms Online](https://courtformsonline.org) site contains many examples
27 | of Docassemble interviews for use in Massachusetts.
28 |
29 | ## What are Docassemble's unique strengths?
30 |
31 | ### Customizability
32 | The greatest strength of Docassemble is the ability for Docassemble to talk to other existing systems. Because Docassemble is code based, you can easily add in new integrations without waiting for the platform author to add them.
33 |
34 | For example, document assembly has existed for decades. Docassemble makes it possible to have document assembly _with information pulled from a case management system_. Of course some platforms integrate with some case management systems. But Docassemble allows you to use any CMS that has a public API or whose database you can access. This may take time, but it's doable. This makes it safe to invest in Docassemble, without fear that the next system that comes along won't be supported.
35 |
36 | ### Working at scale
37 | Docassemble excels at the development of large, complex apps. While the drag-and-drop metaphor is great for infrequently updated and small, contained systems, larger apps have always been built with written code. Docassemble allows you to use traditional programming tools such as linters and code auto-completion while focusing on your core goal.
38 |
39 | Plain-text code can use `diff` to compare and track changes; easily be versioned; easily be searched and take advantage of code-folding and other techniques to provide an overview without requiring drilling down through hundreds of dialogs or menus. Using object-oriented techniques minimizes duplicate code; CSS and other web-development standbys allow you to manage and tweak the appearance of your system without making changes in hundreds of places for each tweak.
40 |
41 | ### Internationalization and accessibility
42 |
43 | Docassemble is a modern tool, built with multiple languages and accessibility for different levels of ability in mind from the beginning.
44 |
45 | A single Docassemble interview can easily be written in multiple languages. The default themes are designed to comply with the Americans with Disability Act / Web Content Accessibility Guidelines ([WCAG](https://en.wikipedia.org/wiki/Web_Content_Accessibility_Guidelines)). Most of the important elements use `aria` tags to aid screen readers. And it even includes a built-in screen reading tool and readability analysis scoring system.
46 |
47 | ### Built-in features
48 |
49 | Docassemble's built-in features could easily be dedicated tools in their own right. For example:
50 |
51 | * Collecting uploaded files from users
52 | * Optical character recognition
53 | * Digital signatures
54 | * Scheduled tasks that can run without your user being present, for things such as court date reminders
55 | * Integration with SMS and email
56 |
57 |
--------------------------------------------------------------------------------
/docs/project-planning/project-planning.md:
--------------------------------------------------------------------------------
1 | ---
2 | # slug: id
3 | # title:
4 | # sidebar_label:
5 | ---
6 | This is a stub
7 |
--------------------------------------------------------------------------------
/docs/prototyping/prototyping.md:
--------------------------------------------------------------------------------
1 | ---
2 | # slug: id
3 | # title:
4 | # sidebar_label:
5 | ---
6 | This is a stub
7 |
--------------------------------------------------------------------------------
/docs/stub.md:
--------------------------------------------------------------------------------
1 | ---
2 | # slug: id
3 | # title:
4 | # sidebar_label:
5 | ---
6 | This is a stub
7 |
--------------------------------------------------------------------------------
/docs/testing/lorem-ipsum.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: lorem-ipsum
3 | title: Lorem Ipsum text
4 | sidebar_label: Lorem Ipsum
5 | ---
6 |
7 | ## Lorem Ipsum
8 |
9 | [Lorem Ipsum](https://en.wikipedia.org/wiki/Lorem_ipsum) is dummy, or
10 | placeholder text, that looks realistic but doesn't distract you from the
11 | content on the screen.
12 |
13 | You can copy and paste the text below to test a form.
14 |
15 | ## Sample lorem ipsum text
16 |
17 | ```
18 | Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod
19 | tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At
20 | vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren,
21 | no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit
22 | amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut
23 | labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam
24 | et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata
25 | sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur
26 | sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore
27 | magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo
28 | dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est
29 | Lorem ipsum dolor sit amet.
30 |
31 | Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie
32 | consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan
33 | et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis
34 | dolore te feugait nulla facilisi. Lorem ipsum dolor sit amet, consectetuer
35 | adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna
36 | aliquam erat volutpat.
37 |
38 | Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit
39 | lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure
40 | dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore
41 | eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui
42 | blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla
43 | facilisi.
44 |
45 | Nam liber tempor cum soluta nobis eleifend option congue nihil imperdiet doming
46 | id quod mazim placerat facer possim assum. Lorem ipsum dolor sit amet,
47 | consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet
48 | dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud
49 | exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo
50 | consequat.
51 |
52 | Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie
53 | consequat, vel illum dolore eu feugiat nulla facilisis.
54 |
55 | At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd
56 | gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum
57 | dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor
58 | invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos
59 | et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea
60 | takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet,
61 | consetetur sadipscing elitr, At accusam aliquyam diam diam dolore dolores duo
62 | eirmod eos erat, et nonumy sed tempor et et invidunt justo labore Stet clita ea
63 | et gubergren, kasd magna no rebum. sanctus sea sed takimata ut vero voluptua.
64 | est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur
65 | sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore
66 | magna aliquyam erat.
67 |
68 | Consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore
69 | et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et
70 | justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata
71 | sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur
72 | sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore
73 | magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo
74 | dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est
75 | Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing
76 | elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna
77 | aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et
78 | ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum
79 | dolor sit amet.
80 | ```
--------------------------------------------------------------------------------
/docs/tutorials.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: tutorials
3 | title: List of Tutorials
4 | sidebar_label: Tutorials
5 | ---
6 |
7 | ## Tutorials for Beginners
8 |
9 | * [Hello, World](https://docassemble.org/docs/helloworld.html) (By Jonathan Pyle)
10 | * [Hello, World](https://gbls.github.io/docassemble-workinggroup/Skillshares/1.%20hello%2C%20world/presentation.html#slide1) (By Quinten Steenhuis)
11 | * [Legal Motion Tutorial](https://gblsma.github.io/docassemble-MotionTutorial/) (By Rina Padua and Quinten Steenhuis)
12 |
13 | ### Videos
14 | * [Sam Harden's Youtube Channel](https://www.youtube.com/channel/UCCFR4rpeXQIv2KwcvaPwweQ)
15 | * [Assembly Line Teaching Tuesdays](https://www.youtube.com/playlist?list=PLy6i9GFGw5GzXmwApG1UDSY6C3hV8TqH1)
16 |
17 | ## Annotated Examples
18 | * [6 sample projects](https://www.nonprofittechy.com/2019/02/26/a-legal-hackathon-toolkit/)
19 |
20 | ## Advanced
--------------------------------------------------------------------------------
/docs/user-centered-design/user-centered-design.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: user-centered-design
3 | title: User Centered Design
4 | sidebar_label: User Centered Design
5 | ---
6 |
7 | ## An introduction to User Centered Design
8 |
9 | The basic process of user centered design involves four phases:
10 |
11 | * Analyze: talk to users and discover their needs
12 | * Ideate: brainstorm solutions
13 | * Build: create a prototype (which may be low fidelity)
14 | * Test: test your assumptions about the prototype by observing real users.
15 |
16 | (repeat)
17 |
18 | The key is to focus on iteration: or creating small testable prototypes, testing, and incorporating feedback and lessons learned into an improved prototype.
19 |
20 | ## Further reading
21 |
22 | * [Making MADE: a discussion of a novice using user-centered design](https://law-tech-a2j.org/odr/made-in-boston-replicable-around-the-world/)
23 | * https://www.usability.gov/what-and-why/user-centered-design.html
24 | * https://www.interaction-design.org/literature/topics/user-centered-design
25 |
26 | ## Contributors and acknowledgments
27 |
28 | This article must also acknowledge the work of [Theory and Principle](https://www.theoryandprinciple.com/) who have contributed a great deal to thinking on this topic in the legal aid space. They have several great posts on [Medium](https://medium.com/theory-and-principle) about the topic.
--------------------------------------------------------------------------------
/docs/user-needs/user-needs.md:
--------------------------------------------------------------------------------
1 | ---
2 | # slug: id
3 | # title:
4 | # sidebar_label:
5 | ---
6 | This is a stub
7 |
--------------------------------------------------------------------------------
/docs/verification/verification.md:
--------------------------------------------------------------------------------
1 | ---
2 | # slug: id
3 | # title:
4 | # sidebar_label:
5 | ---
6 | This is a stub
7 |
--------------------------------------------------------------------------------
/package.json:
--------------------------------------------------------------------------------
1 | {
2 | "name": "open-class",
3 | "version": "0.0.0",
4 | "private": true,
5 | "scripts": {
6 | "start": "docusaurus start",
7 | "build": "docusaurus build",
8 | "swizzle": "docusaurus swizzle",
9 | "deploy": "docusaurus deploy"
10 | },
11 | "dependencies": {
12 | "@docusaurus/core": "^3.1.0",
13 | "@docusaurus/preset-classic": "^3.1.0",
14 | "@easyops-cn/docusaurus-search-local": "^0.44.3",
15 | "@lebalz/remark-admonitions": "^1.2.3",
16 | "classnames": "^2.2.6",
17 | "react": "^18.2.0",
18 | "react-dom": "^18.2.0",
19 | "remarkable-plantuml": "^1.1.0",
20 | "to-vfile": "^6.0.0"
21 | },
22 | "browserslist": {
23 | "production": [
24 | ">0.2%",
25 | "not dead",
26 | "not op_mini all"
27 | ],
28 | "development": [
29 | "last 1 chrome version",
30 | "last 1 firefox version",
31 | "last 1 safari version"
32 | ]
33 | }
34 | }
35 |
--------------------------------------------------------------------------------
/puppeteer-config.json:
--------------------------------------------------------------------------------
1 | {
2 | "args": ["--no-sandbox"]
3 | }
4 |
--------------------------------------------------------------------------------
/src/css/custom.css:
--------------------------------------------------------------------------------
1 | /**
2 | * Any CSS included here will be global. The classic template
3 | * bundles Infima by default. Infima is a CSS framework designed to
4 | * work well for content-centric websites.
5 | */
6 |
7 | /* You can override the default Infima variables here. */
8 | :root {
9 | --ifm-color-primary: #25c2a0;
10 | --ifm-color-primary-dark: rgb(33, 175, 144);
11 | --ifm-color-primary-darker: rgb(31, 165, 136);
12 | --ifm-color-primary-darkest: rgb(26, 136, 112);
13 | --ifm-color-primary-light: rgb(70, 203, 174);
14 | --ifm-color-primary-lighter: rgb(102, 212, 189);
15 | --ifm-color-primary-lightest: rgb(146, 224, 208);
16 | --ifm-code-font-size: 95%;
17 | }
18 |
19 | .docusaurus-highlight-code-line {
20 | background-color: rgb(72, 77, 91);
21 | display: block;
22 | margin: 0 calc(-1 * var(--ifm-pre-padding));
23 | padding: 0 var(--ifm-pre-padding);
24 | }
25 |
--------------------------------------------------------------------------------
/src/pages/index.js:
--------------------------------------------------------------------------------
1 | import React from 'react';
2 | import classnames from 'classnames';
3 | import Layout from '@theme/Layout';
4 | import Link from '@docusaurus/Link';
5 | import useDocusaurusContext from '@docusaurus/useDocusaurusContext';
6 | import useBaseUrl from '@docusaurus/useBaseUrl';
7 | import styles from './styles.module.css';
8 | import Head from '@docusaurus/Head';
9 | //import mermaid from "mermaid";
10 |
11 | //mermaid.initialize({
12 | // startOnLoad: true
13 | //});
14 |
15 | const features = [
16 | {
17 | title: <>Collaboratively built,
18 | imageUrl: 'img/group.svg',
19 | description: (
20 | <>
21 | This class has contributors from around the world.
22 | Learn more on our Github page.
23 |
24 | ),
25 | },
26 | {
27 | title: <>Practical education,
28 | imageUrl: 'img/work.svg',
29 | description: (
30 | <>
31 | Tools for doing. Exercises help you get started right away
32 | building legal technology with open-source tools.
33 |
34 | ),
35 | },
36 | {
37 | title: <>Theories and principles,
38 | imageUrl: 'img/mortarboard.svg',
39 | description: (
40 | <>
41 | Our class materials touch on theories and motivations for legal technology
42 | as well: including the access to justice gap, the future of the legal profession,
43 | and ethical issues.
44 |
45 | ),
46 | },
47 | ];
48 |
49 | function Feature({imageUrl, title, description}) {
50 | const imgUrl = useBaseUrl(imageUrl);
51 | return (
52 |
56 | {description}
60 |{siteConfig.tagline}
75 |