I have the following situation. I want to have a blog on bubble driving traffic to my Bubble Webapp. Since bubble is not a suitable CMS system I use airtable to create the content for blogposts and push new/updated blogpost content to Bubble via a Zapier Integration. This works like a charm.
We all know that the main part of a post is the actual body which is typically written in Markdown language. Since bubble does not have a markdown parser and available markdown plugins focus only on the markdown editor, I use a Zapier transformation to convert markdown into HTML and push the HTML code to bubble as a text.
So actually it should be so easy for Bubble to display html content properly (headings, bullet-points and so on) as it can be identified via HTML tags.
This is my sample content I get from Zapier which I am not able to display anyhow properly in Bubble. I tried two options for about a whole weekend:
- Reference the text body (which is HTML content) directly in the HTML element >> This worked only when ticking the checkbox “Display as i-Frame” in the HTML element. >> I want to avoid this
- Reference the text body in a text element and assign CSS styling to headings >> Nothing ever happened to my actual text. Not sure, what I am doing wrong here, but after trying for a whole weekend it seems to be rocket science or I am just stupid. Maybe you have an idea. Sample content below.
I am a large Heading
I am a very beautiful quote and this quote will never end
I am a medium Heading
- I am number One
I am number Two [ ] I am a checkbox [ ] I am another checkbox I am bold I am italic and bold ~~I am a strikethrough~~
I am a bullet
- I am another bullet