# Articles (blog)

The OpenChurch platform uses the 'default' article content type provided by Drupal's "standard" profile.

### Creating an Article

1\. Visit /node/add/article to add a new article to the website.

<figure><img src="/files/2BmRdPVsVVch8Y1CZcPA" alt=""><figcaption><p>Create Article page</p></figcaption></figure>

2\. After saving the article you should see a page similar to the article below.

<figure><img src="/files/ChM8kTjyMhN0L25WnNF5" alt=""><figcaption><p>Sample article page</p></figcaption></figure>

### Article pages and blocks

Notice that articles will display on the homepage in the "Latest Articles" block.

<figure><img src="/files/ow4NZgKaDRWdonaVfIL6" alt=""><figcaption><p>Latest articles block</p></figcaption></figure>

Underneath the "Pages" main navigation dropdown you will also see a link to an example "Blog" page which will list all articles which can be filtered by "tag."

<figure><img src="/files/Ia2D8ZYgmQyswTyyDWCG" alt=""><figcaption><p>"Our Blog" menu link</p></figcaption></figure>

<figure><img src="/files/FTjSRN35r5SA0ou9JNV3" alt=""><figcaption><p>"Our Blog" page</p></figcaption></figure>

The "Latest Articles" block, "Our Blog" page and Tags block are all views that can be customized at /admin/structure/views.

By default, tags are passed as an argument to the /blog/ path. This path can be configured at /admin/appearance/settings/openchurch\_theme/.

<figure><img src="/files/mZ378bislDIdexRQibTT" alt=""><figcaption><p>OpenChurch configuration page</p></figcaption></figure>

Note that sidebar blocks can be configured at /admin/structure/block/.


---

# 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://drupalninja.gitbook.io/guide/managing-content/articles-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.