# Text field allow a whole paragraph to be written and shown

**URL:** <https://forum.getkirby.com/t/text-field-allow-a-whole-paragraph-to-be-written-and-shown/32188>\
**Category:** Questions\
**Created:** [August 6, 2024, 11:34am UTC](https://forum.getkirby.com/t/text-field-allow-a-whole-paragraph-to-be-written-and-shown/32188 "2024-08-06T11:34:37Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![m-e](https://avatars.discourse-cdn.com/v4/letter/m/54ee81/32.png) [@m-e](https://forum.getkirby.com/u/m-e)\
**Post date:** [August 6, 2024, 11:34am UTC](https://forum.getkirby.com/t/text-field-allow-a-whole-paragraph-to-be-written-and-shown/32188/1 "2024-08-06T11:34:37Z")

</div>

My pages have a paragraph H2 intro. No links, bold, italic, bullet points, other headings – just a paragraph of text.

`<h2><?= $page->page_intro() ?></h2>`

In my Blueprint I thought the plain Text field would be best, but in the Panel it doesn’t wrap the text on to numerous lines, meaning it is impossible to see all the paragraph.

Is there a way to change the Text field size to accommodate more than a few words / one line?

If not, should I use the Writer field and remove all the marks and nodes?

---

<div class="post-metadata">

**Author:** ![texnixe](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/texnixe/32/5754_2.png) [@texnixe](https://forum.getkirby.com/u/texnixe)\
**Post date:** [August 6, 2024, 11:40am UTC](https://forum.getkirby.com/t/text-field-allow-a-whole-paragraph-to-be-written-and-shown/32188/2 "2024-08-06T11:40:19Z")

</div>

You can use a writer field and disable marks and nodes, yes. And use it in [inline mode](https://getkirby.com/docs/reference/panel/fields/writer#inline-mode)

---

<div class="post-metadata">

**Author:** ![m-e](https://avatars.discourse-cdn.com/v4/letter/m/54ee81/32.png) [@m-e](https://forum.getkirby.com/u/m-e)\
**Post date:** [August 6, 2024, 11:42am UTC](https://forum.getkirby.com/t/text-field-allow-a-whole-paragraph-to-be-written-and-shown/32188/3 "2024-08-06T11:42:22Z")

</div>

Thanks.

Would it be useful to allow the Text field to accommodate more than a few words – allow the text to wrap on to numerous lines?

---

<div class="post-metadata">

**Author:** ![texnixe](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/texnixe/32/5754_2.png) [@texnixe](https://forum.getkirby.com/u/texnixe)\
**Post date:** [August 6, 2024, 3:14pm UTC](https://forum.getkirby.com/t/text-field-allow-a-whole-paragraph-to-be-written-and-shown/32188/4 "2024-08-06T15:14:15Z")

</div>

No, an HTML input field is not made for multi-line text. If you want multiline text, use a textarea or writer field. Just wondering why you are using a h2 element for long text.

---

<div class="post-metadata">

**Author:** ![m-e](https://avatars.discourse-cdn.com/v4/letter/m/54ee81/32.png) [@m-e](https://forum.getkirby.com/u/m-e)\
**Post date:** [August 6, 2024, 6:14pm UTC](https://forum.getkirby.com/t/text-field-allow-a-whole-paragraph-to-be-written-and-shown/32188/5 "2024-08-06T18:14:37Z")

</div>

> an HTML input field is not made for multi-line text. If you want multiline text, use a textarea or writer field.

But a textarea or writer field is a pain, when at times we just want to insert a sentence or two of (plain) text into a p tag or heading tag. Without having to turn off the toolbar or marks and nodes.

I’m not sure why the text inside a text field can\t simply wrap on to another line?

---

<div class="post-metadata">

**Author:** ![texnixe](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/texnixe/32/5754_2.png) [@texnixe](https://forum.getkirby.com/u/texnixe)\
**Post date:** [August 6, 2024, 6:16pm UTC](https://forum.getkirby.com/t/text-field-allow-a-whole-paragraph-to-be-written-and-shown/32188/6 "2024-08-06T18:16:42Z")

</div>

Maybe read up on the HTML input element: [\<input type="text"\> - HTML: HyperText Markup Language | MDN](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/text)

So, if you want to use long-form text, don’t use an input field, it’s not made for it. But I’m repeating myself.

Apart from that, I’d reconsider using h elements for such long text.

And regarding the blueprint setup: Set up such a field once, reuse everywhere. No pain.
