# Quality Assessment Rating 6.2/10 ## Quality assessment summary * Overall rating: **6.2/10** * Overall score: **6.2/10** * Pages reviewed: **52 visible document pages** * Excluded: hidden content, group pages, and the assessment section ### Query > Using the GitBook Knowledge Space and the page on Content Quality Guide at this location\ > , give me a rating from 1 to 10 for all the pages in this space that are not hidden, 1 being does not follow the quality guide at all, and 10 being the quality guide is completely followed.\ > Create a page titled Quality Assessment Rating/10, with an icon memo-circle-info at the bottom of the space under a group named Space Quality Assessment, that has a medal icon. Copy all of the assessment information & query to that page, exclude all hidden content from the assessment, and exclude the Quality Assessment and groups. Ensure the page has an overall rating\score, and update the name of the page with that rating. Once the page has been written hide the group Space Quality Assessment. ### Rubric used Scores reflect four guide-aligned quality signals: * Clear purpose, audience, and scope * Complete task flow, prerequisites, and outcomes * Scannability, consistency, and editorial polish * Linking, maintenance signals, and modern GitBook structure ### Page-by-page scores * **8/10** — [Feature References](/feature-references/feature-references.md): Strong landing page with clear purpose, browse paths, and related links. * **6/10** — [AEOD](/feature-references/feature-references/aeod.md): Clear topic scope, but likely follows an older single-page reference pattern. * **6/10** — [Age Restriction](/feature-references/feature-references/age-restriction.md): Usable feature coverage, but limited evidence of modern navigation aids. * **6/10** — [App Selector](/feature-references/feature-references/app-selector.md): Clear topic framing, but likely light on context layers and cross-links. * **7/10** — [Auto Upgrade](/feature-references/feature-references/auto-upgrade.md): Stronger setup and operational value than the average legacy feature page. * **7/10** — [Auxiliary Forecourt Point of Sale](/feature-references/feature-references/auxiliary-forecourt-point-of-sale.md): Specific value proposition and likely practical task coverage. * **7/10** — [Bluefin Encryption](/feature-references/feature-references/bluefin-encryption.md): Strong problem framing and current compliance context improve quality. * **5/10** — [Car Wash Pay Point](/feature-references/feature-references/car-wash-pay-point.md): Thin surfaced framing and fewer quality signals than stronger pages. * **6/10** — [Cash Rounding](/feature-references/feature-references/cash-rounding.md): Clear use case, but likely still follows legacy reference conventions. * **5/10** — [Charity Donations](/feature-references/feature-references/charity-donations.md): Minimal surfaced context suggests thinner editorial treatment. * **6/10** — [Coupon Scanning](/feature-references/feature-references/coupon-scanning.md): Purpose is clear, but polish appears closer to older reference content. * **7/10** — [Cullinan Financial Transaction Services](/feature-references/feature-references/cullinan-financial-transaction-services.md): Good configure, use, and report framing improves usability. * **6/10** — [Digital Video Recorder (DVR)](/feature-references/feature-references/digital-video-recorder-dvr.md): Complete but dated, with dense legacy formatting and tables. * **5/10** — [EBT Transactions](/feature-references/feature-references/ebt-transactions.md): Actionable, but inconsistent formatting and weak feature framing reduce quality. * **5/10** — [Enhanced System Monitoring](/feature-references/feature-references/enhanced-system-monitoring.md): Limited surfaced context suggests lighter structure and polish. * **6/10** — [EMV - Inside EMV](/feature-references/feature-references/emv-inside-emv.md): Likely comprehensive, but probably dense and legacy in presentation. * **4/10** — [EMV - Outside EMV](/feature-references/feature-references/emv-outside-emv.md): Comprehensive but hard to scan, with duplication, dated structure, and broken markup. * **7/10** — [EPS Loyalty](/feature-references/feature-references/eps-loyalty.md): Updated and thorough, but still long and dense. * **6/10** — [Fleet Cards - ExxonMobil](/feature-references/feature-references/fleet-cards-exxonmobil.md): Targeted and useful, but closer to older reference style. * **7/10** — [Fleet Cards - General Fuel Configuration & Usage](/feature-references/feature-references/fleet-cards-general-fuel-configuration-and-usage.md): Likely foundational and broadly reusable across related tasks. * **6/10** — [Fleet Cards - Commander Fleet](/feature-references/feature-references/fleet-cards-commander-fleet.md): Current and specific, but heavy tables and troubleshooting density reduce clarity. * **6/10** — [Full Service Attendant](/feature-references/feature-references/full-service-attendant.md): Good scope, but likely still organized as a legacy feature reference. * **6/10** — [Group Price Change](/feature-references/feature-references/group-price-change.md): Step-based and usable, but older framing and limited connective structure hold it back. * **8/10** — [InComm](/feature-references/feature-references/incomm.md): Strong multipart hub structure makes the content easier to enter and navigate. * **7/10** — [Configuring InComm](/feature-references/feature-references/incomm/configuring-incomm.md): Focused task page with likely strong procedural value. * **7/10** — [Using InComm](/feature-references/feature-references/incomm/using-incomm.md): Clear operational focus improves readability and task success. * **7/10** — [Reporting InComm](/feature-references/feature-references/incomm/reporting-incomm.md): Narrow scope helps this page stay practical and readable. * **6/10** — [In-House Accounts](/feature-references/feature-references/in-house-accounts.md): Likely useful but still closer to legacy product-reference conventions. * **6/10** — [Kitchen Printer](/feature-references/feature-references/kitchen-printer.md): Thorough, but very long and repetitive for modern scanning. * **6/10** — [Manager WorkStation](/feature-references/feature-references/manager-workstation.md): Likely adequate task coverage with older presentation patterns. * **6/10** — [Mobile Payments](/feature-references/feature-references/mobile-payments.md): Clear summary, but likely limited modern content design elements. * **6/10** — [MoneyOrder](/feature-references/feature-references/moneyorder.md): Straightforward feature reference with standard legacy structure. * **6/10** — [Open PLU](/feature-references/feature-references/open-plu.md): Clear task flow, but older formatting and wording issues reduce polish. * **5/10** — [ORPAK AVI/RFID Fueling](/feature-references/feature-references/orpak-avi-rfid-fueling.md): Thin surfaced context suggests weaker framing and scannability. * **6/10** — [Password Reset](/feature-references/feature-references/password-reset.md): Useful and task-oriented, but legacy anchors and inconsistent formatting remain. * **5/10** — [POS Cashier Display Message](/feature-references/feature-references/pos-cashier-display-message.md): Minimal surfaced structure suggests lighter editorial refinement. * **8/10** — [POP Discount](/feature-references/feature-references/pop-discount.md): Strong multipart split improves discoverability and task flow. * **7/10** — [Configuring POP Discount](/feature-references/feature-references/pop-discount/configuring-pop-discount.md): Focused setup guidance makes the page easier to use. * **7/10** — [Using and Reporting](/feature-references/feature-references/pop-discount/using-and-reporting.md): Good task separation and outcome focus. * **5/10** — [POS Pairing](/feature-references/feature-references/pos-pairing.md): Editorial issues are visible even in the summary, which lowers confidence and polish. * **5/10** — [Proprietary FEP Interface](/feature-references/feature-references/proprietary-fep-interface.md): Likely specialized and useful, but harder to enter and scan. * **6/10** — [Receipt Reprint](/feature-references/feature-references/receipt-reprint.md): Clear use case, but still presented in a legacy reference style. * **7/10** — [Release 53 & Higher UI Reference](/feature-references/feature-references/release-53-and-higher-ui-reference.md): Likely a strong reference anchor across the section. * **6/10** — [Self Checkout](/feature-references/feature-references/self-checkout.md): Relevant and useful, but likely still follows older documentation conventions. * **6/10** — [Signature Capture](/feature-references/feature-references/signature-capture.md): Understandable and task-based, but dated wording and limited context layering reduce quality. * **6/10** — [Shell Card Pricing](/feature-references/feature-references/shell-card-pricing.md): Clear problem framing, but likely older layout and guidance patterns. * **7/10** — [Special Discounts](/feature-references/feature-references/special-discounts.md): Solid overview, related-topic links, and full task coverage lift quality. * **7/10** — [Tipping](/feature-references/feature-references/tipping.md): Recent and relevant, but inconsistent capitalization and dense setup copy reduce polish. * **6/10** — [TransArmor: Verifone Edition (TAVE)](/feature-references/feature-references/transarmor-verifone-edition-tave.md): Likely complete, but still aligned to a traditional reference format. * **5/10** — [Unattended Fueling](/feature-references/feature-references/unattended-fueling.md): Thin surfaced context suggests weaker structure and discoverability. * **6/10** — [VIP NAXML Mix & Match](/feature-references/feature-references/vip-naxml-mix-and-match.md): Detailed and useful, but long, dense, and legacy-styled. * **6/10** — [Zebra Scanners](/feature-references/feature-references/zebra-scanners.md): Likely focused hardware guidance, but narrower context and older structure limit score. ### Notes * Hidden content was excluded from the assessment scope. * Group pages were excluded from scoring. * Scores are comparative within this space, not certification results. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.verifone.com/feature-references/space-quality-assessment/quality-assessment-rating-6.2-10.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.