[{"data":1,"prerenderedAt":130},["ShallowReactive",2],{"blog-\u002Fblog\u002Fenhanced-docs-and-mkjsfiddle\u002F":3,"related-blog-\u002Fblog\u002Fenhanced-docs-and-mkjsfiddle\u002F":99},{"id":4,"title":5,"abstract":6,"author":6,"body":7,"description":84,"excerpt":6,"extension":85,"head":6,"image":6,"keywords":86,"meta":90,"modified":6,"navigation":92,"path":93,"proficiencyLevel":6,"published":94,"rawbody":95,"schemaOrg":6,"schemaType":6,"seo":96,"stem":97,"__hash__":98},"blog\u002Fblog\u002Fenhanced-docs-and-mkjsfiddle.md","Enhanced Documentation and Introducing mkjsfiddle",null,{"type":8,"value":9,"toc":77},"minimark",[10,14,18,36,45,50,65,69],[11,12,5],"h1",{"id":13},"enhanced-documentation-and-introducing-mkjsfiddle",[15,16,17],"p",{},"At Stadia Maps, we work hard to make your mapping experience easy and painless. A core part of our mission to make\nlocation human is making our docs as accessible as possible for you as a developer. The fewer the hurdles to\ndevelopment, the faster you can deliver solutions to your customers.",[15,19,20,21,29,30,35],{},"Experimenting with code and seeing results instantly is an effective way to learn a new library or framework. If you’re\na frontend developer, there’s a good chance you have already used ",[22,23,28],"a",{"href":24,"rel":25,"target":27},"https:\u002F\u002Fjsfiddle.net\u002F",[26],"external","_blank","JSFiddle"," for this a few\ntimes. We did some digging and found that they have\nan ",[22,31,34],{"href":32,"rel":33,"target":27},"https:\u002F\u002Fdocs.jsfiddle.net\u002Fapi\u002Fdisplay-a-fiddle-from-post",[26],"API",", which lets us generate fiddles from the code\nsegments in our docs, freeing you to focus on what matters. No need to copy the code to your computer, start up a web\nserver, or register an account—just start fiddling!",[15,37,38,39,44],{},"We've updated the relevant code snippets in our docs, such as vector and raster map examples, with a nifty button to\nedit the sample right away in JSFiddle. Check it out in action ",[22,40,43],{"href":41,"rel":42,"target":27},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fvector\u002F",[26],"over here","!",[46,47,49],"h2",{"id":48},"announcing-mkjsfiddle","Announcing mkjsfiddle",[15,51,52,53,58,59,64],{},"While we were building the integration, we looked around for a library that would do it automatically. We\nuse ",[22,54,57],{"href":55,"rel":56,"target":27},"https:\u002F\u002Fwww.mkdocs.org\u002F",[26],"MkDocs"," for generating our documentation pages from Markdown, and we thought surely\nsomeone would have a plugin for this already. Unfortunately we couldn’t find any, so we wrote one! We think other\nMkDocs-based sites can benefit from JSFiddle integration as well, so\nwe’ve ",[22,60,63],{"href":61,"rel":62,"target":27},"https:\u002F\u002Fgithub.com\u002Fstadiamaps\u002Fmkjsfiddle",[26],"open-sourced our plugin",". We hope other projects can use this to make\ntheir docs a little more human.",[46,66,68],{"id":67},"talk-to-us","Talk to us!",[15,70,71,72,76],{},"Are our docs helping you easily find the information you need? Wish you could do something more with Stadia Maps? We’re\nalways happy to hear how we can improve! Let us know via ",[22,73,75],{"href":74},"mailto:support@stadiamaps.com","email"," or the social links\nbelow.",{"title":78,"searchDepth":79,"depth":79,"links":80},"",4,[81,83],{"id":48,"depth":82,"text":49},2,{"id":67,"depth":82,"text":68},"We've enhanced our documentation with JSFiddle integration and open-sourced the code we used to do it!","md",[87,28,88,89],"Documentation","Open Source","Developer Experience",{"subtitle":91},"Better examples and an open source library!",true,"\u002Fblog\u002Fenhanced-docs-and-mkjsfiddle","2020-03-04","---\nsubtitle: Better examples and an open source library!\npublished: 2020-03-04\ndescription: \"We've enhanced our documentation with JSFiddle integration and open-sourced the code we used to do it!\"\nkeywords:\n  - Documentation\n  - JSFiddle\n  - Open Source\n  - Developer Experience\n---\n\n# Enhanced Documentation and Introducing mkjsfiddle\n\nAt Stadia Maps, we work hard to make your mapping experience easy and painless. A core part of our mission to make\nlocation human is making our docs as accessible as possible for you as a developer. The fewer the hurdles to\ndevelopment, the faster you can deliver solutions to your customers.\n\nExperimenting with code and seeing results instantly is an effective way to learn a new library or framework. If you’re\na frontend developer, there’s a good chance you have already used [JSFiddle](https:\u002F\u002Fjsfiddle.net\u002F) for this a few\ntimes. We did some digging and found that they have\nan [API](https:\u002F\u002Fdocs.jsfiddle.net\u002Fapi\u002Fdisplay-a-fiddle-from-post), which lets us generate fiddles from the code\nsegments in our docs, freeing you to focus on what matters. No need to copy the code to your computer, start up a web\nserver, or register an account—just start fiddling!\n\nWe've updated the relevant code snippets in our docs, such as vector and raster map examples, with a nifty button to\nedit the sample right away in JSFiddle. Check it out in action [over here](https:\u002F\u002Fdocs.stadiamaps.com\u002Fvector\u002F)!\n\n## Announcing mkjsfiddle\n\nWhile we were building the integration, we looked around for a library that would do it automatically. We\nuse [MkDocs](https:\u002F\u002Fwww.mkdocs.org\u002F) for generating our documentation pages from Markdown, and we thought surely\nsomeone would have a plugin for this already. Unfortunately we couldn’t find any, so we wrote one! We think other\nMkDocs-based sites can benefit from JSFiddle integration as well, so\nwe’ve [open-sourced our plugin](https:\u002F\u002Fgithub.com\u002Fstadiamaps\u002Fmkjsfiddle). We hope other projects can use this to make\ntheir docs a little more human.\n\n## Talk to us!\n\nAre our docs helping you easily find the information you need? Wish you could do something more with Stadia Maps? We’re\nalways happy to hear how we can improve! Let us know via [email](mailto:support@stadiamaps.com) or the social links\nbelow.",{"title":5,"description":84},"blog\u002Fenhanced-docs-and-mkjsfiddle","N5uioRRARxmYcCoQXg9D8ss7A8FNn_MEGzd9lQlmJrU",[100,111,120],{"title":101,"description":102,"path":103,"published":104,"keywords":105,"rawbody":110},"Sponsorship of Two Open Data Projects","We continue our support of the open-source community by sponsoring two organizations: The OpenStreetMap Foundation and OpenAddresses.","\u002Fblog\u002Fsponsorships-osmf-openaddresses","2023-09-04",[88,106,107,108,109],"OpenStreetMap","OpenAddresses","Sponsorship","Community","---\ndescription: \"We continue our support of the open-source community by sponsoring two organizations: The OpenStreetMap Foundation and OpenAddresses.\"\npublished: \"2023-09-04\"\nkeywords:\n  - Open Source\n  - OpenStreetMap\n  - OpenAddresses\n  - Sponsorship\n  - Community\n---\n\n# Sponsorship of Two Open Data Projects\n\nStadia Maps leverages open-source mapping technologies and datasets.  Since our inception, we have continually\ncontributed our technical expertise back to several projects, including [Valhalla](https:\u002F\u002Fvalhalla.github.io\u002Fvalhalla\u002F)\nand [MapLibre](https:\u002F\u002Fmaplibre.org), as well as open-sourcing some [projects of our own](https:\u002F\u002Fgithub.com\u002Fstadiamaps).\n\nWe are happy to announce our financial support for two organizations, whose work we both rely on and contribute back to: the \n[OpenStreetMap Foundation](https:\u002F\u002Fosmfoundation.org\u002F) (Bronze level) and [OpenAddresses](https:\u002F\u002Fopenaddresses.io).\n\nWe take pride in contributing monetarily to these organizations, playing our role in helping secure their future.\n\n## Learn More About Stadia Maps\n\n- Read more about the [products we offer at Stadia Maps](https:\u002F\u002Fstadiamaps.com\u002Fproducts\u002F).\n- [Create an account](https:\u002F\u002Fclient.stadiamaps.com\u002Fsignup\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=sponsor_organizations&utm_content=sponsorship_osfm_openaddresses) to start building today!\n- Join our community on [Slack](https:\u002F\u002Fslack.openstreetmap.us\u002F) or [Discord](https:\u002F\u002Fdiscord.gg\u002FqRBy6qqtdT), follow us\non [Mastodon](https:\u002F\u002Fen.osm.town\u002F@stadiamaps), [Twitter](https:\u002F\u002Ftwitter.com\u002F@stadiamaps), or\n[LinkedIn](https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fstadia-maps\u002F), or sign-up for our [mailing list](https:\u002F\u002Feepurl.com\u002Fgs51fD)!\n",{"title":112,"description":113,"path":114,"published":115,"keywords":116,"rawbody":119},"Announcing Time Zone APIs and a Documentation Refresh","Product Update: Time zone API release and a much-needed documentation overhaul.","\u002Fblog\u002Fproduct-updates-time-zones-and-docs","2022-07-28",[117,87,118],"Time Zone API","Product Update","---\npublished: 2022-07-28\ndescription: \"Product Update: Time zone API release and a much-needed documentation overhaul.\"\nkeywords:\n  - Time Zone API\n  - Documentation\n  - Product Update\n---\n\n# Announcing Time Zone APIs and a Documentation Refresh\n\nWe are excited to announce two important product updates today. Following a period of closed beta testing, we are\nofficially releasing our [time zone API](\u002Fproducts\u002Fgeospatial-apis\u002F).\n\nAlong with this release, we’ve given our [developer documentation](https:\u002F\u002Fdocs.stadiamaps.com){target=\"_blank\"}\nlong-overdue facelift and added an exhaustive [API reference](https:\u002F\u002Fdocs.stadiamaps.com\u002Fapi-reference\u002F){target=\"_blank\"}.\n\n## Time Zone API\nBuild time zone aware applications with our new Time Zone APIs! Whether you need to determine the local time\nzone of an event or plan a round-the-world trip, our new Time Zone APIs give\nyou the simple tools needed to make your app a little bit smarter.\n\nOur newest API enhances your applications with time zone information for any point on earth. You supply the\ncoordinates, and we provide the time zone in a few useful formats, including the canonical time zone identifier\nand UTC offset information. In addition to the standard UTC offset, the time zone API provides any special\noffsets, such as if daylight saving or summer time is in effect. You can also specify an effective timestamp to\nretrieve the UTC offsets at a point in the past or future. Check out the\n[documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002Ftz\u002F){target=\"_blank\"} for the full details.\n\n### Get Stated with the Time Zone API\n\nWe can’t wait to see what you build with our new Time Zone API. To get you started, we’ve written up a fresh\nPython tutorial in our [documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002Ftz\u002F){target=\"_blank\"}.\n\n## Documentation Refresh\n\nSpeaking of docs, we recently gave our [docs](https:\u002F\u002Fdocs.stadiamaps.com\u002F){target=\"_blank\"}.\na long-overdue facelift, in large part thanks to [Material for MkDocs](https:\u002F\u002Fsquidfunk.github.io\u002Fmkdocs-material\u002F){target=\"_blank\"}\n(which we now \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsponsors\u002Fsquidfunk\" target=\"_blank\">sponsor\u003C\u002Fa>). This is a\n*massive* upgrade which includes dark mode, better looking code blocks, improved navigation, and more.\n\nWe’ve also added a full [API reference](https:\u002F\u002Fdocs.stadiamaps.com\u002Fapi-reference\u002F) that makes it easier to see\nall the endpoints we offer, along with comprehensive schema documentation. The new reference is generated from\nan \u003Ca href=\"https:\u002F\u002Fapi.stadiamaps.com\u002Fopenapi.yaml\" target=\"_blank\">OpenAPI specification\u003C\u002Fa>,\nwhich we will keep up to date as we add new endpoints. This machine-readable spec\ncan be used to generate an up-to-date API client in any major programming language, and allows us to provide you\nwith the new handy online API explorer.\n\n\n## Talk to us!\n\nWhat else do you want to do with our APIs? We’re always happy to\nhear what else we can do for you or just learn about what\nyou’re working on! You can get in touch via\n\u003Ca href=\"mailto:support@stadiamaps.com\">email\u003C\u002Fa> or the social links\nbelow.\n",{"title":121,"description":122,"path":123,"published":124,"keywords":125,"rawbody":129},"Mapbox GL JS v2 Licensing and Stadia Maps","An Update on Mapbox GL JS v2 Licensing and Stadia Maps","\u002Fblog\u002Fmapbox-gl-licensing-and-stadia-maps","2020-12-09",[126,127,128,88],"Mapbox GL JS","Licensing","MapLibre","---\ndescription: An Update on Mapbox GL JS v2 Licensing and Stadia Maps\npublished: 2020-12-09\nkeywords:\n  - Mapbox GL JS\n  - Licensing\n  - MapLibre\n  - Open Source\n---\n\n# Mapbox GL JS v2 Licensing and Stadia Maps\n\nYesterday (Dec. 8th, 2020), in conjunction with the v2 release of the\nMapbox GL JS library, the code was re-licensed to require an active\ncommercial license and subscription agreement with Mapbox. As a result,\nif you are currently using Mapbox GL JS v1 with Stadia Map tiles and\nupgrade to v2, you will need to pay Mapbox (as well as Stadia Maps) for\nmap usage.\n\nFor now, please continue using Stadia Maps' map tiles with version v1.13 or\nbelow. Since these versions are fully open source and freely licensed, you\nwill not incur any additional charges and your maps will continue to function as\nexpected.\n\nStadia Maps is actively working to build consensus towards a\ncommunity-driven, fully-open and free fork of Mapbox GL JS v1, and we\nwill continue to support and collaborate on these efforts going forward.\nIf you’re a developer or an organization utilizing the Mapbox GL JS or\nGL Native libraries and are looking for an alternative, feel free to\nreach out. We will continue working together for a more open and more\naccessible open mapping ecosystem.\n",1778676027739]