Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Web portal
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
===Corporate=== {{Main|Intranet portal}} Corporate intranets became common during the 1990s. As intranets grew in size and complexity, organization webmasters were faced with increasing content and user management challenges. A consolidated view of company information was judged insufficient; users wanted personalization and customization. Webmasters, if skilled enough, were able to offer some capabilities, but for the most part ended up driving users away from using the intranet. Many companies began to offer tools to help webmasters manage their data, applications and information more easily, and by providing different users with personalized views. Portal solutions can also include workflow management, collaboration between work groups or branches, and policy-managed content publication. Most can allow internal and external access to specific corporate information using secure authentication or [[single sign-on]]. JSR168 Standards emerged around 2001. Java Specification Request (JSR) 168 standards allow the interoperability of [[portlets]] across different portal platforms. These standards allow portal developers, administrators and consumers to integrate standards-based portals and portlets across a variety of vendor solutions. The concept of content aggregation seems to still gain momentum and portal solution will likely continue to evolve significantly over the next few years. The [[Gartner Group]] predicts generation 8 portals to expand on the [[Business Mashups]] concept of delivering a variety of information, tools, applications and access points through a single mechanism.{{Citation needed|date=April 2009}}{{Better source|date=July 2019}} With the increase in [[user-generated content]] (blog posts, comments, photos), disparate data silos, and file formats, information architects and taxonomists will be required to allow users the ability to tag (classify) the data or content. For example, if a vice-president makes a blog post, this post could be tagged with their name, title, and the subject of the post. Tagging makes it easier for users of the intranet to find the content they are interested in. This will ultimately cause a ripple effect where users will also be generating ad hoc navigation and information flows. Corporate portals also offer customers and employees self-service opportunities.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)