# Quality Assessment Space 6/10

## Space quality assessment

### Overall result

**Space rating: 6/10**

This space is useful and mostly navigable.

Its strongest content is the core XPI, Forms Processor, and WIC reference material.

Its weakest content is the legacy import area.

That area still carries file-name titles, thin landing pages, imported document artifacts, weak hierarchy, and older footer or link patterns.

### Query used

> Using the GitBook Knowledge Space and the page on Content Quality Guide at this location `https://app.gitbook.com/o/uOpE0pwQaikBOHcfkMgY/s/YxYaIQQ51Y1kp5Oav4GZ/content-quality-guide`, 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 Space 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 and query to that page, exclude all hidden content from the assessment, and exclude the Quality Assessment and groups. Once the page has been written hide the group Space Quality Assessment.

### Scope

* Included only pages visible in the navigation at review time.
* Excluded hidden content.
* Excluded groups.
* Excluded this assessment section.

### Scoring method

Each page was checked against the quality guide across these categories:

* Standards and reusable structure
* User purpose and audience fit
* Accuracy, completeness, and asset quality
* Headings, hierarchy, and scannability
* Link quality and navigation support
* SEO and discoverability
* AI readability and explicit structure

The guide uses a 0 to 5 scale per category.

That score was normalized to a 1 to 10 page rating.

### Category scores

* Standards and structural consistency: 6/10
* Purpose and audience fit: 7/10
* Accuracy and completeness: 7/10
* Headings and scannability: 6/10
* Links and navigation support: 6/10
* SEO and discoverability: 5/10
* AI readability: 6/10

### Top issues

1. Legacy imported pages still use file names as titles.
2. Several landing pages are too thin.
3. Release notes remain long, noisy, and hard to scan.
4. Heading hierarchy is inconsistent across older sections.
5. Some older content still points to external Verifone web pages or includes footer artifacts.

### Actionable fixes

1. Rename imported pages to task-based, user-facing titles.
2. Replace thin landing pages with short purpose-led summaries.
3. Split release notes into one page per release.
4. Remove imported footer


---

# 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/xpi/space-quality-assessment/quality-assessment-space-6-10.md?ask=<question>
```

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.