updating?

.codecov.yml

@@ -0,0 +1,5 @@
+codecov:
+  coverage:
+    precision: 1
+    round: up
+

.eslintignore

@@ -0,0 +1,4 @@
+dist/
+config/
+coverage/
+styles/

.eslintrc

@@ -1,16 +1,99 @@
 {
-  "extends": "airbnb-base/legacy",
+  "parserOptions": {
+    "ecmaVersion": 2022,
+    "sourceType": "module",
+    "ecmaFeatures": {
+      "jsx": true
+    }
+  },
+  "extends": [
+    "airbnb",
+    "plugin:react/recommended",
+    "plugin:react-hooks/recommended",
+    "plugin:testing-library/react"
+  ],
   "globals": {
-    "Mirador": true,
-    "jQuery": true
+    "page": true,
+    "document": true,
+    "vi": true
   },
+  "plugins": [
+    "react", 
+    "react-hooks",
+    "testing-library"
+  ],
   "rules": {
-    "no-param-reassign": [
-      2, {
-        "props": true,
-        "ignorePropertyModificationsFor": [
-          "$"
-        ]
+    "import/no-unresolved": [
+      2, { "ignore": ["test-utils"] }
+    ],
+    "import/prefer-default-export": "off",
+    "no-console": "off",
+    "no-unused-expressions": ["error", { "allowShortCircuit": true, "allowTernary": true }],
+    "no-unused-vars": "off",
+    "no-undef": "off",
+    "no-restricted-syntax": ["warn", "WithStatement"],
+    "no-restricted-globals": ["error"],
+    "eqeqeq": ["warn", "smart"],
+    "no-use-before-define": [
+      "warn",
+      {
+        "functions": false,
+        "classes": false,
+        "variables": false
+      },
+    ],
+    "no-mixed-operators": [
+      "warn",
+      {
+        "groups": [
+          ["&", "|", "^", "~", "<<", ">>", ">>>"],
+          ["==", "!=", "===", "!==", ">", ">=", "<", "<="],
+          ["&&", "||"],
+          ["in", "instanceof"],
+        ],
+        "allowSamePrecedence": false,
+      },
+    ],
+    "react/jsx-filename-extension": [1, { "extensions": [".js", ".jsx"] }],
+    "require-jsdoc": ["error", {
+      "require": {
+        "FunctionDeclaration": true,
+        "MethodDefinition": true,
+        "ClassDeclaration": true,
+        "ArrowFunctionExpression": true,
+        "FunctionExpression": true
+      }
+    }],
+    "no-underscore-dangle": "off",
+    "react/prefer-stateless-function": "off",
+    "sort-keys": ["error", "asc", {
+      "caseSensitive": false,
+      "natural": false
+    }],
+    "react/jsx-props-no-spreading": "off",
+    "react/function-component-definition": "off",
+    "default-param-last": "off",
+    "arrow-parens": "off",
+    "import/no-anonymous-default-export": "off",
+    "import/no-extraneous-dependencies": "off",
+    "max-len": ["error", {
+      "code": 120,
+      "ignoreComments": true,
+      "ignoreStrings": true,
+      "ignoreTemplateLiterals": true,
+      "ignoreRegExpLiterals": true
+    }],
+    "react/jsx-uses-react": "off",
+    "react/react-in-jsx-scope": "off",
+    "react/require-default-props": [2, {
+      "functions": "defaultArguments"
+    }],
+    "react-hooks/exhaustive-deps": "error",
+    "testing-library/render-result-naming-convention": "off",
+    "testing-library/no-render-in-lifecycle": [
+      "error",
+      {
+        "allowTestingFrameworkSetupHook": "beforeEach"
       }
     ]
   }

.github/ISSUE_TEMPLATE/annotations.md

@@ -0,0 +1,13 @@
+---
+name: Annotations
+about: Issues related to annotation viewing / rendering in Mirador 3. Issues related to annotation creation can be filed in ProjectMirador/mirador-annotations.
+title: ''
+labels: Mirador3, annotations
+assignees: ''
+
+---
+
+<!--- Annotation compatibility support: https://github.com/ProjectMirador/mirador/wiki/Annotation-compatibility-support -->
+<!--- Annotation creation tools plugin: https://github.com/projectmirador/mirador-annotations -->
+
+Manifest URLs:

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/installing-mirador.md

@@ -0,0 +1,11 @@
+---
+name: Installing Mirador
+about: Issues related to installing / embedding Mirador in your application
+title: ''
+labels: Mirador3, embed
+assignees: ''
+
+---
+
+<!--- See "Embedding Mirador" in the wiki: https://github.com/ProjectMirador/mirador/wiki/M3-Embedding-in-Another-Environment -->
+  - Mirador version (release, commit, etc.):

.github/ISSUE_TEMPLATE/manifest-compatibility.md

@@ -0,0 +1,21 @@
+---
+name: Manifest / Image not loading
+about: Report examples of manifests or images that are not loading or displaying as
+  expected
+title: ''
+labels: Mirador3, manifest compatibility
+assignees: ''
+
+---
+
+- I am the author or maintainer of this manifest: Yes or No
+- URL: <!--- insert manifest URL here -->
+- Manifest hosting institution <!--- e.g. Smithsonian, Bodleian Library -->
+
+### Observed behavior
+- Description: (Example: I was able to load my manifest via the "Add Resource" button but thumbnails are not loading in Gallery view)
+- Screenshots / screen recordings / GIFs
+- Errors or warnings from the UI, developer console, or the [IIIF Presentation Validator](https://iiif.io/api/presentation/validator/service/)
+```
+Paste errors here if needed, otherwise delete
+```

.github/ISSUE_TEMPLATE/misc.md

@@ -0,0 +1,10 @@
+---
+name: Miscellaneous
+about: If your issue doesn't fit the other categories, use this one!
+title: ''
+labels: Mirador3
+assignees: ''
+
+---
+
+<!--- Add manifest URLs or screenshots if relevant -->

.github/ISSUE_TEMPLATE/plugins.md

@@ -0,0 +1,13 @@
+---
+name: Plugins
+about: Issues, questions, and proposals for customizing Mirador.
+title: ''
+labels: Mirador3, Plugins 🔌
+assignees: ''
+
+---
+
+<!--- See examples of Mirador 3 plugins on the wiki: https://github.com/ProjectMirador/mirador/wiki/Mirador-3-plugins -->
+- Mirador version (release or commit):
+- Description of use case:
+- Include screenshots, designs, etc. if relevant

.github/ISSUE_TEMPLATE/requested-settings.md

@@ -0,0 +1,13 @@
+---
+name: Requested setting
+about: Propose new options for Mirador’s out-of-the-box settings. See examples in src/config/settings.js
+title: 'Requested setting'
+labels: Mirador3, requested setting
+assignees: ''
+
+---
+
+<!--- See examples of settings at: https://github.com/ProjectMirador/mirador/blob/b15cbb61a7b60118b50469675d66e672748cb39e/src/config/settings.js#L252 -->
+- Manifest URLs (if any):
+- Screenshots of desired behavior
+- Description of desired behavior, suggested options for settings

.github/ISSUE_TEMPLATE/ui-ux.md

@@ -0,0 +1,8 @@
+---
+name: UI / UX
+about: Feedback on Mirador’s user interface / user experience. User stories for enhancements and new features
+title: ''
+labels: Mirador3, user experience
+assignees: ''
+
+---

.github/workflows/node.js.yml

@@ -0,0 +1,30 @@
+# This workflow will do a clean install of node dependencies, build the source code and run tests across different versions of node
+# For more information see: https://help.github.com/actions/language-and-framework-guides/using-nodejs-with-github-actions
+
+name: Node.js CI
+
+on:
+  push:
+    branches: [ master ]
+  pull_request:
+    branches: [ master ]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        node-version: [18.x, 20.x, 22.x]
+
+    steps:
+    - uses: actions/checkout@v4
+    - name: Use Node.js ${{ matrix.node-version }}
+      uses: actions/setup-node@v4
+      with:
+        node-version: ${{ matrix.node-version }}
+    - run: npm install
+    - run: npm test -- --coverage
+    - name: Upload coverage to Codecov
+      uses: codecov/codecov-action@v5
+      env:
+        CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}

.gitignore

@@ -1,17 +1,6 @@
-.grunt/
-_SpecRunner.html
-bkp
-css/discovery.css
-css/mirador.css
-dev.html
-discovery.html
-js/discovery
-node_modules/
-npm-debug.log
+dist/
 coverage/
-data/ecodices
-data/BnF
-data/Harvard
-build/
-.idea/
-bower_components/
+node_modules/
+package-lock.json
+*.log
+*.tgz

CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Mirador  Code of Conduct
+
+The [IIIF Code of Conduct](https://iiif.io/event/conduct/) guides our behavior as members of the IIIF Community in any forum, including remote and in-person meetings and events, email lists, Slack, GitHub, social media, and private correspondence related to IIIF and the Mirador project. IIIF is an inclusive and safe community, committed to openness and transparency in all interactions and activities. To reflect these commitments, we agree to operate according to the following standards.
+
+> **Note:** Please visit the [IIIF Code of Conduct](https://iiif.io/event/conduct/) page for the complete and current standards, which includes additional details regarding the process for evaluating Code of Conduct reports, the appeals process, and the IIIF Code of Conduct Team involved in these activities.
+
+
+ - [Community Ideals](#community-ideals)
+	 - [Inclusivity](#inclusivity)
+	 - [Collaboration](#collaboration)
+	 - [Respect](#respect)
+	 - [Greater Good](#greater-good)
+ - [Unacceptable Behaviors](#unacceptable-behaviors)
+ - [Reporting Harassment](#reporting-harassment)
+ - [Project Maintainer Enforcement Responsibilities](#project-maintainer-enforcement-responsibilities)
+ - [Acknowledgements](#acknowledgements)
+
+
+## Community Ideals
+
+### Inclusivity 
+We believe everyone is a valuable contributor to the community regardless of physical or intellectual ability, gender, sexual orientation, physical appearance, race, religion, nationality, language, employment source or status, financial ability, and any other facets of community dynamics not mentioned here. While the community primarily communicates in English at this point, we recognize that it is not the native language for many in the community and strive to express ourselves simply and clearly. We provide opportunities for participation despite challenges of ability, time, geography, finances, etc.
+
+### Collaboration
+
+We collaborate to share the community’s workload and to ensure a variety of needs and voices are accounted for. We do our work as transparently as possible, establishing guidelines for contributing and sharing current and historical community information openly, and welcome new collaborators with enthusiasm.
+
+### Respect
+
+The IIIF community is respectful of and open to differing opinions, viewpoints, experiences, and backgrounds. When we make a mistake we accept responsibility, apologize, and learn from the experience. We give and gracefully accept constructive feedback.
+
+### Greater Good
+
+We do work that benefits the community. We notice, call attention to, and help resolve potential problems. Community members should model good behavior and feel empowered to be [active bystanders](https://www.diglib.org/active-bystander-orientation/) to call out improper behavior and step in to help resolve issues without waiting to escalate to a higher power.
+
+
+## Unacceptable Behaviors
+
+Participants asked by anyone to stop any harassing behavior must comply immediately. Participants who violate these guidelines by behaving in the following ways will be notified and asked to change their behavior.
+
+-   Physical or verbal harassment or threats directed against another person or group of people
+-   Offensive verbal comments, insults, or jokes related to physical or intellectual ability, gender, sexual orientation, disability, physical appearance, body size, race, religion, etc.
+-   Sexual harassment, including inappropriate or unwanted physical contact, use of sexualized language or imagery, and sexual attention or advances of any kind
+-   Intentional provocation, insulting or derogatory comments, and personal or political attacks
+-   Publishing or threatening to publish others’ private information without their explicit permission
+-   Other conduct which could reasonably be considered inappropriate in a professional setting
+-   Advocating for or encouraging any of the above
+
+## Reporting Harassment
+
+If you believe anyone is in physical danger, please notify appropriate law enforcement first.
+
+If you are subject to or witness harassment, please contact the Code of Conduct committee at [[email protected]](mailto:[email protected]), or individually at in-person events where committee members or event-specific contacts will be identified by badges and introductions at the beginning of the event.
+
+**Written or verbal Code of Conduct reports should include the following information:**
+-   Your contact information
+-   Names (real, nicknames, or pseudonyms) of individuals involved and witnesses
+-   When and where the incident occurred (please be as specific as possible)
+-   Your account of what occurred. If there is a record available (e.g. a mailing list archive or messages in a Slack channel) please include a link or screenshot.
+-   If you believe this incident is or may be ongoing
+
+You will receive an email or verbal confirmation that your report has been received. Within one week you will receive a resolution and course of action or explanation of why the situation is unresolved and continues to be evaluated.
+
+## Project Maintainer Enforcement Responsibilities
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct.
+
+## Acknowledgements
+
+The IIIF Code of Conduct is modeled on examples from [Contributor Covenant](https://www.contributor-covenant.org/version/2/0/code_of_conduct/), [Django](https://www.djangoproject.com/conduct/), [the Digital Library Federation (DLF)](https://www.diglib.org/about/code-of-conduct/), [Islandora](https://www.islandora.ca/code-of-conduct), [Samvera](https://wiki.duraspace.org/display/samvera/Code+of+Conduct), and [DuraSpace](https://duraspace.org/about/policies/code-of-conduct/#:~:text=All%20communication%20will%20be%20treated,exclusionary%20behavior%20in%20any%20form.).
+
+Project maintainer enforcement responsibilities are modeled on the [Contributor Covenant](https://www.contributor-covenant.org/version/2/0/code_of_conduct/).
+
+The IIIF Code of Conduct is licensed under a [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0/).