The idea of Static Content Blog or Static Content Wiki widget is to display a specific entry from a blog (= post) or wiki (= page). This works fine without personalization.
When personalization is enabled, the current implementation in Static Content Blog or Static Content Wiki widget only allows to "personalize" the Blog or Wiki as content source. The option to select a specific entry is no longer available. Instead, the "Static Content" widget displays the latest entry from the specific blog or wiki. This is not really static, actually unusable for wiki as every change in the corresponding wiki would lead to a different displayed content. Finally, the "Static Content Blog" widget becomes like a News widget displaying the latest blog post.
Personalization in Static Content Wiki (or Blog) widget should allow which static wiki page (or blog post) is displayed from a specific wiki (blog).
If the implementation is either
a) define wiki as content source and use personalization to select a specific wiki page within that wiki
or
b) use personalization to select both a specific wiki and a wiki page inside that wiki is up to HCL.
Of course, option a) limits it to a single wiki, while option b) is more flexible. It allows a better separation and management of content in multiple content sources.
Concrete customer use case: Based on profile field "location", customer wanted to display site-specific information on ICEC page using "Static Content Wiki" widget.
