# How I Publish Content to curiouslychase.com

> How I publish content to curiouslychase.com

Source: https://curiouslychase.com/posts/how-i-publish-content-to-curiouslychasecom/

Previously I iterated on a few solutions to publish content and they each had downsides...

First, I [used Dropbox to publish my posts](https://curiouslychase.com/posts/back-to-writing-content-in-dropbox/). The downsides were:

- Files didn't stay in sync between [Obsidian](https://curiouslychase.com/tools/obsidian/) sync and Dropbox.
- I had to stay up to date with the Dropbox API and it changed quit a bit
- I wasn't needing to "publish on the go" the way I anticipated I needed to.

In my second iteration, I wanted to focus on publishing more of what I originally considered posts as "notes", so I was using [Obsidian Publish](https://curiouslychase.com/posts/obsidian-publish/) by fetching content on request and serving a rendered version via [NextJS](https://curiouslychase.com/tools/nextjs/). The downsides were:

- It was slow to render
- My URLs were hard to read
- It was brittle because I kept track of the entire path of a file. If I moved it, it broke the URL

# Goals

My goals are to...
- publish content easily (but not necessarily on the fly) 
- reduce duplication of where I write and focus in on [Obsidian](https://curiouslychase.com/tools/obsidian/)
- reduce creating redirects

# New Solution

I now copy my Obsidian vault on my computer into my [`git`](https://curiouslychase.com/engineering/git/) repo's `content` folder and publish on push.

## Implementation [!TODO]