Merge 5 17 26 (#159)

Author: JohnDamilola

.gitignore

@@ -39,4 +39,4 @@ learning_observer/learning_observer/static_data/google/
 learning_observer/learning_observer/static_data/admins.yaml
 .ipynb_checkpoints/
 .eggs/
-.next/
+.next/

Dockerfile

@@ -2,6 +2,15 @@ FROM python:3.10
 RUN git config --global --add safe.directory /app
 WORKDIR /app
 
+# Future work:
+# - This image currently uses an older Python base image version.
+# - Update the Python version to align with current LO/WO support targets.
+# - Some configurations may also require extra roster files mounted/provided
+#   at runtime (for example: admins.yaml or teachers.yaml).
+# - Consider a layered setup:
+#   1) maintain a shared "base LO" Docker image
+#   2) extend it with a WO-specific image (or other module-set images)
+
 # TODO start redis in here
 # see about docker loopback
 RUN apt-get update && \

Makefile

@@ -46,8 +46,8 @@ install: install-pre-commit-hook
 	# recent version. We would like to directly fetch `lodrc-current`,
 	# however, the fetch only returns the name of the file it's
 	# linked to. We do an additional fetch for the linked file.
-	@LODRC_CURRENT=$$(curl -s https://raw.githubusercontent.com/ETS-Next-Gen/lo_assets/main/lo_dash_react_components/lo_dash_react_components-current.tar.gz); \
-	pip install https://raw.githubusercontent.com/ETS-Next-Gen/lo_assets/main/lo_dash_react_components/$${LODRC_CURRENT}
+	@LODRC_CURRENT=$$(curl -s https://raw.githubusercontent.com/ArgLab/lo_assets/main/lo_dash_react_components/lo_dash_react_components-current.tar.gz); \
+	pip install https://raw.githubusercontent.com/ArgLab/lo_assets/main/lo_dash_react_components/$${LODRC_CURRENT}
 
 install-dev:
 	# TODO create a dev requirements file

README.md

@@ -7,7 +7,7 @@ learning analytics dashboard to help instructors be able to manage
 student learning processes, and in particular, student writing
 processes.
 
-![linting](https://github.com/ETS-Next-Gen/writing_observer/actions/workflows/pycodestyle.yml/badge.svg)
+![linting](https://github.com/ArgLab/writing_observer/actions/workflows/pycodestyle.yml/badge.svg)
 
 ## Learning Observer
 
@@ -17,6 +17,14 @@ per-student writing data, and aggegators to make dashboards. We've
 tested this in math and writing, but our focus is on writing process
 data.
 
+At a high level, Learning Observer functions as an application platform.
+The primary `learning_observer` module bootstraps the system: it loads
+configuration, connects to storage and messaging back ends, and brokers
+communication with data sources. Other modules plug into that
+infrastructure to define the specific reducers, dashboards, and other
+items that users interact with, letting teams experiment with new
+features without having to reimplement the platform core.
+
 It's not finished, but it's moving along quickly.
 
 ## Writing Observer
@@ -54,9 +62,10 @@ that the core approach and APIs are correct.
 
 ## Getting Started
 
-We have a short guide to [getting started](docs/workshop.md). Getting
-the base system working is pretty easy. The guide is pretty
-comprehensive (including how to develop your first module).
+We have a short guide to [installing the system](docs/tutorials/install.md).
+Getting the base system working is pretty easy. To create a new module
+for the system to use, check out our [cookiecutter module guide](docs/tutorials/cookiecutter-module.md).
+For a current package/module overview, see the [module inventory](docs/reference/module_inventory.md).
 
 ### System requirements
 

VERSION

@@ -1 +1 @@
-0.1.0+2025.10.01T21.16.15.146Z.8b205d0c.master
+0.1.0+2026.06.08T14.57.09.3NZ.c99f98d.refactor.portfolio.diff

autodocs/how-to.rst

@@ -4,22 +4,29 @@ How-to
 Practical instructions for achieving specific goals within Learning Observer. Use these guides when you know what outcome you need and want a proven recipe to follow:
 
 - :doc:`Communication Protocol <docs/how-to/communication_protocol>` - How to query data from reducers or system endpoints for dashboards.
-- :doc:`Configure Learning Observer <docs/how-to/config>` - Set up credentials, environment variables, and other configuration details required for a smooth deployment.
 - :doc:`Build Dashboards <docs/how-to/dashboards>` - Walk through creating dashboards from reducer outputs, including layout choices and data wiring.
-- :doc:`LTI <docs/how-to/lti>` - Cover how to install Learning Observer as an LTI application.
+- :doc:`Offline Reducer Replay <docs/how-to/offline_replay>` - Explain how to repopulate reducer content with study logs.
+- :doc:`Serve as LTI application<docs/how-to/lti>` - Cover how to install Learning Observer as an LTI application.
+- :doc:`Connect LO Blocks to Canvas via Learning Observer<docs/how-to/connect_lo_blocks_to_canvas>` - Show how to connect launch LO Blocks through Learning Observer from within Canvas.
+- :doc:`Configure Multiple Roster Sources<docs/how-to/multiple_roster_sources>` - Allow the system to dynamically choose a roster source given a user's context.
 - :doc:`Run with Docker <docs/how-to/docker>` - Learn how to containerize the stack, manage images, and operate the project using Docker Compose.
 - :doc:`Writing Observer Extension <docs/how-to/extension>` - Install, configure, and validate the Writing Observer browser extension for capturing events.
 - :doc:`Interactive Environments <docs/how-to/interactive_environments>` - Connect Learning Observer to Jupyter and other live coding setups for iterative development.
+- :doc:`Impersonate Users <docs/how-to/impersonation>` - Start and stop acting as another user while keeping dashboards informed.
+
 
 .. toctree::
    :hidden:
    :maxdepth: 1
    :titlesonly:
 
    docs/how-to/communication_protocol.md
-   docs/how-to/config.md
    docs/how-to/dashboards.md
+   docs/how-to/offline_replay.md
    docs/how-to/lti.md
+   docs/how-to/connect_lo_blocks_to_canvas.md
+   docs/how-to/multiple_roster_sources.md
    docs/how-to/docker.md
    docs/how-to/extension.md
    docs/how-to/interactive_environments.md
+   docs/how-to/impersonation.md

autodocs/index.rst

@@ -12,6 +12,12 @@ per-student writing data, and aggegators to make dashboards. We've
 tested this in math and writing, but our focus is on writing process
 data.
 
+At a high level, Learning Observer operates as an application platform:
+the core :mod:`learning_observer` package boots the system, loads
+configured modules, and manages shared data services, while each module
+provides the specific dashboards, reducers, and other artifacts that
+users interact with.
+
 Our documentation is organized into four main categories, each serving a different purpose. You can explore them below:
 
 - :doc:`Tutorials <tutorials>` - Step-by-step guides to help you learn by doing.

autodocs/reference.rst

@@ -9,6 +9,8 @@ Detailed, structured information about APIs, configurations, and technical detai
 - :doc:`Linting Rules <docs/reference/linting>` - Review the automated checks that keep the codebase healthy and how to run them locally.
 - :doc:`Testing Strategy <docs/reference/testing>` - Explore the testing layers we rely on and guidelines for writing reliable tests.
 - :doc:`Versioning and Releases <docs/reference/versioning>` - See how we tag releases, manage dependencies, and maintain backward compatibility.
+- :doc:`lo_assets Built Packages <docs/reference/lo_assets>` - Understand how prebuilt package artifacts are published and consumed.
+- :doc:`Module Inventory <docs/reference/module_inventory>` - Get a quick at-a-glance list of current monorepo modules and their roles.
 - :doc:`Module Reference <modules>` - Dive into the autogenerated API reference for Python modules within Learning Observer.
 - :doc:`API Reference <api>` - Inspect the internal functionality of the system.
 
@@ -23,5 +25,7 @@ Detailed, structured information about APIs, configurations, and technical detai
    docs/reference/linting.md
    docs/reference/testing.md
    docs/reference/versioning.md
+   docs/reference/lo_assets.md
+   docs/reference/module_inventory.md
    modules
    api

devops/README.md

@@ -10,4 +10,65 @@ We would like to be cross-platform, and evenually support both
 Debian-based distros and RPM-based distros. We're not there yet
 either. We'd also like to support multiple cloud providers. We're not
 there yet either. However, we probably won't accept PRs which move us
-away from this goal.
+away from this goal.
+
+## Create an AWS account and an EC2 instance.
+* Select Ubuntu, nano AMI. The cost should be 0.5 cents per hour.
+* In security groups, add HTTP, HTTPS rules. Open up only to your computer's IP address (the client).
+* Launch instance.
+* Suppose your instance public DNS is {ec2_ip}, e.g., ec2-18-223-122-172.us-east-2.compute.amazonaws.com.
+* Create aSSH key pair, save PEM file say under ~/.ssh, chmod to u+r.
+
+## Set up the EC2 instance.
+* SSH into the machine: `bash ssh -i {pem_file} ubuntu@{ec2_ip}`.
+* (Optional) Create a user account: sudo useradd {user}
+* Download the server code (same repository as the extension):
+```bash
+cd
+git clone https://github.com/ETS-Next-Gen/writing_analysis.git writing_analysis
+```
+* Install Ansible.
+```bash
+sudo apt-get update
+sudo apt-get upgrade
+sudo apt-get install ansible
+````
+* Configure Ansible.
+sudo pico /etc/ansible/hosts
+Add
+```
+[localhost]
+127.0.0.1
+```
+* `cd ~/writing_analysis/configuration`.
+* Run `sudo ansible-playbook local.yaml`. This may take a while on an EC2 nanon machine.
+If all goes well, you should see an output with no errors, like this:
+```
+bash
+...
+PLAY RECAP ******************************************************************************************
+127.0.0.1                  : ok=5    changed=4    unreachable=0    failed=0   
+```
+* Navigate to http://{ec2_ip}; you should see the message "Welcome to nginx!" if it's working.
+
+## Obtain a free domain name
+* Go to noip.com.
+* Sign up 
+
+## Obtain a free SSL Certificate Using Certbot
+* Run the following commands:
+```bash
+sudo apt-get install software-properties-common
+Sudo add-apt-repository universe
+sudo add-apt-repository ppa:certbot/certbot
+sudo apt-get update
+sudo apt-get install certbot python-certbot-nginx
+```
+```
+bash
+sudo certbot --nginx
+```
+-- Put in your {mydomain}.hopto.org address.
+-- Choose 1 - no redirect.
+
+## Stand up a backend server on the EC2 instance.

devops/tasks/remote_scripts/gitpaths.py

@@ -10,7 +10,7 @@ def gitpath_to_name(packagepath):
     '''
     Convert a git path to the name of the repo. For example:
 
-    `https://github.com/ETS-Next-Gen/writing_observer.git` ==> `writing_observer`
+    `https://github.com/ArgLab/writing_observer.git` ==> `writing_observer`
     '''
     package = os.path.split(packagepath)[1]
     if package.endswith(".git"):