# Large Documents

**URL:** <https://forums.realmacsoftware.com/t/large-documents/55837>\
**Category:** Elements\
**Created:** [April 22, 2026, 4:29pm UTC](https://forums.realmacsoftware.com/t/large-documents/55837 "2026-04-22T16:29:59Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Flash](https://avatars.discourse-cdn.com/v4/letter/f/f475e1/32.png) [@Flash](https://forums.realmacsoftware.com/u/Flash)\
**Post date:** [April 22, 2026, 4:29pm UTC](https://forums.realmacsoftware.com/t/large-documents/55837/1 "2026-04-22T16:29:59Z")

</div>

Does anyone have experience with creating very large documents with Elements yet? Meaning 200,000 words, upwards of 50 links per page, with an average page length of about 4,000–6,000 words. It’s a technical document.

I have other app options but trying to decide if Elements is a good fit.

---

<div class="post-metadata">

**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\
**Post date:** [April 22, 2026, 5:10pm UTC](https://forums.realmacsoftware.com/t/large-documents/55837/2 "2026-04-22T17:10:17Z")

</div>

My recommendation would be to use the CMS if possible!

---

<div class="post-metadata">

**Author:** ![Flash](https://avatars.discourse-cdn.com/v4/letter/f/f475e1/32.png) [@Flash](https://forums.realmacsoftware.com/u/Flash)\
**Post date:** [April 22, 2026, 5:33pm UTC](https://forums.realmacsoftware.com/t/large-documents/55837/3 "2026-04-22T17:33:35Z")

</div>

That would be fine however I need it to be stable enough that changes will not be made to the core that affect the project down the road. This is a very big project that will take about 300-400 hours to build (estimated). It is then an ongoing project requiring about 10 hours per week for the foreseeable future.

### Couple of questions.

How are we coming along with the UI?  
Does the CMS manage a database of the pages for building links without manually entering them all?

---

<div class="post-metadata">

**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\
**Post date:** [April 22, 2026, 5:48pm UTC](https://forums.realmacsoftware.com/t/large-documents/55837/4 "2026-04-22T17:48:23Z")

</div>

> [@Flash](#):
>
> This is a very big project that will take about 300-400 hours to build (estimated). It is then an ongoing project requiring about 10 hours per week for the foreseeable future.

This project sounds huge, and it’s hard to know the exact requirements you need. However, I think you might be better served with storing the content in an online database, so perhaps Elements isn’t right this project.

> [@Flash](#):
>
> How are we coming along with the UI?

Nothing to report on the UI inside the App, but the online editor is almost ready to ship.

> [@Flash](#):
>
> Does the CMS manage a database of the pages for building links without manually entering them all?

No, the links in the Markdown would have to be manually entered.

---

<div class="post-metadata">

**Author:** ![Flash](https://avatars.discourse-cdn.com/v4/letter/f/f475e1/32.png) [@Flash](https://forums.realmacsoftware.com/u/Flash)\
**Post date:** [April 22, 2026, 5:53pm UTC](https://forums.realmacsoftware.com/t/large-documents/55837/5 "2026-04-22T17:53:46Z")

</div>

Yep, doesn’t sound like this will work. I tried.

---

<div class="post-metadata">

**Author:** ![thominator](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/thominator/32/35233_2.png) [@thominator](https://forums.realmacsoftware.com/u/thominator)\
**Post date:** [April 22, 2026, 11:21pm UTC](https://forums.realmacsoftware.com/t/large-documents/55837/6 "2026-04-22T23:21:21Z")

</div>

Are you sure “article” is the right approach? I’d think that you’d want to do something that uniformly big as a PDF and embed that on a page. That’s particularly true if any of those are internal crosslinks. I tested a really large text file (100k words) in the CMS and it worked fine, but links would have to be done manually, which is a chore. That said, using something like Typora to create the Markdown and then copying that into the CMS would work.

---

<div class="post-metadata">

**Author:** ![Flash](https://avatars.discourse-cdn.com/v4/letter/f/f475e1/32.png) [@Flash](https://forums.realmacsoftware.com/u/Flash)\
**Post date:** [April 23, 2026, 11:07am UTC](https://forums.realmacsoftware.com/t/large-documents/55837/7 "2026-04-23T11:07:12Z")

</div>

The problem with Typora is the links are still built manually. I thought about [Typemill.net](http://Typemill.net), but again, manual links. Wordpress can do it, even the glossary and TOC can be built mostly automated by setting some parameters and a php script takes over. I’m checking one other idea before I head down the road of Wordpress.
