[dba-VS] ASP.NET MVC: Retrieve HTML encoded content
dw-murphy at cox.net
Fri Oct 7 12:00:10 CDT 2016
I am probably missing something, but why not use an existing CMS and not
have to do any development? I use DOTNETNUKE for some organization sites on
shared hosted accounts and they work well. Once the folks involved get a
little training they can maintain their sections of the site using the built
From: dba-VS [mailto:dba-vs-bounces at databaseadvisors.com] On Behalf Of
Sent: Friday, October 07, 2016 3:36 AM
To: Development in Visual Studio
Subject: [dba-VS] ASP.NET MVC: Retrieve HTML encoded content
I'm working with a small low-traffic website that mostly will contain pages
(partial views) with text like articles - title, subtitle, body perhaps with
some links and lists.
Much like a miniature CMS, but while the layout will be fixed, the content
may have to be edited over time.
My first thought was simply to store the content stubs in discrete text
files which easily could be replaced without rebuilding the site, but just
naming these files quickly will be a mess, I think.
Then I thought of a database, but isn't that overkill? Also, that will
require an "admin" section or separate app or the like to edit the content,
and then the project suddenly escalates.
So is there something in between simple files and a database, that my lack
of fantasy is leaving out?
I also thought of XML files, which I have used before with some success, but
that was for traditional data storage, not text blocks.
Further, how do you go about editing the content as HTML? I will only need
basic attributes like bold, link, and list. Do you write up the content in
an HTML editor, save this, and then retrieve it as raw HTML?
dba-VS mailing list
dba-VS at databaseadvisors.com
More information about the dba-VS