All widgets on this page (current-issue/in-press/top/editor's-choice article tabs, facts & figures, publication info, indexing, ads, keyword cloud, related journals, footer news/newsletter/social) are settings-driven sections of one composite screen rendered by themes/<theme>/front/pages/index.php — none is reachable at its own distinct _action/route, so they are documented as one "Home" row rather than split into per-section rows. Other _action values handled by the same index.php dispatcher (advSearch, article/press, articleInfo, linkout, current) render materially different screens and belong to the Search and Issues & Articles modules, not Home.

case "cite": in index.php only delegates to ArticleCitation::manageActions() → getScoupsCitation() (class/article.citation.class.php), which does echo json_encode($ret) — a live Scopus citation-count JSON lookup with no page-template load, running after the switch has already started emitting the page shell, so it can't render a standalone screen either. Grepping the whole legacy tree (excluding vendor/tinymce) for this action turns up zero callers anywhere; it looks unreachable in practice. Per this segment's own "pure handler, no rendered screen" rule (see journal/issues-articles.html's identical treatment of XML export), it is correctly excluded from row consideration in every module, not folded into Search/Issues & Articles as the previous version of this note implied.

The design brief's suggested anchors apps/legacy/js/mainm/index.php and apps/legacy/js/mainn/index.php were traced and found to not be per-journal Home implementations — both hardcode journal_code = 0 and reproduce the cross-journal directory-listing pattern of the Portal segment's main/index.php (journal search/filter grid, "journals list" browsing, static "menu" pages, embedded contact blurb, RSS, year archive), rather than a single journal's themed home page. Per the design doc's segment table, mainm/mainn public dispatch is explicitly sourced under the Journal segment (not Portal); portal/journals.html and portal/landing.html both decline to claim it for that reason. Since it renders a materially different, still-live screen (see below) with no row anywhere in the inventory, leaving it as an inline flag rather than a claimed row was a Definition-of-Done gap — it is now captured above as its own "Cross-Journal Directory" row, bundling the settings-driven menu/highlights/contact/rss/years sub-views the same way the Home row bundles its own widgets, since none of them is reachable at its own distinct _action either.

apps/legacy/spec/auth/public-private-files.md discusses mainm/jufile.php's payment-receipt access-control gap, confirming the mainm tree is still served in production. apps/legacy/apache-httpd/httpd-vhosts.conf maps mainm as the DocumentRoot for the journals.ekb.eg/journal.ekb.eg vhost (plus its bare-IP alias) — i.e. the root portal domain, not any per-journal tenant subdomain (per-journal subdomains are ServerAlias entries on the separate j.ekb.eg vhost whose DocumentRoot is the top-level journals/ dir housing the real per-journal index.php claimed as "Home" above); mainn has no vhost entry of its own and is only reachable as a public subdirectory under that same top-level docroot. That vhost mapping — mainm serving the portal domain — is in tension with the design doc's segment table filing "mainm/mainn public dispatch" under Journal rather than Portal; this row follows the design doc's documented assignment, but the tension is a genuine open question for Phase C triage, not resolved here.

apps/legacy/js/view/index.view.php (also named as a likely anchor) is unrelated to the public Home page — it renders the admin CRUD screens (list/add/edit) for indexing-database entries via class/index.class.php, i.e. the back-office source for the public "Indexing" widget shown here, not a Home page itself.