Add Cesium

[reed-soul]

https://github.com/reed-soul/awesome-cesium#readme

Open-source JavaScript library for 3D globes and maps with geospatial data streaming. CesiumJS is the leading open-source 3D geospatial library, used in aerospace, defense, smart cities, and digital twins. This list covers frameworks, tools, game engine integrations (Unity, Unreal, Godot), AI ecosystem, and emerging technologies like 3D Gaussian Splatting.

Reviewed pull requests

I reviewed the following open PRs and left comments:

1. Add LOL #4070 (Add LOL)
2. Add Human Activity Recognition #4016 (Add Human Activity Recognition)
3. Add Helix #4009 (Add Helix)
4. Add Animal Care #4008 (Add Animal Care)

[sindresorhus]

Thanks for making an Awesome list! 🙌

It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

[n1ckfg]

@reed-soul It looks like most of the linter errors are just using * for bullets instead of the preferred - ...replacing all those and rerunning should provide a clearer picture of what needs to be fixed.

[autogame-17]

I reviewed the list at https://github.com/reed-soul/awesome-cesium and found a few issues that need attention:

1. Default branch is master, not main. The guidelines require the default branch to be named main. See: https://github.com/sindresorhus/awesome/blob/main/pull_request_template.md (section: "The default branch should be named main, not master").

2. License is MIT. The guidelines state: "We strongly recommend the CC0 license, but any Creative Commons license will work. A code license like MIT, BSD, Apache, GPL, etc, is not acceptable." You need to change the license to CC0 or another Creative Commons license.

3. Entry placement. The entry is inserted between "Tiny JS" and "Frontend GIS", but the guidelines say "Your entry should be added at the bottom of the appropriate category." It should go after the last entry in the Front-End Development section (after "WebAssembly").

These need to be fixed before the list can be accepted.

[reed-soul]

Thanks for the review @autogame-17! All three issues have been fixed:

1. Default branch — renamed from master to main
2. License — switched from MIT to CC0
3. Entry placement — moved Cesium to the bottom of the Front-End Development section (after WebAssembly)

[danzek]

@reed-soul I encourage you to carefully read through the guidelines again. You're still missing a few steps which serve as evidence you did not go through and address them all yet.

[johnxie]

Reviewing per the submission requirements:

Issues found in the list (https://github.com/reed-soul/awesome-cesium):

1. Awesome badge links to wrong URL — The badge uses [![Awesome](https://awesome.re/badge.svg)](https://github.com/sindresorhus/awesome) but should link to https://awesome.re not the GitHub repo: [![Awesome](https://awesome.re/badge.svg)](https://awesome.re)

2. Extra social badges — The README includes GitHub stars/forks/watchers badges at the top. The guidelines say not to include CI or extra dynamic badges. These social count badges add noise and are not part of the awesome list standard.

3. Nested TOC — The Table of Contents has multiple levels of nesting (e.g. Learning Resources → Tutorials, Blogs, Videos, Books). The guidelines specify: "Should only have one level of nested lists, preferably none." Flatten the TOC to a single level.

4. README description describes the list, not the theme — A curated list of awesome Cesium libraries, resources and other shiny things. describes the list itself. The theme description (what CesiumJS is) appears in the paragraph below. Per guidelines, the opening blockquote should describe the topic: e.g. > Open-source JavaScript library for 3D globes and maps with high-performance geospatial data streaming.

Addressing these would bring the list into full compliance.

[JinyangWang27]

Great addition! Cesium is a solid choice for the list.

What I like:

• Clear, focused scope
• Good description that explains what Cesium does
• Links appear to be active and relevant

One small suggestion: the description could mention the primary use cases (geospatial visualization, 3D globes, etc.) to help users immediately understand its value.

LGTM overall!

[JinyangWang27]

Solid addition! Cesium is definitely worthy of inclusion.

What works well:

• Clear description explaining what CesiumJS does (3D globes/maps with geospatial streaming)
• Good coverage: frameworks, tools, Unity/Unreal/Godot integrations, AI ecosystem
• 3D Gaussian Splatting mention shows you're tracking emerging tech
• Repo has proper structure with CC-BY-4.0 license and awesome-lint

Minor suggestion: The description mentions aerospace, defense, smart cities, digital twins as use cases — consider including one concrete example or screenshot in your list's README to showcase Cesium's visual capabilities.

Thanks for reviewing 4 other PRs first. Great community participation! LGTM

[weilun88313]

Review of awesome-cesium:

1. The Awesome badge links to https://github.com/sindresorhus/awesome instead of https://awesome.re. The badge image URL is correct (https://awesome.re/badge.svg), but per the awesome badge guidelines, the link target should be https://awesome.re, not the GitHub repo.

2. Social badges (stars, forks, watchers) in the README header. Lines 3-5 display GitHub stars, forks, and watchers shields.io badges. While the guidelines specifically mention CI badges, social/vanity badges in the header are similarly discouraged in awesome lists and should be removed.

3. The top description describes the list, not the project/theme. The blockquote says: "A curated list of awesome Cesium libraries, resources and other shiny things." This violates the requirement: "It should not describe the list itself." It should describe what CesiumJS is, e.g., > Open-source JavaScript library for 3D globes and maps with geospatial data streaming.

4. The Contents section has extensive nesting (multiple sub-levels). The guidelines say the TOC "Should only have one level of nested lists, preferably none." Your Contents has nested items under Learning Resources (4 sub-items), Framework Integration (3), Libraries & Plugins (6), etc. Consider flattening the TOC to one level.

[dwylq]

The Cesium ecosystem is a reasonable topic for this registry -- it is a well-established open-source 3D geospatial library with real adoption in aerospace, defense, and digital twins. The list has good coverage of the ecosystem including game engine integrations, data processing tools, and emerging AI integration.

A few issues to address:

1. Awesome badge link -- The badge at the top links to https://github.com/sindresorhus/awesome instead of https://awesome.re. The guidelines require linking to awesome.re specifically.

2. Extra social badges -- The header includes GitHub stars, forks, and watchers badges. These are not part of the awesome guidelines and add visual noise that is inconsistent with the formatting standards of other lists in the registry. Only the Awesome badge should be present.

3. Description -- The description says "A curated list of awesome Cesium libraries, resources and other shiny things." This is the generic boilerplate text, not a description of Cesium itself. The guidelines ask for a succinct description of the project/theme. Something like "An open-source JavaScript library for creating 3D globes and maps with geospatial data streaming" would be more informative.

4. Quick Start section -- The guidelines say the Table of Contents should be the first section. Having a Quick Start block before the main content breaks this convention. Consider moving it under the main contents or integrating it into the structure.

5. Some entries lack descriptions -- Items like "Official Documentation," "Official Examples," and "Official CesiumJS Tutorials" do not have descriptions following the standard format (link - description with period). The guidelines require all entries to have descriptions.

The content itself is solid and covers a real niche well. Fixing these formatting and guideline issues would make this a strong submission.

[andreahlert]

your description blockquote (A curated list of awesome Cesium libraries, resources and other shiny things) is the phrasing the PR template calls out as wrong. the CesiumJS paragraph right below it is already fine, just promote that one up

the Quick Start heading has an emoji in it, awesome-lint will fail on that

also the Language switcher sitting between the description and the TOC feels off. bottom of the readme or footnotes would be cleaner

but overall, looks great. thanks for your support.

[andreahlert]

description here is just the repo tagline. cesium deserves something more specific, like 3D geospatial JS library for streaming globes and planet-scale terrain