Issue: portal:

Most of the features needed to do this already exist:
- The DIV BB-Code
- The WIDGET BB-Code (currently supporting results from area/book)

However, in order for editors to design a fully functional portal page, the following already-requested features are still needed:
- Widgets that show feed/category listings
- Widgets that show a preview of the content rather than listing it

Most pages will automatically look like portals when the following is implemented (and the feature is used): https://www.vaultwiki.org/issues/4610/

Of the features needed that haven't yet been requested, see this snippet from a Wikipedia portal page:
Here it looks like we would be displaying content from a feed/area/book/category, but drilling down the results by content-type. This is a filter that isn't yet available on any existing widgets. It also looks like a variable is being used that selects a random sub-node ID from a list of parent nodes.

Thus, this request is left open to handle widget drill-downs and random filter/sort.

I think the approach that mediawiki takes by using wikicode is outdated, compared to adding and saving widgets/Blocks like is done in XF/IPS/VB and also in VW.

CTA FT PORTAL is not often used. While many use CTA FT, less than 10% actually use the portal function. I recently polled this amongst a group of XF webmasters. Most use Widget Framework. Any widget framework renderer can be added to any page including CTA FT Portal.