1. Vonage Learn
  2. Contributing

Contributing Guide

Making a Contribution

We love contributions from everyone! 🎉

It is a good idea to talk to us first if you plan to add any new functionality. Otherwise, bug reports, bug fixes and feedback on the library is always appreciated. Check out the Contributing Guidelines for more information and please follow the GitHub Flow.

contributions welcome

The following is a set of guidelines for contributing to this project, which are hosted on GitHub. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.

Please take the time to review the Code of Conduct, which all contributors are subject to on this project.

I don't want to read this whole thing, I just have a question!!!

Writing a Post

If you've been given a login, you can access the CMS and write your content there.

Otherwise, we have a blog post CLI to start you off with an empty markdown file, or you can create the markdown file and send it as a pull request manually.

Example Blog Post

For author and categories values, see content/authors.json and content/categories.json.

title: An awesome title for your post.
description: An awesome description for your post.
thumbnail: /thumbnail-url/goes-here.png
author: tom
published: true
published_at: 2019-03-21T20:21:36.000Z
comments: true
category: tutorial
  - python
  - serverless
  - sms-api
spotlight: false
<!-- # english posts live in /content/blog/en -->

tldr or intro
## section title

some text

## conclusion

some text

Using the Blog Post CLI

Once you've cloned the repository and gone through the local setup guide, you can run the CLI using this command.

npm run blog

# > vonage-dev-blog@0.0.0 blog /Users/luke/Projects/nexmo/dev-education-poc
# > node bin/blog
# ℹ Vonage DevEd Post CLI
# ℹ by @lukeocodes
# ? Would you like to create or translate a blog post? Create
# ? What's the title for this post? <max 70 chars> An awesome ...
# ? What's the description? <max 240 chars> An awesome description ...
# ? What language would you like to create a post in? English
# ? Who's the author? Luke Oliff
# ? What's the category? Tutorial
# ? Enable comments? Yes
# ? By spotlight author? No
# ✔ Saved demo file to content/blog/en/an-awesome-title-for-your-post.md ...

You can then open up the file you've just created in content/blog/ and edit away.

Reporting Bugs

This section guides you through submitting a bug report. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports.

Before creating bug reports, please check this list as you might find out that you don't need to create one. When you are creating a bug report, please include as many details as possible. Fill out the required template, the information it asks for helps us resolve issues faster.

Note: If you find a Closed issue that seems like it is the same thing that you're experiencing, open a new issue and include a link to the original issue in the body of your new one.

Before Submitting A Bug Report

  • Perform a cursory search to see if the problem has already been reported. If it has and the issue is still open, add a comment to the existing issue instead of opening a new one.

How Do I Submit A (Good) Bug Report?

Bugs are tracked as GitHub issues. Create an issue and provide the following information by filling in the template.

Explain the problem and include additional details to help maintainers reproduce the problem:

  • Use a clear and descriptive title for the issue to identify the problem.
  • Describe the exact steps which reproduce the problem in as many details as possible. For example, start by explaining how you started. When listing steps, don't just say what you did, but explain how you did it.
  • Provide specific examples to demonstrate the steps. Include links to files or copy/pasteable snippets, which you use in those examples. If you're providing snippets in the issue, use Markdown code blocks.
  • Describe the behavior you observed after following the steps and point out what exactly is the problem with that behavior.
  • Explain which behavior you expected to see instead and why.
  • Include screenshots and animated GIFs where possible. Show how you follow the described steps and clearly demonstrate the problem. You can use this tool to record GIFs on macOS and Windows, and this tool on Linux.
  • If the problem wasn't triggered by a specific action, describe what you were doing before the problem happened and share more information using the guidelines below.
  • Can you reliably reproduce the issue? If not, provide details about how often the problem happens and under which conditions it normally happens. Include details about your configuration and environment:

Suggesting Enhancements

This section guides you through submitting a suggestion, including completely new features and minor improvements to existing functionality. Following these guidelines helps maintainers and the community understand your suggestion and find related suggestions.

Before creating enhancement suggestions, please check this list as you might find out that you don't need to create one. When you are creating an enhancement suggestion, please include as many details as possible. Fill out the required template, the information it asks for helps us resolve issues faster.

Before Submitting An Enhancement Suggestion

  • Perform a cursory search to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.

How Do I Submit A (Good) Enhancement Suggestion?

Enhancement suggestions are tracked as GitHub issues. Create an issue and provide the following information by filling in the template.

  • Use a clear and descriptive title for the issue to identify the suggestion.
  • Provide a step-by-step description of the suggested enhancement in as many details as possible.
  • Provide specific examples to demonstrate the steps. Include copy/pasteable snippets which you use in those examples, as Markdown code blocks.
  • Describe the current behavior and explain which behavior you expected to see instead and why.
  • Explain why this enhancement would be useful to most users.

Your First Code Contribution

Unsure where to begin contributing? You can start by looking through these beginner and help wanted issues:

  • Beginner issues - issues which should only require a few lines of code, and a test or two.
  • Help wanted issues - issues which should be a bit more involved than beginner issues.

Both issue lists are sorted by total number of comments. While not perfect, number of comments is a reasonable proxy for impact a given change will have.

Pull Requests

Please follow these steps to have your contribution considered by the maintainers:

  1. Follow all instructions in the template
  2. Adhear the Code of Conduct
  3. After you submit your pull request, verify that all status checks are passing.

While the prerequisites above must be satisfied prior to having your pull request reviewed, the reviewer(s) may ask you to complete additional design work, tests, or other changes before your pull request can be ultimately accepted.

I don't want to read this whole thing I just have a question!!!

You can join the Vonage Community Slack for any questions you might have:

  • Contact our Developer Relations Team
  • Reach out on Twitter
    • This Twitter is monitored by our Developer Relations team, but not 24/7 — please be patient!
  • Join the Vonage Community Slack
    • Even though Slack is a chat service, sometimes it takes several hours for community members to respond — please be patient!
    • Use the #general channel for general questions or discussion
    • Use the #status channel for receiving updates on our service status
    • There are many other channels available, check the channel list for channels for a specific library

Alternatively, you can raise an issue on the project.


Capitalize My Title

Enter your text and we'll will automatically format the input, uppercasing the first letter of the first or last words and every other word that isn't one of these; “a,” “an,” “and,” “at,” “but,” “by,” “for,” “in,” “nor,” “of,” “on,” “or,” "out," “so,” “the,” “to,” “up,” and “yet.”. This is based on capitalizemytitle.com.

Tag Tester


Vonage Tags


Language Tags


Brand Tags


Event Tags


Other Tags


Code Block Examples

Examples of different language code blocks. A full list can be found on the Prism website.

No Type

It barely gets formatted at all.


```js code goes here ```

const hello = (val) => {
  return `Hello, ${val}`



```html code goes here ```


<!doctype html>
    <h1>Hello, World</h1>


```ruby code goes here ```


def sum_eq_n?(arr, n)
  return true if arr.empty? && n == 0

  arr.product(arr).reject { |a,b| a == b }.any? { |a,b| a + b == n }


```css code goes here ```


.container {
  margin: auto;
  max-width: 1200px;
  width: 100%;


```kotlin code goes here ```


fun main(args: Array<String>) {
    println("Hello World!")

Writing Style Guide


  • Strive for a conversational tone, as if you were teaching a workshop. It’s ok to use “we” or “you” or both, but try to apply consistently. Watch out for awkward usage that comes from trying to stick too forcefully to one rule.

    • Yes: Today we’re going to learn about Flask. Open up your terminal to begin.
    • No: Let’s save our credentials in your root directory.
  • Keep your language direct, efficient, and active, especially on longer tutorials (don’t want excess text when trying to read dozens of steps). Be cautious with humor, as it doesn’t always translate across languages/cultures and can make people feel excluded.

    • Yes: On a new line, enter your application key.
    • No: Be sure your application key has been entered following your previous line, if you know what’s good for you!
  • Avoid generalizations—“We all know”, “It’s commonly accepted”—unless they are relevant and you can back them up.

  • Try to avoid -ing words in headings and titles. For example, Set Up Your Server rather than Setting Up Your Server.


  • Oxford comma—should always be used with lists of three or more! 

    • Yes: This practice keeps your application secure, resilient, and easy to deploy.
    • No: Next let’s sign up, download the file and install.
  • A period should be followed by a single space.

  • Hyphens are used between words when the phrase is acting as an adjective.

    • Yes: Time to brush off your front-end skills.
    • No: Let’s switch to the application’s front-end.
  • The em dash (—) can be used as an alternative to a comma, semicolon, colon, or parenthesis, but don’t get carried away! It can easily lead to run-on and confusing sentences. If you are using it, be sure to use a proper em dash (longer than a hyphen, look up how to do it for your operating system) and don’t leave space between the dash and the surrounding words.

    • Yes: This application—once finished—will allow users to log in seamlessly.
    • No: Follow along with this tutorial -- it will give you all the information you need.
  • To make an acronym plural, just add s (DON’T use an apostrophe) It is APIs not API's, SDKs not SDK's, and JWTs not JWT's.


  • Inline code (single backticks) is used for typed input, such as a value entered into a field or at a terminal line, as well as names of variables, libraries, functions/methods/classes, and files.

  • Code blocks (triple backticks) can also be used to show text-based output.

They are used for portions of code or
configuration files as well as terminal

Anything inside a code block will not be formatted, so they are good for showing text with characters that might have a specific meaning to the markdown renderer.

  • Italics (use underscores) are for pointing out text-based elements of the UI (i.e. “Click on File > Open” or “Click the Save button”).

  • Bold (use double **) is used for emphasis and as appropriate for names of concepts/products when first introduced. Shouldn’t be over used.

  • Headings should use ## for sections and ### for subsections. 

  • Capitalize the first letter of each word in your headings, apart from articles (the, a, an), prepositions (in, at, by, on, for) and conjunctions (and, or, nor, yet, for so, but). If you are not sure, you can use one of these tools that capitalize the title correctly for you: TitleCase or Capitalize My Title (use the AP Style)

  • For links, try to have the link naturally included in an appropriate phrase. Rather than using “You can find more information here” or “Click here to read more”, use something like “The SMS API allows you to quickly send messages.”

  • Add a UTM link: https://dashboard.nexmo.com/sign-up?utm_source=DEV_REL&utm_medium=github&utm_campaign=github-repo whenever directing the reader to sign up for a Nexmo account. (replace github-repo with your own repo link). 

  • Keep a white space line between paragraphs.


  • Titles should be under 71 and include keywords related to technologies and languages used in the post.

  • Include a description, under 160 characters, that will show up for your post in search results.

  • Posts should include at least 4 mentions of your SEO key phrase.

  • Majority of image alt descriptions should include your SEO key phrase.

    • Ok alt: Screenshot of chat
    • Bad alt: Screenshot
    • Really bad alt:
    • Amazing alt: Screenshot of Client SDK conversation between two users
  • Include links to related articles inside the blog content.

  • Concluding section should include links to further reading as well as the Vonage Developer Twitter and Community Slack.