Synopsis [Edit]

PageWork has many competitors – or rather, brothers and sisters, that is, alternatives to choose from. It has therefore three explicit design goals that characterize its intended standing among its siblings.

PageWork is designed to be fast and efficient in what it does.
As opposed to complex and confusingly structured.
Adaptable to personal needs, and easily extendable with regard to its functionality.

The first two goals, mostly self-explanatory in themselves, envision a clearly designed, light weight software package with a low latency in comparison to a bloated, resource hungry environment that takes a system administrator weeks to comprehend and customize. It also means that PageWork is comparatively frugal when it comes to system requirements. It does not require a RDBMS, nor exclusive hardware to run on.

Feature richness, too, is a desirable goal (it always is), but easily folds into a path that leads away from efficiency and clearness. This is where the third axiom comes in. PageWork is designed to be immediately adaptable to most requirements, and extendable to meet specific scenarios.

PageWork stores most dynamic data in schema free, document orientated data records that are built on top of a native key-value store. This choice of storing data contributes to the intended design goal of efficiency and simplicity of the underlying database.

Feature Summary [Edit]

  • Light weight storage back-end
  • Wiki farming
  • Site access management
  • Revision control/versioning for all managed resources
  • Online configuration customization with revision control
  • Online backup/restore functionality
  • Visualization of page changes
  • Localization
  • Localized content indexing
  • Editing tools and GUI
  • Variable page and image caching
  • Media management
  • Tags
  • Users
  • User groups
  • Resource access management/ACL based on users and groups
  • Breadcrumbs (recently visited pages)
  • Personal configuration
  • Personal bookmarks
  • Personal memos
  • Page templates
  • Customizable and extendable editing syntax
  • SEO
  • Meta data management for all resources
  • Comments/discussion for all resources (“talk”)
  • Management of deleted resources (“dump”)
  • Namespaces
  • Aliases
  • Front-end/back-end separation
  • Atom/RSS feed
  • Tools to detect broken links and orphaned resources
  • XHTML and CSS2 compliant output