# Blog Post 🗞

* [ ] Title

  Copy that educates the user on what to expect to read, typically phrased in an eye-catching or interesting manner
* [ ] Sub heading

  Elaborating on the title, defining the purpose of the post
* [ ] Thumbnail

  A visual aid to illustrate the the themes of the content

  ⭐️ Thumbnail style should draw from branding and style guide
* [ ] Author

  Who wrote and contributed to the post

  ⭐️ Make an author's profile selectable to let users follow their favourite writers in the blog
* [ ] Content

  The actual blog post itself

  ⭐️ Consider responsiveness and how content is represented on smaller devices

  ⭐️ Text size should be minimum 18px to ensure readability
* [ ] Social sharing tools

  Ability to share or send the post to other people

  ⭐️ Positioning this element in a fixed position on the page allows the opportunity for the user to share the post at any point
* [ ] Author

  Who wrote and contributed to the post

  ⭐️ Make an author's profile selectable to let users follow their favorite writers in the blog
* [ ] Lead conversion content

  Introducing relevant information about your product that ties in with the post
* [ ] Related articles

  Suggested posts relevant to the current post
* [ ] Opt-in for subscription

  A signup form for users to join which will subscribe them to a platform that lets you notify them of new posts
* [ ] Date posted

  When the post was shared live
* [ ] Tags

  A specific category for users to explore as a topic
* [ ] Comments

  A section for discussion that users can join and contribute to


---

# 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://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/pages/blog-post.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.
