I'm with Robyn on this one, which is why I recommended you find someone to consult with to analyze your best and most cost effective solution.
The site may already be a type of CMS, and the admin login and some minor training could be all you need. Or it might be a bunch of faux-dynamic, actually-static files that "need" (but not really) a developer to update. Or it could be even more complex. Without looking at the source code, all anyone on this list can do is speculate, which is of minimal help.
Of course the first course of action might be to work with the original design and development team, assuming that is an option for you.
--Sean
On Aug 20, 2015 1:18 PM, <robyn@dcphp.com> wrote:
-- Hi Mel, et al.
I am sorry to disagree with such excellent advice - I know the people here are very smart about strategic thinking. But unless I have missed something, you still don't know what your website is made from or what files are there.
The cost of rebuilding the site is not trivial, and tracking down a user/password would almost certainly be easier. Any coder could probably see a way to view your admin area quite quickly. And after a review of your files and database you could make a far more informed choice.
And here is the thing about rebuilding the site: there are too many unknowns. Are there external links out in the world that point to critical files? Is there a backend database with critical information? Are there users who would be locked out? Are there any other organizational files up on the server that are necessary?
I don't know the answers to these questions, maybe you do, but without them you are opening up costs and risks that have unknown consequences, and that always makes me uncomfortable.
The work that is required to track down these answers might also not be trivial, but it could hardly be more than rebuilding the whole site.
Anyway, best of luck. I agree with folks about how useful Wordpress is. It's a great CMS.
Robyn Wyrick
President, DC PHP, LLC
202-374-4747
robyn@dcphp.com <mailto:robyn@dcphp.com>
"I cherish my kinship with all living beings, particularly Ice Cream."
On Aug 20, 2015, at 7:48 AM, Ray Paseur <ray.paseur@gmail.com <mailto:ray.paseur@gmail.com>> wrote:
Mel, I think your instincts are right about the site, but you won't learn how to do updates and improvements in a small number of man-days; this sort of thing is learned in semesters of college. It would probably be wise to discard what you have here and start over. Here's how the standards organizations see the site:
http://validator.w3.org/nu/?doc=http%3A%2F%2Fwww.millenniumartssalon.org%2F <http://validator.w3.org/nu/?doc=http%3A%2F%2Fwww.millenniumartssalon.
----- Message truncated -----
--
You received this message because you are subscribed to the Google
Group: "Washington, DC PHP Developers Group" - http://www.dcphp.net
To post, send email to washington-dcphp-group@googlegroups.com
To unsubscribe, send email to washington-dcphp-group+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/washington-dcphp-group?hl=en
--- You received this message because you are subscribed to the Google Groups "Washington, DC PHP Developers Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to washington-dcphp-group+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google
Group: "Washington, DC PHP Developers Group" - http://www.dcphp.net
To post, send email to washington-dcphp-group@googlegroups.com
To unsubscribe, send email to washington-dcphp-group+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/washington-dcphp-group?hl=en
---
You received this message because you are subscribed to the Google Groups "Washington, DC PHP Developers Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to washington-dcphp-group+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
0 comments:
Post a Comment