<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Propel field notes</title><description>Practical thinking on marketing measurement, attribution, data quality, and trustworthy decision systems.</description><link>https://partnerwithpropel.com/</link><language>en-us</language><item><title>Test Post — Hello from Notion</title><link>https://partnerwithpropel.com/blog/test-post-hello-from-notion/</link><guid isPermaLink="true">https://partnerwithpropel.com/blog/test-post-hello-from-notion/</guid><description>A simple test post to check the write-and-publish-via-Notion workflow.</description><pubDate>Sat, 25 Jul 2026 00:00:00 GMT</pubDate><content:encoded>## Testing the Blog Rendering Pipeline

This post exists to verify that content written in Notion renders correctly once published to the website. It exercises a range of formatting so you can spot anything the engine handles incorrectly.

### Text formatting

You should see **bold text**, _italic text_, _**bold italic**_, ~~strikethrough~~, and `inline code`. Here is an [external link](https://www.partnerwithpropel.com/) that should be clickable.

### A bulleted list

- First item, plain

- Second item with **bold** inside

- Third item with a nested list:
  - Nested item A
  - Nested item B

### A numbered list

1. Confirm topic and angle

1. Draft the article in Notion

1. Move status to Ready to Publish

1. Engine publishes and writes back the URL

### Quote and callout

&gt; Measurement only matters if someone acts on it.

### Code block

```python
def publish(post):
    html = render_markdown(post.body)
    url = website.publish(title=post.title, html=html)
    return url
```

### Heading levels

#### Heading 3

Some supporting text under a level-three heading.

### Wrap-up

If every element above renders cleanly on the site, the pipeline is good to go. This is placeholder content — safe to delete or overwrite after testing.</content:encoded></item></channel></rss>