docs: Add ecosystem projects to the projects page #43
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -110,6 +110,24 @@ | |
| "url": "https://visgl.github.io/deck.gl-community", | ||
| "image": "https://images.prismic.io/open-visualization/Z1s945bqstJ98bvz_arrow-logo-hex.png?auto=format,compress", | ||
| "description": "Arrow visualization layers for deck.gl." | ||
| }, | ||
| { | ||
| "name": "@deck.gl-community/layers", | ||
| "url": "https://visgl.github.io/deck.gl-community", | ||
| "image": "/visgl/images/frameworks/deck.gl-community.png", | ||
| "description": "Additional community-contributed layers for deck.gl." | ||
| }, | ||
| { | ||
| "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." | ||
|
|
||
| }, | ||
| { | ||
| "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." | ||
|
|
||
| } | ||
| ] | ||
| }, | ||
|
|
@@ -197,6 +215,51 @@ | |
| "description": "Development tools for vis.gl frameworks." | ||
| } | ||
| ] | ||
| }, | ||
| { | ||
| "title": "Ecosystem", | ||
| "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).", | ||
|
Collaborator
There was a problem hiding this comment. I don't see anything deck related in the awsome link?
Collaborator
There was a problem hiding this comment. 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 |
||
| "entries": [ | ||
| { | ||
| "name": "Viv", | ||
|
Collaborator
There was a problem hiding this comment. Nit: I think having a separate section for "biomolecular visualizations" could be nice, and include this link there. There was a problem hiding this comment. Once we get a bit further with https://github.com/Taylor-CCB-Group/SpatialData.js then that as well. |
||
| "url": "https://avivator.gehlenborglab.org/", | ||
| "image": "/visgl/images/frameworks/deck.gl-community.png", | ||
| "description": "Multiscale bioimaging visualization on the web, built with deck.gl." | ||
| }, | ||
| { | ||
| "name": "deck.gl-raster", | ||
| "url": "https://github.com/developmentseed/deck.gl-raster", | ||
| "image": "/visgl/images/frameworks/deck.gl-community.png", | ||
| "description": "GPU-accelerated raster visualization layers for deck.gl." | ||
| }, | ||
| { | ||
| "name": "@deck.gl-community/three", | ||
|
Collaborator
There was a problem hiding this comment. Are other people able to publish under the
Collaborator
There was a problem hiding this comment. Charles authored this module for the TreeLayer
Collaborator
There was a problem hiding this comment. Yes just realized I missed that, been too busy the last weeks. |
||
| "url": "https://visgl.github.io/deck.gl-community", | ||
| "image": "/visgl/images/frameworks/deck.gl-community.png", | ||
| "description": "Three.js-powered layers for deck.gl." | ||
| }, | ||
| { | ||
| "name": "Flowmap.blue", | ||
| "url": "https://flowmap.blue/", | ||
| "image": "/visgl/images/frameworks/FlowmapBlue.jpg", | ||
| "description": "Flow map visualization tool for geographic movement data, powered by deck.gl." | ||
| }, | ||
| { | ||
| "name": "SandDance", | ||
| "url": "https://microsoft.github.io/SandDance/", | ||
| "image": "/visgl/images/frameworks/deck.gl-community.png", | ||
| "description": "Unit visualization explorer by Microsoft, using deck.gl for rendering." | ||
| }, | ||
| { | ||
| "name": "outlined-path-layer", | ||
|
Collaborator
There was a problem hiding this comment. 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
Collaborator
There was a problem hiding this comment. I thought in the end they decided to stay separate since they may push updates after all
Collaborator
There was a problem hiding this comment.
Collaborator
There was a problem hiding this comment. 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.
Collaborator
There was a problem hiding this comment. 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 There was a problem hiding this comment. 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.
Author
There was a problem hiding this comment. 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.
Collaborator
There was a problem hiding this comment. I think it is fine to link to a raw github page that hosts an "awesome list" anyone can contribute to. 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.
Author
There was a problem hiding this comment. 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. |
||
| "url": "https://github.com/ubilabs/outlined-path-layer", | ||
| "image": "/visgl/images/frameworks/deck.gl-community.png", | ||
| "description": "Custom PathLayer by Ubilabs that renders paths with customizable outlined borders" | ||
| } | ||
| ] | ||
| } | ||
| ] | ||
| } | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.