I need your thoughts on something I can kludge together to contain documents and procedures for technicians in a small business environment (60). These are the three on my mind but I'm willing to look at anything.
Wiki
-Seems available and decent choice for a CMS
-I'm not sure if I could maintain it on the back end but never tried.
-free
vBulletin like this site here
-Love using vBulletin sites
-Sort of kills two birds with one stone, we would now have a place for our techs to interact which has been asked for
-Not sure how hard it is to maintain, backups and fixing problems etc?
-$? not sure that's a concern
Microsoft Sharepoint
-used this at another company and it worked
-ran into weird problems when we moved out of its comfort zone doing things it isn't meant for like storing files
One HUGE advantage; for the moment at least the site will only be visible inside the network and won't be exposed to the big bad internet. Hoping that will protect us from security issues though we won't have anything too secret on the site. Though it would be super nice if the system lent itself to being able to face the public internet for convenience sake in the future if we wanted to.
Background:
At my last company I wrote and organized a lot of internal procedures and documentation. There we had a custom CMS that someone else was responsible for. I do NOT want to go the custom route, the system needs to be maintainable by me. I'm not afraid to RTFM and edit config files but if I have to debug some code things are going to go badly. Small amount of experience in Microsoft SQL and MySQL, even less in PostgreSQL.
Now at my new job I'm doing much the same but now I run the CMS. At the moment it is a super simple HTML put together in notepad running on Nginx because it was quick and easy. Right now honestly it looks bad and while easy to maintain I'm the sole gateway to getting information on it, there is zero collaboration and stuff is going to get hard to find quick.
Wiki
-Seems available and decent choice for a CMS
-I'm not sure if I could maintain it on the back end but never tried.
-free
vBulletin like this site here
-Love using vBulletin sites
-Sort of kills two birds with one stone, we would now have a place for our techs to interact which has been asked for
-Not sure how hard it is to maintain, backups and fixing problems etc?
-$? not sure that's a concern
Microsoft Sharepoint
-used this at another company and it worked
-ran into weird problems when we moved out of its comfort zone doing things it isn't meant for like storing files
One HUGE advantage; for the moment at least the site will only be visible inside the network and won't be exposed to the big bad internet. Hoping that will protect us from security issues though we won't have anything too secret on the site. Though it would be super nice if the system lent itself to being able to face the public internet for convenience sake in the future if we wanted to.
Background:
At my last company I wrote and organized a lot of internal procedures and documentation. There we had a custom CMS that someone else was responsible for. I do NOT want to go the custom route, the system needs to be maintainable by me. I'm not afraid to RTFM and edit config files but if I have to debug some code things are going to go badly. Small amount of experience in Microsoft SQL and MySQL, even less in PostgreSQL.
Now at my new job I'm doing much the same but now I run the CMS. At the moment it is a super simple HTML put together in notepad running on Nginx because it was quick and easy. Right now honestly it looks bad and while easy to maintain I'm the sole gateway to getting information on it, there is zero collaboration and stuff is going to get hard to find quick.