docs: Add ecosystem projects to the projects page by charlieforward9 · Pull Request #43 · openjs-foundation/open-visualization

charlieforward9 · 2026-02-20T10:45:58Z

Closes ubilabs/outlined-path-layer#12
Closes visgl/deck.gl-community#488
Closes visgl/deck.gl-community#495

@chrisgervang @kylebarron @ibgreen

Co-authored-by: charlieforward9 <62311337+charlieforward9@users.noreply.github.com>

…s-page Add ecosystem projects to the projects page

vercel · 2026-02-20T10:46:04Z

@charlieforward9 is attempting to deploy a commit to the OpenJS Foundation Team on Vercel.

A member of the Team first needs to authorize it.

…-layer to ecosystem Co-authored-by: charlieforward9 <62311337+charlieforward9@users.noreply.github.com>

…-links Add incomplete-module maintenance note and ubilabs outlined-path-layer to ecosystem

content/projects.json

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

ibgreen · 2026-03-01T16:51:23Z

content/projects.json

+          "category": "ecosystem",
+          "layout": "full",
+          "theme": "default",
+          "description": "An [awesome list](https://github.com/sindresorhus/awesome) of external projects that use or integrate with deck.gl. [Suggest a project](https://github.com/visgl/open-visualization/issues/new).",


I don't see anything deck related in the awsome link?

Fair, this isn't technically an "awesome list" which usually takes the form of a GitHub repo with a large README.

I think it'd be complementary to create one of these lists and link to it from here

ibgreen · 2026-03-01T16:52:59Z

content/projects.json

+              "description": "GPU-accelerated raster visualization layers for deck.gl."
+            },
+            {
+              "name": "@deck.gl-community/three",


Are other people able to publish under the @deck.gl-community namespace? This seems concerning.

Charles authored this module for the TreeLayer

Yes just realized I missed that, been too busy the last weeks.
Generally the concept of a THREE.js integration module could mean many things to different people and I think it is helpful if that we can clearly define the scope of it in the comment here. I have suggested we also refine the name, perhaps three-layers (if that is what it is, deck.gl layers implemented under the hood with THREE.js primitives)

ibgreen · 2026-03-01T16:53:57Z

content/projects.json

+              "description": "Unit visualization explorer by Microsoft, using deck.gl for rendering."
+            },
+            {
+              "name": "outlined-path-layer",


If we have integrated this in deck.gl-community and they are explicitly stating that they are no longer supporting it, I suggest we drop it here and instead add a note to their repo saying this has been migrated to deck.gl-community

I thought in the end they decided to stay separate since they may push updates after all

visgl/deck.gl-community#484 (review)

Regardless, I feel that a module that only contains one layer does not really rise to the level of meriting being included here. (Especially when it is already duplicated into community).

We are not trolling for things to add to our list, it is already long and impressive, and other entries are significantly more substantial.

It sounds like you’re approaching this from the perspective that the website should be selective about what’s included. I can definitely see the merit in that.

That said, when I suggested adding this list, my hope was to create a destination that could house any deck content - unofficial or official. To me, that’s the spirit of an "awesome" list: comprehensive and community-driven. That’s also why lists like this often live as large READMEs on GitHub rather than as curated entries on an official-looking site.

I'm curious what you all think about the repo/README direction to complement this website? We could link to it from our site and let it scale with the community

FWIW I think it would be valuable, somewhere to have a list in the style of Awesome lists that includes official, community, and external deck.gl resources on a single page.

With the feedback here and the absence of information on the current deck.gl-community README - thats the best augmentation of existing content - in the place that makes the most sense - given the expected format of most awesome lists.

I think it is fine to link to a raw github page that hosts an "awesome list" anyone can contribute to.
However, I personally feel that this is the official website and it should be "official".

For instance, a potential concern is that some of the projects referenced here may be stale, old or outdated - e.g. https://github.com/microsoft/SandDance/blob/main/package.json#L49

Along these lines there are some really cool examples out there such as Minecraft viewer on deck.gl v3 and Wind Demo which may be deck.gl v6 or v7, but it would seem inappropriated to list them here (admittedly they are more examples rather than libraries). In any event, many of them are already listed in the deck.gl showcases section that just links to their pre-built examples, that is the way we worked around the dated dependency problems before.

One day after another - I am baffled by the capabilities of deck.gl. This minecraft viewer is incredible.

Yes - my intention here is to close this PR and focus on investing more into the modules that deck.gl-community repo exposes, and related modules that external orgs want to retain.

See visgl/deck.gl-community#553

ibgreen · 2026-03-01T16:54:16Z

content/projects.json

+              "name": "@deck.gl-community/react",
+              "url": "https://visgl.github.io/deck.gl-community",
+              "image": "/visgl/images/frameworks/deck.gl-community.png",
+              "description": "React components for deck.gl."


Additional...

ibgreen · 2026-03-01T16:54:23Z

content/projects.json

+              "name": "@deck.gl-community/widgets",
+              "url": "https://visgl.github.io/deck.gl-community",
+              "image": "/visgl/images/frameworks/deck.gl-community.png",
+              "description": "UI widgets for deck.gl."


Additional...

ibgreen · 2026-03-01T16:55:27Z

content/projects.json

+          "description": "An [awesome list](https://github.com/sindresorhus/awesome) of external projects that use or integrate with deck.gl. [Suggest a project](https://github.com/visgl/open-visualization/issues/new).",
+          "entries": [
+            {
+              "name": "Viv",


Nit: I think having a separate section for "biomolecular visualizations" could be nice, and include this link there.

Once we get a bit further with https://github.com/Taylor-CCB-Group/SpatialData.js then that as well.

Copilot AI and others added 3 commits February 19, 2026 20:36

Initial plan

3a9f68c

Add ecosystem projects to the projects page

b253788

Co-authored-by: charlieforward9 <62311337+charlieforward9@users.noreply.github.com>

Merge pull request #1 from NEW-HEAT/copilot/apply-pr-ideas-to-project…

59b378e

…s-page Add ecosystem projects to the projects page

Copilot AI and others added 5 commits February 20, 2026 10:52

Initial plan

0cdf6e4

Add maintenance note for incomplete modules and ubilabs outlined-path…

3d07ac7

…-layer to ecosystem Co-authored-by: charlieforward9 <62311337+charlieforward9@users.noreply.github.com>

Apply suggestion from @charlieforward9

a311e73

Apply suggestion from @charlieforward9

aace01c

Merge pull request #2 from NEW-HEAT/copilot/add-maintenance-notes-and…

d72068b

…-links Add incomplete-module maintenance note and ubilabs outlined-path-layer to ecosystem

chrisgervang approved these changes Feb 20, 2026

View reviewed changes

charlieforward9 added 2 commits February 20, 2026 13:01

docs: add @deck.gl-community/three to Ecosystem layer packs

5cb982f

docs: restore formatting of projects.json

3702369

This comment was marked as resolved.

Sign in to view

kylebarron reviewed Feb 20, 2026

View reviewed changes

content/projects.json Show resolved Hide resolved

fix(content): restore pretty-printed formatting in projects.json

aa5a35f

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

ibgreen approved these changes Mar 1, 2026

View reviewed changes

charlieforward9 mentioned this pull request Mar 11, 2026

docs: rewrite README as focused awesome list visgl/deck.gl-community#553

Merged

3 tasks

charlieforward9 closed this Mar 11, 2026

Conversation

charlieforward9 commented Feb 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

vercel bot commented Feb 20, 2026

Uh oh!

This comment was marked as resolved.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

charlieforward9 commented Feb 20, 2026 •

edited

Loading