Is it ok to save large html content in the database when building a CMS

I'm building a site which mainly has articles and I'm using **ASP.NET MVC 5** framework and SQL server.

I want to handle the site as a Content Management System, where I can add, edit these article content.
I'm planning to use a **Rich text editor** (TinyMCE) to handle content of an article (Add and edit text, images, links etc.).

In this approach I'll have to save the html of a whole article page in a database column, like given below.

*Article table columns*


- ArticleId
- ArticleTitle
- CreatedDate

- Content (The html of the whole article, generated by the text editor)

I searched about saving html in database and I found mixed responses.
I would want to know is this conceptually correct in a general perspective and in an ASP MVC perspective. and I'm open to alternative approach.

After researching a lot on this,

Lots of CMSs save **HTML content generated from Rich Text Editors** in databases as HTML (Even Wordpress [
Why does Wordpress stores HTML in the Database][1]).


[1]:

[To see links please register here]

So the below approach is pretty acceptable.

Article table columns

- ArticleId
- ArticleTitle
- CreatedDate
- Content (The html content, generated by the text editor)

When rendering the page, use a template for the Article page, which will handle the layout of the page.