# Blog

## A simple, yet powerful blog solution

Ready SaaS includes a simple yet powerful Blog content management system. It allows you to create SEO optimized blog posts right from within your Django admin without having to pay for additional blog service providers or build this yourself.

\
The markdown is beautified using Tailwind, and it looks absolutely professional.\
\
In the example below, you can see a sample blog article created using this feature.<br>

<figure><img src="https://1908511726-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT1c9BPzeUyd2bkOioywo%2Fuploads%2FLSvwBbySQJybISPByFDh%2Fimage.png?alt=media&#x26;token=946ffa10-9d0a-4988-bb30-2786f3894add" alt=""><figcaption></figcaption></figure>

You can check the live sample blog post [here.](https://ready-saas-demo-157bf36bed0c.herokuapp.com/blog/unleashing-the-power-of-blogging-with-ready-saas)

## Creating a blog post is super easy...

Just go to **admin > blog posts** and create a new post. It's going to look something like this:<br>

<figure><img src="https://1908511726-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT1c9BPzeUyd2bkOioywo%2Fuploads%2Fhh8MLEWj2X8lKKnq7Ke9%2Fimage.png?alt=media&#x26;token=3aa20f1d-d070-4fcf-bc61-644e96915080" alt=""><figcaption></figcaption></figure>

#### Fields Explained:

* **Title**
  * Displayed as the blog post title
  * Used as the \<title> meta tag for SEO
  * Used to generate an SEO-friendly url
* **Content**
  * Markdown text
* **Description**
  * Used to populate meta description tags
* **Keywords**
  * Used to pupulate meta keywords tag
* **Published**
  * Can be toggled to publish/unpublish a blog post


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://readysaas.gitbook.io/docs/features/blog.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
