> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/app/navigation/home-screen/mark-blogs-sticky.md).

# Mark blogs sticky

### How to mark your WordPress blogs sticky?

To showcase a blog on the dashboard of your mobile application, you must mark it as “Sticky” from the backend of your WordPress website. Here are the steps you can follow to mark a blog sticky:

{% embed url="<https://scribehow.com/shared/Mark_blogs_sticky__Ir1MdOjTQPKlozYb7d7M2Q>" %}

#### Option 1: Use the Edit option

* Login to the backend of your WordPress website and navigate to **Posts > All Posts** from the side menu.&#x20;
* Select the blog that you’d like to mark sticky.
* Click on “Edit” under the blog’s name to access the post's backend.
* On the right, you’ll find a section called Status & visibility.
* Click to check the box against “Stick to the top of the blog”
* Finally, click on “Update” to save settings.

#### Option 2: Use the ‘Quick Edit’ option

Here is an alternate way to mark a blog sticky.

* Login to the backend of your WordPress website and navigate to the Posts > All Posts.
* Click “Quick Edit” under the blog you wish to mark as sticky.
* Click to check the box against “Make this post sticky".
* Finally, click on “Update” to save settings.

{% hint style="danger" %}
The blogs marked as **sticky** on your WordPress website will appear in the **Popular** section of your app's home screen. If no blogs are marked as sticky, the Popular section will remain empty, even if it is enabled.&#x20;
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmysite.com/app/navigation/home-screen/mark-blogs-sticky.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.