After a respondent completes the MPADQ questionnaire, the results page assembles a personalized report by weaving their numeric scores together with explanatory prose pulled from the database. This interpretation text — which provides context before each score and guidance after it — is fully editable through the admin dashboard atDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/ijmeisner/einerlei/llms.txt
Use this file to discover all available pages before exploring further.
/admin/dashboard/understanding-your-scores-edit/. No database client or developer access is required to revise it.
Score Text Structure
The results page organizes scores at two levels of granularity, and each level has its own database table and editing interface.Broad Categories
Two top-level groupings — Symptomatology and Contributing Factors — each with introductory and interpretive text stored in
LikertAnswerBroadCategory.Sub-Categories
Twenty-four sub-categories nested under the broad categories (e.g., Physical Symptoms, Perfectionism and Self-Criticism, The Audition Factor), each with its own text stored in
LikertAnswerSubCategory.Database Schema
Both tables share the same structure, withtext_area1 and text_area2 holding the editable interpretation text:
| Field | Purpose |
|---|---|
text_area1 | Introductory or context text displayed before the user’s score for that category. |
text_area2 | Interpretation text displayed after the user’s score for that category. |
Navigating to Edit Score Text
From the admin dashboard, click the Edit Understanding Your Scores Text link. The page at/admin/dashboard/understanding-your-scores-edit/ presents two separate selection forms:
- Select a Broad Category — a dropdown populated from
LikertAnswerBroadCategory(id,category) - Select a Sub Category — a dropdown populated from
LikertAnswerSubCategory(id,category)
Editing Broad Category Text
The two broad categories are Symptomatology and Contributing Factors, seeded into the database as:Select a broad category
On the Edit Understanding Your Scores Text page, use the Select a Broad Category dropdown to choose either Symptomatology or Contributing Factors, then click Edit.
Edit the two text areas
You are redirected to
/admin/dashboard/understanding-your-scores-edit/edit-broad/. The page receives the selected id via POST, queries text_area1, text_area2, and category from LikertAnswerBroadCategory, and pre-fills both multi-line text areas.- Upper text area (
text_area1) — Write the introductory text that appears before the user’s broad category score. - Lower text area (
text_area2) — Write the interpretation text that appears after the score. The page labels this area: “The following text is displayed after a user’s score for [Category].”
Submit your changes
Click Submit. The form POSTs
first, second, id, and a hidden cat_type field set to Broad to /admin/dashboard/understanding-your-scores-edit/confirm/. The confirm page applies the following sanitization to both fields before writing:real_escape_string()— escapes SQL special charactersstripslashes()— removes escape slasheshtmlentities()— converts special characters to HTML entitiesstrip_tags()— strips any HTML or PHP tags
UPDATE statements are then executed:Editing Sub-Category Text
There are 24 sub-categories in total. Three fall under Symptomatology:- Physical Symptoms
- Cognitive Symptoms
- Behavioral Symptoms
- Student-Teacher Relationship
- Sense of Belonging at School/Career
- Generalized Anxiety and Stress
- Perfectionism and Self-Criticism
- Self-Concept of Performance Ability and Confidence
- Self-Esteem
- Self-Concept of Long-Term Stakes
- Personal Support Structure in People and Activities
- Security, Happiness and Support in Romantic Relationships
- Physical and Emotional Health
- Spiritual and/or Religious Support System and/or Beliefs
- Feelings of Being Out-of-Control
- Controlling Personality and Competitiveness
- Self-Concept of Anxiety
- Self-Concept of Focus
- Self-Concept of Musical and/or Performance Preparation
- Conflict Resolution Inclination
- Introversion
- General Negativity
- Personal Drive/Motivation
- The Audition Factor
Select a sub-category
On the Edit Understanding Your Scores Text page, use the Select a Sub Category dropdown to choose the sub-category you want to update, then click Edit.
Edit the two text areas
You are redirected to
/admin/dashboard/understanding-your-scores-edit/edit-sub/. The page receives the selected id via POST, queries text_area1, text_area2, and category from LikertAnswerSubCategory, and pre-fills the same two text areas:- Upper text area (
text_area1) — Introductory text shown before the user’s sub-category score. - Lower text area (
text_area2) — Interpretation text shown after the score. The page labels this: “The following text is displayed after a user’s score for [Sub-Category].”
Submit your changes
Click Submit. The form POSTs to
/admin/dashboard/understanding-your-scores-edit/confirm/ with cat_type set to Sub. The confirm page sanitizes both fields using the same pipeline as broad category edits, then runs:Text changes take effect immediately for all users. There is no draft or staging mode — once you click Submit on the edit form, the updated text is live in the database and will be served by the results page on the next page load.
Writing Effective Interpretation Text
Keep the following guidelines in mind when drafting or revising score text:| Field | Recommended Content |
|---|---|
text_area1 | Define what the category measures. Briefly describe the behaviors, thoughts, or experiences it captures. Keep it neutral and educational — the user has not yet seen their score. |
text_area2 | Interpret the score in context. Acknowledge the range of possible outcomes and what each implies. Avoid language that could feel stigmatizing; instead, frame findings as areas of awareness and growth. |
The sanitization pipeline on the confirm page (
htmlentities() + strip_tags()) removes all HTML markup from saved text. Do not attempt to embed HTML formatting such as <b>, <em>, or <br> tags — they will be stripped before the value reaches the database. Use plain prose only.