_(Previous Post: [Part 10](/@jfollas/write-a-steemit-web-app-part-10-retrieving-comments-with-getcontentreplies))_

Previously in this series, we learned how to fetch content (blog posts and replies) from the Steemit blockchain using Steem.js. How would a web app submit new content to Steemit?

# Introducing `steem.broadcast.comment`
When posting content, there is only one Steem.js function to know: `steem.broadcast.comment`. This is used to both create new blog posts and reply to content written by other people:

```javascript
steem.broadcast.comment (
    private_posting_wif,  // Steemit.com Wallet -> Permissions -> Show Private Key (for Posting)
    parent_author,        // empty for new blog post 
    parent_permlink,      // main tag for new blog post
    author,               // same user the private_posting_key is for
    permlink,             // a slug (lowercase 'a'-'z', '0'-'9', and '-', min 1 character, max 255 characters)
    title,                // human-readable title
    body,                 // body of the post or comment
    json_metadata         // arbitrary metadata
)
```

## New Blog Posts
For new blog posts, use an empty string for `parent_author` and use the post's main Tag (Category) as the `parent_permlink`. 

It is up to your app to create the slug that will be used as the `permlink`. Steemit requires that the slug be lowercase and only numbers, letters, and the '-' dash characters be in the slug string. The length of the slug must be between 1 and 255 characters total.

The `json_metadata` argument can be either an object literal, or JSON string. While not well documented, it appears that Steemit needs certain data to appear in the metadata for a new post. 

As an example, let's look at the metadata that was submitted with [Part 10's Blog Post](https://steemdb.com/steemdev/@jfollas/write-a-steemit-web-app-part-10-retrieving-comments-with-getcontentreplies/data):

```javascript
{
    "tags": [
        "steemdev",
        "developer",
        "javascript",
        "steemjs",
        "steem-dev"
    ],
    "links": [
        "\/@jfollas\/write-a-steemit-web-app-part-9-retrieving-content-with-getdiscussionsby",
        "https:\/\/esteem.ws\/"
    ],
    "image": [
        "https:\/\/steemitimages.com\/DQmZBbDGvKqM8V46NHaXoT7nZvrXhHLtTysrhixRu8eS87g\/javascriptlogo.png"
    ],
    "format": "markdown",
    "app": "steemit\/0.1"
}
```

<br/>Steemit uses the first entry from the `image` array as the blog's picture (you can even provide this in the metadata without actually having an image in the blog post). It also uses the `tags` array to set the various categories for the blog post (maximum of 5). 

I am not sure at this time if the remaining data is used by the Condenser (i.e., steemit.com) or other apps, but `format` seems to be either "markdown" or "html", depending on the content of the post body. `app` is an identifier for the application that is posting (i.e., your web app). And `links` is apparently an array of all of the URLs found in the body.

## Replies
For replies or comments, provide the actual author and permlink that you are replying to as the `parent_author` and `parent_permlink` (these will be properties of the content's data). 

There seems to be a convention for the structure of a reply's own permlink (slug). For example:

`re-jfollas-write-a-steemit-web-app-part-10-retrieving-comments-with-getcontentreplies-20170802t041610122z`

Fortunately, Steem.js provides a helper function to create a proper `permlink` for you given the `parent_author` and `parent_permlink`:

```javascript
const permlink = steem.formatter.commentPermlink(parent_author, parent_permlink)
```

<br>As for the `json_metadata`, there doesn't seem to be a lot of consistency between apps. Steemit.com will submit something like this:

```javascript
{
    "tags": [
        "steemdev"
    ],
    "users": [
        "jfollas"
    ],
    "app": "steemit\/0.1"
}
```

<br/>The `tags` array will contain the main post's primary tag, as well as any `#tag` mentions found in the body. `users` will contain any `@user` mention found in the body. Steemit doesn't seem to use these yet, but I'm hopeful that there will be a database API developed later to allow you to find `@user` mentions (so maybe including them in the metadata is just the first step in that process).

# Deleting Content
Now, the Steemit.com website doesn't permit a post or comment to be deleted. But, there is an API function that allows for this, if ever needed. Note that this will not remove record of the post or comment from the blockchain itself, because that is a permanent recording of all transactions. But, it will prevent the content from appearing on Steemit.com, at least.

```javascript
steem.broadcast.deleteComment(private_posting_wif, author, permlink)
```

<br/>The caveat here, though, is that the post cannot have any children (replies). Once it does, calling `deleteComment()` will result in an error.


![javascriptlogo.png](https://steemitimages.com/DQmZBbDGvKqM8V46NHaXoT7nZvrXhHLtTysrhixRu8eS87g/javascriptlogo.png)

_(Next Post: [Part 12](/@jfollas/write-a-steemit-web-app-part-12-voting))_