A user on Quora was contemplating a LAN (private) network implementation of an intranet using WordPress. It’s an interesting proposition, so my response may be of interest to others. It is also possible that I completely missed the objectives of the questioner.
In corporate settings, it can be difficult to obtain web server services needed to host a site internally — not technically difficult, but organizationally. So first see if you can gain adequate support to host and service a site internally.
If yes, then one would want to verify that by “blocked from internet service,” you mean it is not available on the public internet. You can have your IT folks host a site that is not available to the public, but it will need internet access itself to update plugins and to access the content you are speaking of — which probably is hosted offsite on public sites. You can download everything to your own site but that’s a lot of work that involves some nontrivial effort.
So I’m assuming you mean locally hosted on your own network, but with access after login to the internet.
I think this will confuse you, but there are some proxy services for WordPress to address some of the issues that arise with such an approach.
10 Amazing WordPress Proxy Plugins
You will need some initial IT help to do this, and ongoing support for maintaining the web site (Apache or IIS), network security for new user access, language updates for PHP, and access to a MySQL database — usually a separate server except for small sites. If your IT folks are OK with this, you are probably golden, but in many organizations where WordPress is not a mainstream app, you face many hurdles: as mentioned, most of them not technical.
For example, IT may identify you as a nontechnical user for whom they will have to budget additional labor for hand-holding and maintenance, such as to install new plugins, perform backups or roll back changes. Every app has a coattail effect for maintenance and training. In smaller organizations folks are willing to take this collateral duty on. In larger ones, they’ll be rightfully concerned about what they’re getting into — especially if you have no budget yourself and may abandon the project after they’ve set everthing up for you.
On the outside chance that you are wildly successful, IT will have to figure out how to scale up resources that were probably allocated for a modest project. This is a small problem for cloud infrastructure, but you’re probably speaking of in-house resources.
WordPress is fantastic for many things. When used out of the box as an intranet though, it lacks the portal capabilities of Sharepoint or Java’s JSR 168 / 286 interop standards. So it’s easy to add WordPress building blocks to WordPress, but less easy to add non-WordPress features. Example: If you add your HR system or expense reporting system through the intranet, users will probably have to sign in again and in a separate window. This is hardly better than launching the app from a browser bookmark or link on an intranet web page.
It works as a front end (very loosely speaking) to other enterprise assets, but the app itself lacks the extensibility and familiarity that would make in-house developers working in node.js and other tools of recent vintage happy. This is why you won’t see much interop between The Official Microsoft ASP.NET Site (another widely adopted platform standard) and WordPress — even when hosted on Microsoft web servers. Which is a shame.