Yes. The two groups have different URL patterns and different page-group configs. They share the same underlying release feed, but each group declares its own grouping rules. Most teams use this exact pairing for cross-referenced archives.

The page-group config defines a grouping rule, typically by date prefix or quarter calculation. The plugin applies that rule when resolving an archive row and pulls in only the matching release rows. The grouping is invisible to the source feed itself.

Yes, on the next cache cycle. The resolved archive row is cached for the duration set in the page-group config. Clearing the items table forces re-resolution, which pulls in any newly published releases in that window.

Yes. The URL is stable and indefinitely addressable. Once a window closes, the archive page becomes a static record of releases shipped in that period. Search engines treat it as evergreen content that stops updating, which is the right model for archives.

The base page reads its column list per row, so each window row can carry its own column definition. In practice teams keep one column shape across the cluster for consistency, but the underlying flexibility is there if you need exceptions.

Most teams keep the old archive URLs alive with redirects and launch the new group at a slightly different prefix, then redirect old to new in bulk. Because SleekRank URLs are stable, the migration is a one-time effort with no ongoing maintenance cost.

Each archive page carries a summary, a contained release list with dates and headlines, and per-window narrative fields. That is enough substance to avoid thin content concerns, especially when the page links to the matching per-release pages in the version group.

Yes. Field mappings can target image tags, chart container divs, or any other element on the base page. Many teams include a small bar chart per window page that shows release counts by type, fed from the same row.