search

Esri / awesome-arcgis-developers

A curated list of resources to help you with ArcGIS development, APIs, SDKs, tools, and location services
Creative Commons Zero v1.0 Universal
243 stars 25 forks source link

Adding APIs and SDKs category proposal #2

Closed hhkaos closed 3 years ago

hhkaos commented 3 years ago

As I mentioned on this issue I have many doubts, but I just wanted to start with one category, so I decided to go alphabetically -> "APIs and SDKs"

Note: have more category proposal like: "App Builders", "Datasets", "Data conversion tools", "Data exploration tools", "Data generation tools", "Data integration tools", "Data storage", "Design resources, tools and frameworks", "Github accounts with devtools, demos, slides, etc.", "Portal administration tools", "REST Services", "Search Engines", "Social Media", "Specifications, schemas and tools", "Training" and "Related awesome lists".

hhkaos commented 3 years ago

I thing I would like to ask / recommend / consider is to create domains for at least the most popular APIs. I always use js.arcgis.com but I'm not sure if there are more.

hhkaos commented 3 years ago

this is just a rehashing of our existing Documentation page and only offers a short description of each API's purpose. this is against the "awesome" concept of only awesome is awesome, should we not just have a link to the documentation page instead?

Yes, you are 100% right, and this was one of my doubts. According to Google, the developer site has... ~50.000 URLs 😅 , but it has a lot of useful resources that many times are not straightforward to find (even if you know they are there somewhere), like the vector tile editor, the JS playgrounds, ... And sometimes you need to browse several pages until you really understand what's the difference/purpose between some APIs. That's why I considered adding this category.

But if we decide to adhere strictly to the definition of the awesome manifesto, I guess we should avoid duplicate URLs.

In my case, with the developers.arcgis.com domain I think it would be more flexible. But I would also understand if we decide to replace it with a single link.

jf990 commented 3 years ago

@hhkaos OK, let's go forward with these links. the grouping and description are helpful, and will be more so when accompanied by more helpful links to developer resources. we can try it out and see how it all comes together and revisit the content in the future once we see how users are interacting with this list.

hhkaos commented 3 years ago

I would consider creating domains for at least the most popular APIs. I always use js.arcgis.com but I'm not sure if there are more.

@jf990, @isaacviel is this feasible?

https://android.arcgis.com https://net.arcgis.com https://java.arcgis.com ...

And probably I would point to the API Reference of each one.