One not so commonly talked about feature in Podio is the ability to use Markdown within Text type fields, Calculation, Tiles and Comments. I only found out about this because I was looking for different ways to highlight text (Bold, Italic, etc..) while developing my Navigation Calculation Jump Links .
What I found was that within areas of Podio that support text, but that do not have the standard Text Editor, Podio supported something called Markdown syntax. Below is an example of the Podio Text Editor.
This makes sense, because what if you wanted to add some formatting to a calculation field result or a comment, you normally could not because there was no editor controls. Enter Markdown Syntax!
What is Markdown Syntax?
Obviously you are wondering what exactly Markdown Syntax is right? Well it's basically a way to tell the browser (or Podio) how to display and format text. Normally browsers (or Podio) need HTML tags to describe the formatting of Text...
<b>This is Bold Text</b> <i>This is Italic Text</i>
The browser would then display the text as follows...
This is Bold Text This is Italic Text
Now unfortunately Podio does not allow you to enter HTML tags into its fields to format the text. If you want to Bold or Italicize some text you'll have to use Markdown. It's easy though, you just have to know the syntax. Here is a quick example for bold and italic...
For bold add 2 asterisks or underscores before and after the text: **This is Bold Text** or __This is Bold Text__ For italic add 1 asterisk or underscore before and after the text: *This is Italic Text* or _This is Italic Text_
How to use Markdown in Podio?
Like I mentioned before, there are 3 areas in Podio where you can use Markdown. Those are a Calculation Field, Tiles (on Activity Dashboard) and the Comments areas. The comments field is pretty straight forward, while using markdown in a calculation requires some work.
Markdown in Comment Areas
To use Markdown in Podio comment fields you'll just be adding the "tags" before and after the text that you want it to affect. In the below example I am making the word TEXT appear italicized TEXT. I did this by adding the markdown tags for italic, the underscore ("_") before and after the word.
Markdown in Calculation Fields
You have the basics down, so now I'm going to step it up a notch. Markdown can be used in Podio Calculation Fields. This is really helpful when you want certain information to stand out.
To output Text from a calculation field you have to wrap any text in quotes first. So...
"Text to Display"
And now if we want to add some markdown, all we have to do is add in the markdown tags inside the quotes. I'll bold the word Display
"Text to **Display**"
All calculation fields however require you to have a reference to at least one Podio Field other then itself. So to work this into the text string we need to concatenate the field token (using the @ syntax) onto the string. We do this like so...
"Text to Display from field: " + @FieldName
The + character is used for combining individual strings and field values. And now finally if we want to make the field text bold, we do this...
"Text to Display from field: **" + @FieldName + "**"
Do you see how the Markdown tags (**) are within the quotes before and after the @FieldName? That is necessary because when calculation field "calculates" the value, the final string will be like...
"Text to Display from field: **This is the field value**"
Sometimes you don't want to include another field's value in your output. To get around Podio's insistence you can just assign a field to a dummy variable like so
See how i'm not using the dummy variable in my output at all. Podio is okay with this and I use this trick all the time.
var dummy = @FieldName; "Text to **Display**"
This might not seem that hard, but it can get crazy quickly if you introduce line breaks and tables. The issue is that markdown syntax in Podio is very picky and must be formatted exactly. If not then it won't work. Let's take a look at making a table.
Here is the Calculation Field Code
"| Tables | Are | Cool |" +" \n | ------------- |:-------------:| -----:|" +" \n | " + @Title + " | right-aligned | $1600 |" +" \n | col 2 is | centered | $12 |" +" \n | zebra stripes | are neat | $1 |"
The markdown syntax for a table requires that each table row be on a separate line so you need to add in the new line code ("\n") before each row.
"\n | col 2 is | centered | $12 |"
In the example above I like to break the rows up into there own actual lines to make it easier to read. To do that you need to terminate the string by adding a closing end quote. I then have to concatenate each line together by using the '+' sign before each new row.
However, You do not need to do this and just have the entire table code in one long string like so..
"| Tables | Are | Cool | \n | ------------- |:-------------:| -----:| \n | " + @Title + " | right-aligned | $1600 | \n | col 2 is | centered | $12 | \n | zebra stripes | are neat | $1 |"
Here are more examples..
More About Podio Markdown
Markdown is used in many applications outside of Podio. While it works well in Podio, not all of the features are compatible. One of those features is the video tags. Podio will just ignore the tag.
Header tags (# - H1; ## - H2; ### - H3; etc..) sort of work in Podio. You can use them, and they do make the text larger like a header should be. However, no matter which header size (H1,H2,H3,etc..) you wish to render, it will come out the same size. Which is slightly larger then the normal Podio text.
Full list of Markdown Tags
To get a full list of all the markdown tags take a look at the links below. While most will work in Podio, some do not at this point in time. You never know when Podio will support new features. So give them a try.
I use markdown all the time within my Podio calculation fields, Globiflow generated comments and even in the Activity App Tiles. One excellent use is showing a google maps location. Take a look at my article for doing just that below. You'll recognize the use of the Image Markdown syntax.
- Make Calls and Send Texts in Podio using smrtPhone - April 26, 2019
- Email Marketing with Podio and ConvertKit: Dealing with Unsubscribes - February 27, 2019
- Email Marketing With Podio and ConvertKit: Multiple Sequences - February 12, 2019