IT reporting website for every day users
-
use any basic wiki they all have an "edit" mode.
Wordpress is real overkill.
Even wiki.js without a super fancy WYSIWYG can easily be formatted. THe need for WYSIWYG is crazy for this. You need very minimal formatting for a simple alert page.
Markdown (what wiki.js uses) woudl be simple for it. No need for a database instance or anything.
-
@JaredBusch said in IT reporting website for every day users:
use any basic wiki they all have an "edit" mode.
Wordpress is real overkill.
Even wiki.js without a super fancy WYSIWYG can easily be formatted. THe need for WYSIWYG is crazy for this. You need very minimal formatting for a simple alert page.
Markdown (what wiki.js uses) woudl be simple for it. No need for a database instance or anything.
My boss specified that he wanted "any user" to be able to edit it. They aren't going to be able to handle markdown. I suggested Bookstack because as far as I have seen its the best wiki with a WYSIWYG editor
-
@wirestyle22 said in IT reporting website for every day users:
@JaredBusch said in IT reporting website for every day users:
use any basic wiki they all have an "edit" mode.
Wordpress is real overkill.
Even wiki.js without a super fancy WYSIWYG can easily be formatted. THe need for WYSIWYG is crazy for this. You need very minimal formatting for a simple alert page.
Markdown (what wiki.js uses) woudl be simple for it. No need for a database instance or anything.
My boss specified that he wanted "any user" to be able to edit it. They aren't going to be able to handle markdown. I suggested Bookstack because as far as I have seen its the best wiki with a WYSIWYG editor
Your boss is an idiot.
"any user" should never do this. it isan IT status page. IT updates it.
-
@JaredBusch said in IT reporting website for every day users:
@wirestyle22 said in IT reporting website for every day users:
@JaredBusch said in IT reporting website for every day users:
use any basic wiki they all have an "edit" mode.
Wordpress is real overkill.
Even wiki.js without a super fancy WYSIWYG can easily be formatted. THe need for WYSIWYG is crazy for this. You need very minimal formatting for a simple alert page.
Markdown (what wiki.js uses) woudl be simple for it. No need for a database instance or anything.
My boss specified that he wanted "any user" to be able to edit it. They aren't going to be able to handle markdown. I suggested Bookstack because as far as I have seen its the best wiki with a WYSIWYG editor
Your boss is an idiot.
"any user" should never do this. it isan IT status page. IT updates it.
Not my choice
-
Also still a wiki. Just a publicly editable one.
which is also stupid.
-
@JaredBusch said in IT reporting website for every day users:
Also still a wiki. Just a publicly editable one.
which is also stupid.
Well he didn't take the suggestion. I said wiki and he said that's not really what he wants.
-
Doesn't change anything I said about stupid.
Day 1: IT enters valid stuff and sends page out to all.
Day 2-10: No one changes anything except IT.
Day 11: Bob from Account Temps has fun on the last day of his contract, but you have no way to know that.
Day 12: Boss implements rule that passwords are required.
Day 13+: no one ever updates it besides IT because password. -
@JaredBusch said in IT reporting website for every day users:
Doesn't change anything I said about stupid.
Day 1: IT enters valid stuff and sends page out to all.
Day 2-10: No one changes anything except IT.
Day 11: Bob from Account Temps has fun on the last day of his contract, but you have no way to know that.
Day 12: Boss implements rule that passwords are required.
Day 13+: no one ever updates it besides IT because password.Oh I see what you think. I didn't mean anyone as in, all users everywhere will be editing. I just mean it can be given and taken away from anyone. My bad. I should've said that differently. Managers will be editing it
-
@wirestyle22 said in IT reporting website for every day users:
@JaredBusch said in IT reporting website for every day users:
Also still a wiki. Just a publicly editable one.
which is also stupid.
Well he didn't take the suggestion. I said wiki and he said that's not really what he wants.
How about a Wiki with a REALLY nice page?
lol
Find a good theme - it can look sorta like a WP page. -
@wirestyle22 said in IT reporting website for every day users:
My boss asked me to design a very neat and professional self-hosted website (probably word press) which my company will use to track outages and issues that have been reported to us in an effort to reduce call volume to our help desk. Do anyone of you have something similar setup or an alternative way to create a better solution?
WordPress is a blogging platform. While it is great, unless you are publishing a blog, it's a bizarre platform to start with for designing a status system.
Microblogging (a la Twitter) is at least way more sensible and while it is still blogging, it is conceptually focused on status, not long format stories.
For people updating general status GNU Social is the obvious choice (formally StatusNet and Laconica.)
-
@wirestyle22 said in IT reporting website for every day users:
Needs to have a WYSIWYG editor.
Under what bizarre conditions would someone add formatted text to a status?
-
@travisdh1 said in IT reporting website for every day users:
@wirestyle22 Do you have monitoring of any type in place currently? Most monitoring solutions should be able to produce a CSV file that you could automatically parse. It's what I'd do anyway.
Many will post to a microblogging platform automatically, too.
-
@wirestyle22 said in IT reporting website for every day users:
@travisdh1 We have solarwinds for IT, but this is for every day people. They can access the website to see what issues have been reported so they don't duplicate calls to the help desk.
Then a wiki with a status page would be logical because you just want IT and no one else giving a status, and you don't want history, just the current state of things.
-
@wirestyle22 said in IT reporting website for every day users:
@IRJ said in IT reporting website for every day users:
@wirestyle22 said in IT reporting website for every day users:
@IRJ Can you provide examples I can test?
It's not something I've worked with for quite a while so I can't really tell you what's the best right now. I'm sure someone on here can chime in. Here are some examples.
Yeah it's too in-depth for what I am looking to do. My boss just wants a list of reported issues.
Application is down in Citrix. We are aware of the issue and are currently working on it.
Internet outage at X site. This is an ISP problem that is being worked on.
It's actually almost more of a blog than it is true reporting
Then a wiki is the sole logical choice. Everything else will be harder, more complicated, and more noisy.
-
@jmoore said in IT reporting website for every day users:
@wirestyle22 I still think Wordpress is what you want for this. Its easy and quick enough for what your describing.
Can't be as good as a wiki. WordPress is built around blogging, not status. Blogs of status would be super weird and confusing. Wordpress can host a wiki, but all that is doing is making a really basic wiki harder than it needs to be.
DokuWiki is perfect here, no database needed.
-
@wirestyle22 said in IT reporting website for every day users:
@IRJ said in IT reporting website for every day users:
@wirestyle22 said in IT reporting website for every day users:
@IRJ said in IT reporting website for every day users:
@wirestyle22 said in IT reporting website for every day users:
@IRJ Can you provide examples I can test?
It's not something I've worked with for quite a while so I can't really tell you what's the best right now. I'm sure someone on here can chime in. Here are some examples.
Yeah it's too in-depth for what I am looking to do. My boss just wants a list of reported issues.
Application is down in Citrix. We are aware of the issue and are currently working on it.
Internet outage at X site. This is an ISP problem that is being worked on.
It's actually almost more of a blog than it is true reporting
Ah ok I see
Zabbix is something I am proposing though just as an FYI
Zabbix is for IT, it would be crazy for end users to see that.
-
@scottalanmiller said in IT reporting website for every day users:
@wirestyle22 said in IT reporting website for every day users:
@IRJ said in IT reporting website for every day users:
@wirestyle22 said in IT reporting website for every day users:
@IRJ said in IT reporting website for every day users:
@wirestyle22 said in IT reporting website for every day users:
@IRJ Can you provide examples I can test?
It's not something I've worked with for quite a while so I can't really tell you what's the best right now. I'm sure someone on here can chime in. Here are some examples.
Yeah it's too in-depth for what I am looking to do. My boss just wants a list of reported issues.
Application is down in Citrix. We are aware of the issue and are currently working on it.
Internet outage at X site. This is an ISP problem that is being worked on.
It's actually almost more of a blog than it is true reporting
Ah ok I see
Zabbix is something I am proposing though just as an FYI
Zabbix is for IT, it would be crazy for end users to see that.
Not as a solution for this request, just in general
-
@Dashrender said in IT reporting website for every day users:
@wirestyle22 said in IT reporting website for every day users:
@IRJ said in IT reporting website for every day users:
@wirestyle22 said in IT reporting website for every day users:
@IRJ Can you provide examples I can test?
It's not something I've worked with for quite a while so I can't really tell you what's the best right now. I'm sure someone on here can chime in. Here are some examples.
Yeah it's too in-depth for what I am looking to do. My boss just wants a list of reported issues.
Application is down in Citrix. We are aware of the issue and are currently working on it.
Internet outage at X site. This is an ISP problem that is being worked on.
It's actually almost more of a blog than it is true reporting
Something simple could easily be static HTML page. But WordPress would likely be easy enough.
Wiki would be better than either. Easier to edit than HTML (WYSIWYG options), way easier than WordPress. And easier to host than WP. And way easier to manage permissions than straight HTML
-
@scottalanmiller said in IT reporting website for every day users:
@Dashrender said in IT reporting website for every day users:
@wirestyle22 said in IT reporting website for every day users:
@IRJ said in IT reporting website for every day users:
@wirestyle22 said in IT reporting website for every day users:
@IRJ Can you provide examples I can test?
It's not something I've worked with for quite a while so I can't really tell you what's the best right now. I'm sure someone on here can chime in. Here are some examples.
Yeah it's too in-depth for what I am looking to do. My boss just wants a list of reported issues.
Application is down in Citrix. We are aware of the issue and are currently working on it.
Internet outage at X site. This is an ISP problem that is being worked on.
It's actually almost more of a blog than it is true reporting
Something simple could easily be static HTML page. But WordPress would likely be easy enough.
Wiki would be better than either. Easier to edit than HTML (WYSIWYG options), way easier than WordPress. And easier to host than WP. And way easier to manage permissions than straight HTML
What wiki would you recommend? I've tried Bookstack and Wiki.js
-
@wirestyle22 said in IT reporting website for every day users:
My boss specified that he wanted "any user" to be able to edit it. They aren't going to be able to handle markdown. I suggested Bookstack because as far as I have seen its the best wiki with a WYSIWYG editor
Well then the whole project is a joke and won't work. Is it status, or is it gibberish? It can't have everyone editing the page AND be any kind of useful status. That's so dumb, stop the project now, it's designed to fail.
