Monorepo merge

.firebaserc

@@ -0,0 +1,18 @@
+{
+  "projects": {
+    "default": "benefit-decision-toolkit-play"
+  },
+  "targets": {
+    "benefit-decision-toolkit-play": {
+      "hosting": {
+        "screener-frontend": [
+          "bdt-screener"
+        ],
+        "builder-frontend": [
+          "bdt-builder"
+        ]
+      }
+    }
+  },
+  "etags": {}
+}

.firebaserc.old.json

@@ -0,0 +1,18 @@
+{
+  "projects": {
+    "default": "benefits-decision-toolkit"
+  },
+  "targets": {
+    "benefits-decision-toolkit": {
+      "hosting": {
+        "screener-frontend": [
+          "benefits-decision-toolkit"
+        ],
+        "builder-frontend": [
+          "bdt-screener-builder"
+        ]
+      }
+    }
+  },
+  "etags": {}
+}

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @Michael-Dratch

.gitignore

@@ -1,5 +1,74 @@
-target/
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+firebase-debug.log*
+firebase-debug.*.log*
 
-thunder-tests/thunderResponses.json
-thunder-tests/res-files/
-thunder-tests/thunderActivity.json
+# Firebase cache
+.firebase/
+
+# Firebase config
+
+# Uncomment this if you'd like others to create their own Firebase project.
+# For a team working on the same Firebase project(s), it is recommended to leave
+# it commented so all members can deploy to the same project(s) in .firebaserc.
+# .firebaserc
+
+# Runtime data
+pids
+*.pid
+*.seed
+*.pid.lock
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Coverage directory used by tools like istanbul
+coverage
+
+# nyc test coverage
+.nyc_output
+
+# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
+.grunt
+
+# Bower dependency directory (https://bower.io/)
+bower_components
+
+# node-waf configuration
+.lock-wscript
+
+# Compiled binary addons (http://nodejs.org/api/addons.html)
+build/Release
+
+# Dependency directories
+node_modules/
+
+# Optional npm cache directory
+.npm
+
+# Optional eslint cache
+.eslintcache
+
+# Optional REPL history
+.node_repl_history
+
+# Output of 'npm pack'
+*.tgz
+
+# Yarn Integrity file
+.yarn-integrity
+
+# dotenv environment variables file
+.env
+
+# dataconnect generated files
+.dataconnect
+# IntelliJ
+.idea
+*.ipr
+*.iml
+*.iws

.idx/dev.nix

@@ -1,5 +1,5 @@
 # To learn more about how to use Nix to configure your environment
-# see: https://developers.google.com/idx/guides/customize-idx-env
+# see: https://firebase.google.com/docs/studio/customize-workspace
 { pkgs, ... }: {
   # Which nixpkgs channel to use.
   channel = "stable-24.05"; # or "unstable"
@@ -8,36 +8,21 @@
   packages = [
     pkgs.maven
     pkgs.quarkus
-    pkgs.jdk17
+    pkgs.jdk21
   ];
 
   # Sets environment variables in the workspace
-  env = {
-    # PORT = "8080";
-  };
+  env = {};
   idx = {
     # Search for the extensions you want on https://open-vsx.org/ and use "publisher.id"
     extensions = [
-      "jellydn.toggle-excluded-files"
-      "waderyan.gitblame"
-      "kie-group.dmn-vscode-extension"
-      "rangav.vscode-thunder-client"
-      "redhat.vscode-xml"
-      "mhutchie.git-graph"
-      "redhat.java"
-      "redhat.vscode-quarkus"
+      # "vscodevim.vim"
     ];
 
     # Enable previews
-    # previews = {
-    #   enable = true;
-    #   previews = {
-    #     web = {
-    #       command = [
-    #         "bin/dev"
-    #       ];
-    #       manager = "web";
-    #     };
+    previews = {
+      enable = true;
+      previews = {
         # web = {
         #   # Example: run "npm run dev" with PORT set to IDX's defined port for previews,
         #   # and show it in IDX's web preview panel
@@ -48,19 +33,20 @@
         #     PORT = "$PORT";
         #   };
         # };
-    #   };
-    # };
+      };
+    };
 
     # Workspace lifecycle hooks
     workspace = {
       # Runs when a workspace is first created
       onCreate = {
-        install-default-settings = "cp .idx/default-vscode-settings.jsonc /home/user/.codeoss-cloudworkstations/data/Machine/settings.json";
-        install-thunder-client-tests = "ln -s /home/user/dmn-benefit-toolbox/thunder-tests/ /home/user/.codeoss-cloudworkstations/data/User/globalStorage/rangav.vscode-thunder-client";
+        # Example: install JS dependencies from NPM
+        # npm-install = "npm install";
       };
       # Runs when the workspace is (re)started
       onStart = {
-        start-quarkus-dev-server = "bin/dev";
+        # Example: start a background task to watch and re-build backend code
+        # watch-backend = "npm run watch-backend";
       };
     };
   };

.idx/integrations.json

@@ -1,4 +1,7 @@
 {
+  "firebase_hosting": {
+    "deploymentHostingUrl": "https://benefit-decision-toolkit-play.web.app"
+  },
   "cloud_run_deploy": {
     "region": "us-east4",
     "sourceFlag": "--source .",

README.md

@@ -1,119 +1,3 @@
-# Benefit Decision Toolkit
+### Benefits Decision Toolkit Web App
 
-**Use [DMN](https://www.omg.org/dmn/) and [FEEL](https://docs.camunda.io/docs/components/modeler/feel/what-is-feel/) to create APIs and Screeners for public benefit rules.**
-
-## Motivation
-
-Why hire a team of software engineers to codify rules that your benefit experts already know inside and out?
-
-Why design a screening tool from scratch when your goal is simply to deploy a functionally accurate service as quickly as possible?
-
-***Benefit Decision Toolkit simplifies the management of eligibility rules and screeners so motivated subject matter experts can create useful tools with less hand-holding from traditional software teams.***
-
-## Examples
-
-### The Philly Property Tax Relief Screener
-
-As a proof of concept, we've built a screener for several of the [tax relief benefits available in Philadelphia](https://www.phila.gov/services/payments-assistance-taxes/taxes/property-and-real-estate-taxes/get-real-estate-tax-relief/).
-
-You can interact with the screener yourself at: https://phillypropertytaxrelief.org.
-
-### JSON ("REST") API
-
-A JSON API is generated from the eligibility rules created in DMN/FEEL. You can interact with the endpoints of this API at: https://phillypropertytaxrelief.org/q/swagger-ui/
-
-## Setup a Development Environment
-
-Since the ultimate goal of this project is to enable a development environment that is accessible to those without a software engineering background, we are intrigued by tools like [Firebase Studio](https://firebase.google.com/docs/studio) as a precursor/mockup for a more specialized service that we'd like to build (eventually).
-
-With Firebase Studio, the environment is in the cloud, and can be accessed from any computer without any manual setup.
-
-If you're an experienced engineer, however, you may want to skip Firebase Studio in favor of your own preferred setup. (Up to you.)
-
-### Use Firebase Studio (simplest)
-
-The easiest way to get a feel for Benefit Decision Toolkit is to [fork this repo*](https://github.com/CodeForPhilly/benefit-decision-toolkit/fork) and then open it (from the fork!) in Firebase Studio:
-
-<a href="https://studio.firebase.google.com/import?url=https%3A%2F%2Fgithub.com%2FCodeForPhilly%2Fbenefit-decision-toolkit">
-  <picture>
-    <source
-      media="(prefers-color-scheme: dark)"
-      srcset="https://cdn.firebasestudio.dev/btn/open_dark_32.svg">
-    <source
-      media="(prefers-color-scheme: light)"
-      srcset="https://cdn.firebasestudio.dev/btn/open_light_32.svg">
-    <img
-      height="32"
-      alt="Open in Firebase Studio"
-      src="https://cdn.firebasestudio.dev/btn/open_blue_32.svg">
-  </picture>
-</a>
-
-When you open Benefit Decision Toolkit in Firebase Studio, a development machine will be created and configured for you in the cloud. (This will take a few minutes.)
-
-After the first time you open the project, you can just return to https://studio.firebase.google.com   to pick up where you left off.
-
-_*Note on forking: you can skip this step if you are just curious or otherwise don't intend to contribute changes back to the project._
-
-### Use Devbox (medium simple)
-
-The second easiest way to get started is to [fork this repo*](https://github.com/CodeForPhilly/benefit-decision-toolkit/fork), clone it to your local machine, and use the included Devbox configuration:
-
-[![Built with Devbox](https://www.jetify.com/img/devbox/shield_galaxy.svg)](https://www.jetify.com/devbox/docs/contributor-quickstart/)
-
-[Devbox](https://www.jetify.com/devbox) is a way to create isolated development environments on your own machine.
-
-We're experimenting w/ Devbox for the same reason we're experimenting w/ Firebase Studio; we're interested in how this approach to managing development environments could form the basis of some future specialized/packaged toolkit.
-
-### Roll your own (for experienced developers)
-
-Of course, you can also manually setup a laptop/desktop to work on Benefit Decision Toolkit, but it isn't recommended unless you really know what you're doing.
-
-### Additional setup notes
-
-#### Forms development
-
-If you're planning to develop forms (the basis of eligibility screeners) in addition to eligibility rules, then you'll also need to download [Camunda Modeler](https://camunda.com/download/modeler/).
-
-#### Kicking the tires and testing your work
-
-You can run `bin/dev`* from a terminal to start the Quarkus development server. This will serve the API and any existing eligibility screeners from `https://localhost:8080`**.
-
-*_If you are using Firebase Studio the Quarkus dev server should automatically start when you load the workspace._
-
-**_Since Firebase Studio is a browser-based environment, the system will map the URL for the dev server to an address you can reach from a browser in your local machine. You can access this address by clicking on the Firebase Studio logo in the left sidebar, then clicking into the "Backend Ports" panel._
-
-<img src="docs/images/backend-ports.png" width=600 alt="Screenshot of Backend Ports list in Firebase Studio">
-
-## Technologies overview
-
-We use a combination of open-source tools ([Kogito](https://kogito.kie.org/) and [form-js](https://bpmn.io/toolkit/form-js/)) with some scaffolding to tie them together and make them easier to use.
-
-Here are some high-level things to orient you...
-
-### DMN Files
-
-DMN files (`.dmn`) can be edited directly in VS Code via the [DMN Editor extension](https://marketplace.visualstudio.com/items?itemName=kie-group.dmn-vscode-extension). If you're using Firebase Studio as described above, then this extension is already installed for you. If you're using another dev environment, then you'll need to install the extension manually.
-
-You may occasionally need to interact with the raw XML text of the DMN; this can be done via the "Reopen with Text Editor" feature of VS Code.
-
-A good orientation on the basics of DMN can be found [here](https://learn-dmn-in-15-minutes.com/).
-
-In this project, DMN (and its accompanying expression language FEEL) acts as the "source code" for a JSON web API. Kogito generates this API (with Java) when you run the Quarkus development server (automatic with Firebase Studio, or by running the `bin/dev` script).
-
-### Form Files
-
-Form files (`.form`) can be edited using [Camunda Modeler](https://camunda.com/download/modeler/). The modeler provides a UI for designing the form's layout and logic (which often incorporates FEEL expressions).
-
-Behind the scenes,the form is saved in JSON format.
-
-When it comes time to use the form in a screener, form-js interprets this JSON and uses it to display the form on a web page.
-
-### Eligibility Screeners
-
-To create the [Philadelphia Property Tax Relief Screener](https://phillypropertytaxrelief.org), we've written a [Qute template](https://quarkus.io/guides/qute) which displays the form, posts data as it is collected to the eligibility API (the one that is built from the DMN), and receives back eligibility results for display on the form.
-
-For future screeners, we envision packaging up this functionality somehow, allowing the entire screening and results process to be included as part of other websites and tools, the content of which is outside the scope of this project.
-
-## License
-See the [LICENSE](https://github.com/CodeForPhilly/benefit-decision-toolkit/blob/main/LICENSE.md) file for license rights and limitations (MIT).
+Welcome to the BDT Web App! The BDT Web App is a project focusing on building a cloud-based platform that makes it easy to build, test, and share benefit eligibility screeners.

builder-api/.dockerignore

@@ -0,0 +1,5 @@
+*
+!target/*-runner
+!target/*-runner.jar
+!target/lib/*
+!target/quarkus-app/*