suffolklitlab/courtformsonline.org

Code for courtformsonline.org index of guided interviews. This replaces the "massaccess" repo

This is a Next.js project bootstrapped with create-next-app.

Getting Started

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.

This project uses next/font to automatically optimize and load Inter, a custom Google Font.

Form Sources Config

The formSources.config.js file allows new paths and server sources to be added to courtformsonline. There are two main components to this config file:

• pathToServerConfig: Maps paths to servers, which facilitates adding new paths or modifying existing connections to different servers.
• formSources: Contains the details of the servers, including URLs and names, used by the application.

Form source example

{ key: 'newServerKey', url: 'https://newserver.example.com', name: 'New Server Name', },

Path to server config example

yourPath: { path: 'yourPath', servers: ['New Server Name', 'Existing Server Name'], },

courtformsonline.org's Issues

Hamburger menu has transparent background on small and medium viewport sizes

Figure out best way to generate an index per-jurisdiction

Ultimately we want ma.courtformsonline.org, il.courtformsonline.org

But we need to make it clear that the content belongs to the author of the forms, not our website.

Make the cards on the landing page reflect the real list of interviews

Update cards to mimic Law Help New Mexico cards

User Story

As a stakeholder, I would like cards to go from this screenshot to this New Mexico screenshot.

---

Notes

1. See Quinten's previous recommendations in initial issue: #3

Come up with a consistent layout for the landing page for each interview

This doesn't have to be creative. Here are a few examples:

• https://www.illinoislegalaid.org/legal-information/divorce
• https://www.washingtonlawhelp.org/resource/parenting-plan-forms-online
• A simpler one: https://michiganlegalhelp.org/resources/housing/do-it-yourself-motion-set-aside-default-eviction

I like the balance set by ILAO personally.

I've added the metadata that the ILAO interview shows on the landing page here: SuffolkLITLab/docassemble-MA209AProtectiveOrder#104

Documentation of the /list?json=1 endpoint

https://docassemble.org/docs/config.html#dispatch

Fix rounding of 1 2 3 icons

Come up with a place to store a manually curated list of interviews and side-load it with real data

We want to get interview data from the /list endpoints on various Docassemble servers. But that will require editing each interview and adding the metadata.

It's probably helpful to come up with a shortcut before we get to that stage, since editing the metadata should probably also go along with testing each repo. That will take a fair amount of time to do. Maybe clinic students will be able to help.

See: https://github.com/SuffolkLITLab/massaccess/ and the Google Sheet that is pointed to in that repository as the source. We might want to write a quick script to get the data from Google Sheets and generate a JSON that looks like the output of /list (at least the keys we care about)

Navigate categories based on LIST

User Story

As a user, I would like to navigate the 20 top level categories (+Other) based on LIST (from the processed CSV) and not see empty categories that have no interviews.

---

Extend gray color all the way to the left

will need a new container for the left pane of the hero

Drive all data on the application from a docassemble JSON

User Story

As a stakeholder, I would like to drive all data on the application from this docassemble JSON.

---

Drive data on an interview card from a docassemble JSON

User Story

As a stakeholder, I would like to drive all data on an interview card from this docassemble JSON.

---

Linked Issues

Related: #8
Closed: #7

Concept for topic cards

1. Show the most popular topics and a "view all categories" button. 7+- 2 is the most we can show at the top level. (Note: in topics.config.ts, there's currently a priority field for this. higher priority = show it earlier in the list)
2. Consider showing a preview of the sub-topics within a top-level topic, with a "show more" button if there are more than 4 sub-topics.
3. Allow some room to change the most popular topics by language
4. Only show a top-level category if there's a form in that category.

Add some language: "don't see a form you wanted? let us know!"
Push people to the search interface / SPOT to try again to type their problem out.

On the category pages, we should show a "don't see the form you wanted? try searching"

Some kinds of forms, like "Divorce" aren't going to be pre-bundled. But we don't want to show 4 sub-items for divorce on the front card. Maybe use LIST taxonomy -- if there are multiple child items, take to a page. if there's only one matching child item

Some ideas to add illustrations on landing page

Let people indicate a canonical location for the main route that isn't on courtformsonline.org?

This is really just a question about whether the base_path is hardcoded anywhere

"Show all categories" should be expanded by default and look like a button

If there is anything in "Other", it should be shown. If we do end up somehow with too many top level categories, the "Show all" link should be a clear interactable element.

If the metadata key `unlisted` is `true`, don't publish a form on the site

There are a handful of interviews that we need to keep dispatch directives for, but that shouldn't appear live.

Here's an example: https://suffolklitlab.org/courtformsonline.org/ma/health

Should this repo be renamed to avoid URL issues with GitHub Pages (edit: and Google)?

I realize @jtmst is actively developing this repo, but this is probably related to the launch checklist. Currently this repo is publishing to GitHub Pages as suffolklitlab.org/courtformsonline.org. That's a goofy URL, but it's obviously not where the website will live.

If GitHub Pages is a necessary part of deployment, we might want to rename the repo because we are going to switch to using subdomains, and I don't think courtformsonline.org.suffolklitlab.org is a valid URL. If GitHub Pages is not necessary, it should probably be disabled.

Also pinging @nonprofittechy and @KindBill.

Breakpoint issue with the logo?

For interview forms, URL should default to start

Add new jurisdiction via configuration file

User Story

As a stakeholder, I would like to add a new jurisdiction, ex: Mass., via a configuration file that points to a JSON configuration file.

---

Copy over the Spot integration from the massaccess repo

Currently on CourtFormsOnline.org there's a JavaScript that interacts with Spot. We should replicate that on the new courtformsonline.org

Can copy from the massaccess repo?

Finish identifying the metadata we want to capture from an interview

• LIST_topics (should be either one topic, or a list of topics/categories from LIST)

See also:

SuffolkLITLab/docassemble-AssemblyLine#534