QUESTIONNAIRES · SHARED COMPONENTS
Reclamo Studio
Edit presentation and review a service built with the canonical Reclamo library.
Hurto · Spanish questionnaire test
Six content tasks plus Review use Legal’s canonical breakdown, with 19 focused steps and all seven dashboard cards available from the start. The original 14 CMS sections, 24 question IDs and conditions remain separate source data. Files and answers stay in this page and reset on refresh.
Hurto authoring is verified in the explicit local demo and controlled GitHub tests. These new documents must be reviewed and added to the Studio content workspace before live editing; this feature preview does not seed or modify drafts. Existing sample editing remains available.
Try the pilot
- Audit a definition. Download the original sample or the reconstructed Hurto test. These are two explicit test formats; an official CMS structural export is still pending.
- Edit presentation. Choose Service introduction, a task, Review or Help, then English or Español. Open properties and select Page to edit screen text, input labels, descriptions, choice labels, placeholders and positions.
- Save, then wait for the preview build. A saved revision is on GitHub; it is not a completed deployment. The drafts branch rebuilds its own preview. Use the service links to test conditions, validation, task saving, review and capture. They show compiled content.
Audit a JSON file
The original synthetic contract and the screenshot-reconstructed Hurto definition are supported. Selecting a file audits it in your browser; it does not create a branch or trigger a build.
Download the original sample JSON
Choose a file to see its audit.
What is editable
Service introduction owns the notice board. Each task owns its title, description, screen instructions, Save wording and existing input presentation. Review owns its introduction, generated section headings and labels. Help owns its title, content and close wording. Source field identities, answer values, types and rules remain fixed.
Rigel's canvas is script-free and shows all declared conditional fields for editing. Text bindings update there. Placeholder attributes, input positions and Review section order apply after a build; the canvas shows their draft values as editing notes. Saving does not mean that a preview build has finished.
Use Preview on website or the service links for interactions. JSON is audited here; it does not automatically create a new service. GitHub saving and publishing target Studio only. New service definitions require review and an explicit content-workspace promotion.