# API reference web page

**URL:** <https://community.cesium.com/t/api-reference-web-page/11221>\
**Category:** General\
**Created:** [October 13, 2020, 11:46am UTC](https://community.cesium.com/t/api-reference-web-page/11221 "2020-10-13T11:46:48Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aristeidis\_Bampakos](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/aristeidis_bampakos/32/2013_2.png) [@Aristeidis\_Bampakos](https://community.cesium.com/u/Aristeidis_Bampakos)\
**Post date:** [October 13, 2020, 11:46am UTC](https://community.cesium.com/t/api-reference-web-page/11221/1 "2020-10-13T11:46:48Z")

</div>

Hey Cesium team,

As an occasional user of the Cesium website, I am really glad for all the work that you have done to enhance the user experience from a developer point of view. Things as tutorials, demos and how to guides are now easier to find and use, especially with the refurbished Learning Center 💯.

However, one area that looks odd is the CesiumJS API reference 🤔. The design looks a bit old fashioned and I think that if the topics covered could be arranged in categories, they would be more easily discoverable. Generally, I feel that this part of the website should be refreshed to fit with the rest of the content.

If there is anything that I can do to help towards this direction or provide more feedback, please let me know. I would be happy to contribute to this effort 🙏

---

<div class="post-metadata">

**Author:** ![omar](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/omar/32/1999_2.png) [@omar](https://community.cesium.com/u/omar)\
**Post date:** [October 14, 2020, 2:26am UTC](https://community.cesium.com/t/api-reference-web-page/11221/2 "2020-10-14T02:26:07Z")

</div>

Hey Aristeidis, glad to hear you’ve found the revamped resources helpful!

I’m sure feedback is welcome on the [CesiumJS API reference](https://cesium.com/docs/cesiumjs-ref-doc/index.html). I think a community proposed restructuring would be welcome. The API reference doc is currently generated with [JSDoc](https://jsdoc.app/). Maybe a natural type of automated category would be the class path (for example GeoJSONDataSource and CZMLDataSource would all be under “Datasources”, you’ll have core classes under “Core” etc).

I don’t know if JSDoc supports this out of the box - are there any API doc sites you or others really like/have found useful that would be good inspiration here? Or know any doc-generation tools you’ve used that you liked?

---

<div class="post-metadata">

**Author:** ![Aristeidis\_Bampakos](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/aristeidis_bampakos/32/2013_2.png) [@Aristeidis\_Bampakos](https://community.cesium.com/u/Aristeidis_Bampakos)\
**Post date:** [October 14, 2020, 1:29pm UTC](https://community.cesium.com/t/api-reference-web-page/11221/3 "2020-10-14T13:29:36Z")

</div>

Hi @omar,

Thanks very much for your instant feedback 🙂 One of the tools that I have used before and I really liked it, was [Gitbook](https://www.gitbook.com/). Really easy to use and with a nice user interface.  
AFAIK there is an integration with JSDoc, you can find more details in this article [https://medium.com/@kevinast/integrate-gitbook-jsdoc-974be8df6fb3](https://medium.com/@kevinast/integrate-gitbook-jsdoc-974be8df6fb3). It essentially converts JSDoc to Markdown and then serves the content through Gitbook.

---

<div class="post-metadata">

**Author:** ![TJ\_Koury](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/tj_koury/32/3280_2.png) [@TJ\_Koury](https://community.cesium.com/u/TJ_Koury)\
**Post date:** [October 27, 2020, 2:56pm UTC](https://community.cesium.com/t/api-reference-web-page/11221/4 "2020-10-27T14:56:57Z")

</div>

We used the TS definitions to basically provide the documentation as hints in our IDE:

[Mapshot.app](Https://Mapshot.app).

Try typing / hovering over keywords.