Menu
Community /Pin to ProfileBookmark
@NogDogAug 18.2016 — #
While I understand the viewpoint, you have to look at it from a full ROI perspective. If by using a CMS you can get an acceptable solution running in some significant fraction of the time you would otherwise (e.g. writing everything from scratch), then you've spent that much less time (and time == money) to develop it, [i]and[/i] it's live and (hopefully) starting to make a return on the investment you made.
Now, the hard part is knowing how to determine if (a) a CMS can actually do what you want it to, and (b) if so, will it actually save you enough time to make it worthwhile? ?@NogDogAug 18.2016 — #
Which is essentially the gist of any CMS. ? So it likely becomes a case of picking the CMS with the features and look/feel (which can be from 3rd-party templates) that you want. You might want to poke around at opensourcecms.com for some options.
You can, of course, write what would essentially be your own CMS if you only need something really simple that a login system and a few basic forms could do for you. If it's going to be more complex, or your coding skills are not up to that, or time is a constraint, then picking an existing CMS seems logical to me.@NogDogAug 25.2016 — #If you want a facility for a non-technical user to update the site, but you want to code it yourself, then you essentially need to code it as your own CMS. That means adding user login/authentication (so that only authorized users can change the content), and some way for them to actually make the changes. If the layout will stay the same, then all(?) you need are form fields where they can edit the text for the relevant text sections, and upload new images to replace the current ones. Those "pieces" will then likely be stored somewhere (database, config file, etc.?), and then the actual page view would be a script that dynamically loads those pieces in. Let's say you just save the text pieces in 2 files, called text1.txt and text2.txt. In PHP, a simple way to include them would be something like:
Pre-developed site with CMS? URGENT HELP
So I’m developing a portfolio for my friend who is a renown printmaker. I need to code a site that he can edit without having to actually change/write code. He would have to update photos, descriptions, and other content. I’ve heard the best way to go about doing this is to integrate a CMS (content management system). How do I go about doing that?
Do I develop the website first and then integrate with a CMS like WordPress (was recommended), or do I have to do something special with WordPress while I’m developing it? Do I have to develop a template, and then bring in his info via WordPress? I’m just kind of confused where to start. If someone could point me to good tutorials or give me any general info, I should be able to rocket off from there. Thanks guys!
Sign in
to post a comment14 Comments(s) ↴
0
@NogDogAug 18.2016 — #avoid CMS mad simple, that is all I can say on the subject.[/QUOTE]
While I understand the viewpoint, you have to look at it from a full ROI perspective. If by using a CMS you can get an acceptable solution running in some significant fraction of the time you would otherwise (e.g. writing everything from scratch), then you've spent that much less time (and time == money) to develop it, [i]and[/i] it's live and (hopefully) starting to make a return on the investment you made.
Now, the hard part is knowing how to determine if (a) a CMS can actually do what you want it to, and (b) if so, will it actually save you enough time to make it worthwhile? ?
0
@NogDogAug 18.2016 — #The thing my client would be doing requiring content management is switching out portfolio items (photos and descriptions). What is the alternative to using a CMS for an easy way for a client with no code experience to do that?[/QUOTE]
Which is essentially the gist of any CMS. ? So it likely becomes a case of picking the CMS with the features and look/feel (which can be from 3rd-party templates) that you want. You might want to poke around at opensourcecms.com for some options.
You can, of course, write what would essentially be your own CMS if you only need something really simple that a login system and a few basic forms could do for you. If it's going to be more complex, or your coding skills are not up to that, or time is a constraint, then picking an existing CMS seems logical to me.
0
@NogDogAug 25.2016 — #If you want a facility for a non-technical user to update the site, but you want to code it yourself, then you essentially need to code it as your own CMS. That means adding user login/authentication (so that only authorized users can change the content), and some way for them to actually make the changes. If the layout will stay the same, then all(?) you need are form fields where they can edit the text for the relevant text sections, and upload new images to replace the current ones. Those "pieces" will then likely be stored somewhere (database, config file, etc.?), and then the actual page view would be a script that dynamically loads those pieces in. Let's say you just save the text pieces in 2 files, called text1.txt and text2.txt. In PHP, a simple way to include them would be something like:[code=php]
<!-- some static HTML to start, then -->
<div id="foo">
<p><? php echo nl2br(htmlspecialchars(file_get_contents('text1.txt'))); ?></p>
</div>
<!-- some more static HTML, then -->
<div id="bar">
<p><? php echo nl2br(htmlspecialchars(file_get_contents('text2.txt'))); ?></p>
</div>
<!-- the rest of the static HTML -->
[/code]