Our great sponsors
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
awesome-modern-twitter-api
Discontinued A curated list of awesome apps built with, or libraries and resources for using, the modern Twitter API
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
awesome-dva
A curated list of "damn vulnerable apps" and exploitable VMs / wargames. See contributing.md for information.
In order to plug this in to the Shields.io service, all we really need is a simple way to serve up these JSON stanzas when the URL is used. There's a very nice Node.js module to do something like this: json-server, with a tagline:
Well, that's convenient! I spun up a Twbadges, a quick app on Glitch which acts as a REST API - the data is served from a simple JSON file, and I used a couple of options to json-server to switch off the write functionality (it can support full CRUD operations if required). After that, I created a simple web page to showcase the badges using the Bulma CSS framework, and the app is ready to go! I've continued to quietly tinker with the code as a learning exercise (I haven't used Bulma before, also, I added twemoji to the web page, and messed with the layout), but it's simple and it does the job - pick from one of the available badges, and use them in your README files to show off your support of the latest Twitter developer features! You can also apply Shields.io style parameters if you want to use a different look-and-feel.
Code on GitHub (if you'd like to learn how I made this)
This is where my second side project comes in: Awesome Modern Twitter API. This is aiming to be an Awesome List that the community can contribute to in order to build a list of libraries, SDKs, tools, tutorials and projects that can help other developers to start to use the new API as quickly as possible, and to discover resources that we might not have listed directly in the main documentation. Why "Modern"? Well, that's a metaphorical "line in the sand" - v1.1 is at the end of its life and no new features will be added there, the future is the new foundation from v2 (and onwards), so the list will only include resources for the new platform.
We've all seen those nice little badges or shields that show up in Open Source project README files, to signal everything from whether the build is passing, to what license the code is under, or what operating systems the code targets. Many of these are provided by services such as Shields.io or Badgen which generate similar styles of image that can serve as quick visual guides to what features the project supports.
Well, that's convenient! I spun up a Twbadges, a quick app on Glitch which acts as a REST API - the data is served from a simple JSON file, and I used a couple of options to json-server to switch off the write functionality (it can support full CRUD operations if required). After that, I created a simple web page to showcase the badges using the Bulma CSS framework, and the app is ready to go! I've continued to quietly tinker with the code as a learning exercise (I haven't used Bulma before, also, I added twemoji to the web page, and messed with the layout), but it's simple and it does the job - pick from one of the available badges, and use them in your README files to show off your support of the latest Twitter developer features! You can also apply Shields.io style parameters if you want to use a different look-and-feel.
This is where my second side project comes in: Awesome Modern Twitter API. This is aiming to be an Awesome List that the community can contribute to in order to build a list of libraries, SDKs, tools, tutorials and projects that can help other developers to start to use the new API as quickly as possible, and to discover resources that we might not have listed directly in the main documentation. Why "Modern"? Well, that's a metaphorical "line in the sand" - v1.1 is at the end of its life and no new features will be added there, the future is the new foundation from v2 (and onwards), so the list will only include resources for the new platform.