24,089
edits
(Adding some other purposes.) |
No edit summary |
||
Line 27: | Line 27: | ||
A ship website is ''not'' the "end-all, be-all" reference for your ship. There is good reasoning behind this: No matter how easy we make it to update a site, there will always be crews that just don't have anyone who is knowledgeable or motivated enough to help update it. As such, a ship's website will inevitably fall into disrepair which looks bad for our group. We are trying to avoid that at all costs. What the goal should always be, in creating a site, is to set up something that can be static, and still relevant after a long period of time. | A ship website is ''not'' the "end-all, be-all" reference for your ship. There is good reasoning behind this: No matter how easy we make it to update a site, there will always be crews that just don't have anyone who is knowledgeable or motivated enough to help update it. As such, a ship's website will inevitably fall into disrepair which looks bad for our group. We are trying to avoid that at all costs. What the goal should always be, in creating a site, is to set up something that can be static, and still relevant after a long period of time. | ||
{{Taskforces}} | |||
[[Category:Web Development Team|*]] | [[Category:Web Development Team|*]] |