@formique/semantq
| Install | |
|---|---|
npm install @formique/semantq |
|
| Latest Version: | 1.1.13 |
| Vue: | 3 |
| License: | MIT |
| Last Updated: | Sep 26, 2026 |
| Links: | GitHub · npm |
Formique-Semantq
Table of Contents
- About Formique Semantq
- Features
- Installation
- Quick Start
- Form Schema Guide
- Submission & Lifecycle
- Styling Guide
- Email Forms
- Domain Verification
About Formique Semantq
Formique Semantq is a native Semantq JS framework Schema Definition Language (SDL) and Formique Form Definition Language (Low Code). The library is a robust and elegant Web Content Accessibility Guidelines (WCAG) and Web Accessibility Initiative – Accessible Rich Internet Applications (WAI-ARIA) compliant form-building library tailored for JavaScript enthusiasts. It supports a wide array of input types, features JavaScript-driven themes, and offers advanced functionalities like nested conditional logic and dynamic dropdowns. Highly customizable and extensible, Formique is built for the Semantq JS Framework but integrates seamlessly with Vanilla JS, Semantq, and Vue. This guide covers implementing Formique in Semantq.
Features
- Declarative Syntax: Define forms using a simple and intuitive schema.
- Wide Range of Inputs: Supports text, email, number, password, date, time, file uploads, and more.
- HTML Content Blocks: Insert custom HTML or plain text anywhere in your form.
- Validation and Attributes: Easily specify validation rules and attributes for each form field.
- Dynamic Form Generation: Generate forms dynamically based on your schema.
- Framework Agnostic: Currently works with Semantq and Vanilla JS (more frameworks to be added).
- Accessibility and Usability Compliant: Formique yields form markup compliant with WCAG.
- Mobile Responsive: Forms are mobile responsive out of the box.
- Nested Dynamic Conditional Logic: Implement complex conditional logic to show or hide form fields based on user input.
- Dynamic Dropdowns: Create dropdowns whose options change dynamically based on other field selections.
- JavaScript-Driven Themes: Apply themes or theme colors dynamically using JavaScript for a customizable user interface.
- WAI-ARIA and WCAG-Compliant HTML: Ensure all form elements are accessible and meet WCAG standards.
- Progressive Enhancement: Forms function with or without JavaScript, ensuring accessibility and functionality across all environments.
- Configurable Loading, Success & Error States: Customize the spinner text and on-page result messages shown during and after submission.
- Submission Lifecycle UI: Formique renders loading, success, and error states as part of its managed submission lifecycle.
- Integration with
@semantq/qlForm: When configured without an explicit endpoint, Formique listens toform:processing,form:success, andform:errorevents and drives its own UI. - Externally Managed Submissions: Applications can own the API request entirely — Formique will not issue a second HTTP request when no explicit
formParams.actionis configured.
How to Install Formique in Semantq
Step 1: Install Semantq
Create a new Semantq project using the following commands:
# install semantq globally
npm i -g semantq
# create a new project in my-app
semantq create my-app
Note: Always refer to the latest official Semantq guide on how to create a Semantq app, as this may change. Semantq Documentation: Creating a Project
Step 2: Install Formique
npm i @formique/semantq
Step 3: CSS Styling (Optional)
Formique now automatically injects its internal styles by default - no additional CSS files needed! The library handles styling internally with built-in themes and CSS variables.
Using Built-in Styles (Default)
Formique automatically applies its styling system. Just use the theme or themeColor options in your formSettings:
const formSettings = {
theme: 'midnight-blush', // Apply a built-in theme
// OR use a custom color:
themeColor: '#4338ca' // Override with your own hex color
};
Disabling Default Styles
If you prefer to use your own custom CSS, you can disable Formique's internal styles:
const formSettings = {
disableStyles: true, // Prevents internal CSS injection
// Now you can provide your own CSS file or styles
};
When disableStyles: true is set, Formique will not inject any styles, giving you complete control over the form's appearance. You can then link your own CSS file:
<!-- Your custom CSS -->
<link rel="stylesheet" href="/path/to/your-custom-form-styles.css" />
Why This Change?
- Zero configuration: Forms look great out of the box
- Reduced dependencies: No need to manage separate CSS packages
- Better performance: Styles are injected efficiently
- Theming flexibility: Built-in themes and CSS variables work seamlessly
- Opt-out option: Full control when you need it
- Eliminates FOUC (Flash of Unstyled Content): Styles are injected before form rendering, ensuring the form appears fully styled immediately
Demo: Creating a New Route in Semantq for Formique
Step 1: Create a New Route
semantq make:route registration
Step 2: Implement the Form
@script
import Formique from '@formique/semantq';
const formSchema = [
['text', 'name', 'Name', { required: true }],
['text', 'surname', 'Surname', { required: true }],
['email', 'email', 'Email', { required: true }],
['submit', 'submit', 'Submit', {}, { style: 'width: 100%;' }],
];
const formParams = {
id: "regForm",
method: "POST",
};
const formSettings = {
submitOnPage: true,
theme: "midnight-blush",
requiredFieldIndicator: true,
placeholders: true,
};
$onMount(() => {
const form = new Formique(formSchema, formParams, formSettings);
});
@end
@html
<div id="formique"></div>
Form Schema Guide
Formique uses a simple, intuitive array-based schema to define forms. Each field follows this format:
[type, name, label, validation, attributes, options]
Standard Input Fields
[
['text', 'username', 'Username', { required: true, minlength: 3 }],
['email', 'user_email', 'Email Address', { required: true }],
['password', 'user_pass', 'Password', { required: true, minlength: 8 }],
['number', 'age', 'Age', { min: 18, max: 99 }],
['tel', 'phone', 'Phone Number', { pattern: '[0-9]{3}-[0-9]{3}-[0-9]{4}' }],
['date', 'dob', 'Date of Birth'],
['time', 'appointment', 'Appointment Time'],
['color', 'fav_color', 'Favorite Color', {}, { value: '#ff0056' }],
['file', 'avatar', 'Profile Picture', { accept: 'image/*' }],
['textarea', 'bio', 'Biography', { maxlength: 500 }, { rows: 5 }],
['url', 'website', 'Personal Website'],
['search', 'search', 'Search'],
]
Radio & Checkbox Groups
// Radio buttons (single selection)
[
'radio', 'gender', 'Gender', { required: true }, {}, [
{ value: 'male', label: 'Male' },
{ value: 'female', label: 'Female' },
{ value: 'other', label: 'Other' }
]
],
// Checkbox group (multiple selection)
[
'checkbox', 'interests', 'Interests', {}, {}, [
{ value: 'coding', label: 'Coding', selected: true },
{ value: 'design', label: 'Design' },
{ value: 'music', label: 'Music' }
]
]
Select Dropdowns
// Single select
[
'singleSelect', 'country', 'Country', { required: true }, {}, [
{ value: 'us', label: 'United States', selected: true },
{ value: 'uk', label: 'United Kingdom' },
{ value: 'ca', label: 'Canada' }
]
],
// Multiple select
[
'multipleSelect', 'skills', 'Skills', { required: true }, {}, [
{ value: 'js', label: 'JavaScript' },
{ value: 'python', label: 'Python' },
{ value: 'java', label: 'Java' }
]
]
Dynamic Single Select
Create cascading dropdowns where options in the second select depend on the first selection:
[
'dynamicSingleSelect', // Field type
'programming', // Field name
'Programming Languages', // Label
{ required: true }, // Validation
{}, // Attributes
[ // Main categories (appear in first dropdown)
{
id: 'frontend',
label: 'Front End',
options: [
{ value: 'javascript', label: 'JavaScript' },
{ value: 'react', label: 'React' },
{ value: 'vue', label: 'Vue' }
]
},
{
id: 'backend',
label: 'Back End',
options: [
{ value: 'nodejs', label: 'Node.js' },
{ value: 'python', label: 'Python' },
{ value: 'java', label: 'Java' }
]
}
]
]
HTML Content Blocks ✨ New
Insert custom HTML or plain text anywhere in your form. Perfect for section headers, instructional text, warnings, or embedded content:
[
'html', // Field type
'div', // HTML element to render (div, p, span, section, etc.)
'Your content here', // Content (HTML or plain text)
{}, // Validation (not used for HTML blocks -but do keep the empty {})
{ // Attributes for the HTML element
id: 'section-header',
class: 'info-message highlight',
style: 'color: #4338ca; padding: 1rem; background: #f5f3ff;',
'data-type': 'instructional'
}
]
Examples:
Plain text paragraph:
['html', 'p', 'Please fill out all required fields marked with *', {}, {
class: 'instruction-text',
style: 'font-style: italic;'
}]
Section header with custom styling:
['html', 'h3', 'Personal Information', {}, {
class: 'form-section-header',
style: 'border-bottom: 2px solid #4338ca; margin-top: 2rem;'
}]
Warning message:
['html', 'div', '⚠️ Your session will expire in 5 minutes', {}, {
class: 'warning-banner',
role: 'alert'
}]
Complex HTML with nested elements:
['html', 'div', `
<div class="info-box">
<strong>Note:</strong>
<span>All fields are required unless marked optional</span>
</div>
`, {}, {
class: 'custom-wrapper'
}]
Resulting HTML structure:
<div class="form-group" id="section-header-block">
<div id="section-header" class="info-message highlight" style="color: #4338ca; padding: 1rem;">
Your content here
</div>
</div>
Each HTML block is automatically wrapped in a form-group div for consistent spacing and layout with form fields.
Conditional Logic
Show/hide fields based on other field values:
// Parent field with dependents
[
'singleSelect', 'role', 'Role',
{ required: true },
{ dependents: ['topic', 'mode'] }, // Fields that depend on this
[
{ value: 'attendee', label: 'Attendee' },
{ value: 'presenter', label: 'Presenter' }
]
],
// Dependent field with string condition
[
'text', 'topic', 'Presentation Topic',
{},
{
dependsOn: 'role',
condition: 'presenter' // Shows when role = 'presenter'
}
],
// Dependent field with function condition
[
'singleSelect', 'mode', 'Presentation Mode',
{ required: true },
{
dependsOn: 'role',
condition: (value) => value === 'presenter' // Function condition
},
[
{ value: 'virtual', label: 'Virtual' },
{ value: 'physical', label: 'Physical' }
]
]
Submission & Lifecycle
Formique separates form rendering and submission UI from network transport. Depending on how you configure it, Formique can either own the HTTP request or defer to another submission controller (such as Form from @semantq/ql).
A. Formique-Managed Submission
When formParams.action is explicitly configured and submitOnPage: true, Formique owns the submission lifecycle: it shows the spinner, issues the request, awaits the response, and renders the success or error state.
const formParams = {
id: 'contact-form',
method: 'POST',
action: '/contact'
};
const formSettings = {
submitOnPage: true
};
Formique owns: preventDefault → spinner → fetch → success/error UI.
B. Externally Managed Submission
When formParams.action is omitted, Formique does not invent a fallback endpoint and does not issue an HTTP request. The request may instead be performed by another submission controller such as Form from @semantq/ql.
const formParams = {
id: 'resident-form',
method: 'POST',
enctype: 'multipart/form-data'
// no action
};
Architecture in this mode:
Formique
→ renders the form
→ renders loading/success/error UI
→ listens for Form lifecycle events
Form (@semantq/ql)
→ captures the payload
→ owns the async submission lifecycle
smQL
→ performs HTTP transport
Important: When no explicit
actionis configured, Formique will not issue a second HTTP request. This is intentional — it prevents accidental duplicate submissions and premature success states.
Using Formique with @semantq/ql Form
Formique listens to three lifecycle events dispatched by the Form utility on the <form> element:
| Event | Formique UI effect |
|---|---|
form:processing |
Show loading indicator (#formiqueSpinner) with the configured loadingMessage |
form:success |
Hide loading indicator, show successMessage |
form:error |
Hide loading indicator, show errorMessage |
Note: form:captured belongs to the Form capture lifecycle and does not itself represent success or failure.
Loading, Success & Error States
All three on-page states are configurable through formSettings:
const formSettings = {
submitOnPage: true,
loadingMessage: 'Uploading assessment...',
successMessage: 'Assessment uploaded successfully.',
errorMessage: 'Assessment upload failed. Please try again.'
};
| Setting | Controls | Default |
|---|---|---|
loadingMessage |
Text shown beside the Formique spinner during submission | 'Submitting...' |
successMessage |
On-page success state shown after a successful submission | 'Your details have been submitted successfully.' |
errorMessage |
On-page error state shown after a failed submission | 'An error occurred while submitting the form. Please try again.' |
Lifecycle Events
For advanced use, Formique exposes the underlying lifecycle events so that applications can attach their own listeners:
const formEl = document.getElementById('resident-form');
formEl.addEventListener('form:processing', () => {
// fires before the request begins
});
formEl.addEventListener('form:success', (event) => {
// fires after a successful response
console.log('Result:', event.detail?.result);
});
formEl.addEventListener('form:error', (event) => {
// fires after a failed response or rejection
console.error('Error:', event.detail?.error || event.detail?.result);
});
Note: Form from @semantq/ql yields to the browser after dispatching form:processing, giving Formique (or any other lifecycle consumer) an opportunity to paint its loading state before expensive asynchronous work begins.
Public Lifecycle UI Methods
Formique exposes three public methods that drive the loading/success/error presentation. These are useful when the application is coordinating an externally managed submission and wants to control Formique's UI directly:
form.showLoading();
form.showSuccess();
form.showError();
Optional message overrides:
form.showLoading('Processing...');
form.showSuccess('Completed successfully.');
form.showError('Something went wrong.');
When no argument is given, the methods use loadingMessage, successMessage, and errorMessage from formSettings.
For most workflows using Form from @semantq/ql, you do not need to call these methods manually — Formique invokes them automatically when it receives the lifecycle events.
Notifications
Formique's lifecycle UI and Notification.show() from @semantq/ql are independent presentation mechanisms and may be used together.
For example, a successful submission may simultaneously produce:
Notification.show()
→ temporary application-level toast
Formique
→ persistent in-form success state
Formique does not require Notification to function. Notification is not part of Formique's internal lifecycle.
Complete External API Submission Example
The following example shows Formique + Form + smQL working together with an externally managed file upload:
import Formique from '@formique/semantq';
import {
smQL,
Form,
Notification
} from '@semantq/ql';
const api = new smQL(baseOrigin);
const formSchema = [
[
'file',
'assessment',
'Resident Assessment',
{ required: true }
],
[
'submit',
'submit',
'Upload Assessment'
]
];
const formParams = {
id: 'resident-form',
method: 'POST',
enctype: 'multipart/form-data'
};
const formSettings = {
submitOnPage: true,
loadingMessage: 'Uploading assessment...',
successMessage: 'Assessment uploaded successfully.',
errorMessage: 'Assessment upload failed.'
};
$onMount(() => {
new Formique(
formSchema,
formParams,
formSettings
);
new Form(
'resident-form',
'submit',
{
onCaptured: async ({ formData }) => {
try {
const response = await api.post(
'/resident-assessments',
formData
);
Notification.show({
type: response?._ok
? 'success'
: 'error',
message: response?._ok
? 'Assessment uploaded successfully.'
: response?.message ||
'Assessment upload failed.'
});
return response;
} catch (error) {
Notification.show({
type: 'error',
message:
error?.message ||
'Assessment upload failed.'
});
throw error;
}
}
}
);
});
What's happening:
- Formique has no
action, so it does not issue the API request. Formcaptures the nativeFormData(including the uploaded file).smQLperforms the HTTP request viaapi.post(...).- When
onCapturedstarts,Formdispatchesform:processing→ Formique shows its loading state. - Returning
responseallowsFormto determine whether to emitform:successorform:error. - Throwing caught exceptions preserves
form:errorpropagation. - Formique displays its on-page status independently of the optional toast notification.
1. Styling the Form
Formique comes with a set of built-in themes to help you quickly style your forms. These themes are headless and minimal, allowing easy blending with your site's design system. They apply styling primarily to the submit button background and the bottom border of focused inputs, while maintaining a light background for most themes.
Available Built-in Themes:
lightdarkpinkindigodark-bluelight-bluedark-orangebright-yellowgreenpurplemidnight-blushdeep-bluebluebrownorange
⚠️ The
darktheme is more opinionated with full dark background support. All others are intentionally minimal.
To apply a theme, set the theme option in your formSettings:
const formSettings = {
theme: 'indigo'
};
If no theme is set, Formique will default to the light theme.
Fine-Grained Theme Control
To override the button and focus color with your own custom color, use the themeColor option in hexadecimal format:
const formSettings = {
themeColor: '#327ba8' // Must be a valid hex value
};
Custom Styling
Formique's form classes are exposed for complete customization. You can target the form using .formique, and inputs with classes like .form-input, .form-label, .form-submit-btn. See section below.
Example:
.form-input {
border-radius: 5px;
padding: 10px;
}
2. Styling and Sizing the Form Container
Formique renders inside a container <div> that you specify by ID.
Default Container
<div id="formique" class=""></div>
⚙ Custom Container ID
You can use any custom container ID by declaring it in your formSettings:
const formSettings = {
formContainerId: 'myForm'
};
And in your HTML:
<div id="myForm"></div>
Built-in Container Size Classes
Formique includes several responsive width utility classes:
| Class Name | Description |
|---|---|
width-full |
100% width |
width-half |
50% width |
width-medium |
600px fixed width |
width-small |
400px fixed width |
Example:
<div id="formique" class="width-half"></div>
Custom Inline Style Control
For precise container control:
const formSettings = {
formContainerStyle: 'width: 100%; max-width: 700px; padding: 2rem;'
};
Complete List of .formique-Scoped CSS Classes
Container & Layout
.formique.formique-form.width-full.width-half.width-medium.width-small.width-custom
Labels & Inputs
.form-label.form-input.form-control.form-textarea.form-select.form-select-input.form-radio-input.form-checkbox-input.form-color-input
Input Wrappers
.input-block.radio-group.checkbox-group.form-group
Themes
.custom-theme.dark-theme.light-theme.pink-theme.indigo-theme.dark-blue-theme.light-blue-theme.dark-orange-theme.bright-yellow-theme.green-theme.purple-theme.midnight-blush-theme.deep-blue-theme.blue-theme.brown-theme.orange-theme
Button
.form-submit-btn
Loading State
Formique's loading indicator is composed of three parts:
#formiqueSpinner
→ loading-state container
.formique-spinner
→ animated spinner graphic
#formiqueSpinner .message
→ loading text (uses `loadingMessage` from formSettings)
⚠️ CSS ownership: Formique controls spinner visibility as part of its submission lifecycle. Application CSS should not permanently force
#formiqueSpinneror.formique-spinnertodisplay: none !important, because doing so prevents Formique from displaying the processing state.Example of what not to do:
#formiqueSpinner { display: none !important; } .formique-spinner { display: none !important; }Custom CSS may style the spinner (colors, size, spacing), but should not override Formique's runtime visibility state.
Status Messages
.formique-success.formique-error
These classes are applied to the on-page success and error states rendered by Formique after a submission completes.
3. Contact Form Quick Setup
Formique supports plug-and-play email contact forms.
Basic Email Contact Setup
const formSettings = {
submitMode: 'email', // Required
submitOnPage: true, // Required
successMessage: 'Message sent successfully!',
errorMessage: 'Something went wrong',
sendTo: ['contacts@yourwebsite.com'] // Recipient email(s)
};
Complete Contact Form Example
const formSchema = [
['html', 'h3', 'Get in Touch', {}, {
class: 'form-section',
style: 'margin-top: 0;'
}],
['text', 'name', 'Your Name', { required: true }],
['email', 'email', 'Email Address', { required: true }],
['text', 'subject', 'Subject', { required: true }],
['textarea', 'message', 'Message', { required: true, minlength: 20 }, { rows: 5 }],
['html', 'p', 'We\'ll respond within 24 hours', {}, {
class: 'form-note',
style: 'font-size: 0.9rem; color: #666;'
}],
['submit', 'submit', 'Send Message']
];
const formSettings = {
submitMode: 'email',
submitOnPage: true,
sendTo: ['hello@yourwebsite.com'],
theme: 'blue',
requiredFieldIndicator: true
};
⚠️ Domain Verification for Email Submissions
To enable email submissions, ensure your domain is registered on your useformique.com account.
This is required for sender verification and spam protection.
For more comprehensive details on Formique's features and options, visit the Formique GitHub Repository.
Related Packages
Nuxt-style meta-framework for @jasonshimmy/custom-elements-runtime
Version History
| Version | Released | Vue | License |
|---|---|---|---|
| 1.1.13 | ^3.0.0 | MIT | |
| 1.1.12 | ^3.0.0 | MIT | |
| 1.1.10 | ^3.0.0 | MIT | |
| 1.1.9 | ^3.0.0 | MIT | |
| 1.1.8 | ^3.0.0 | MIT | |
| 1.1.7 | ^3.0.0 | MIT | |
| 1.1.6 | ^3.0.0 | MIT | |
| 1.1.5 | ^3.0.0 | MIT | |
| 1.1.4 | ^3.0.0 | MIT | |
| 1.1.3 | ^3.0.0 | MIT | |
| 1.1.2 | ^3.0.0 | MIT | |
| 1.1.1 | ^3.0.0 | MIT | |
| 1.1.0 | ^3.0.0 | MIT | |
| 1.0.12 | ^3.0.0 | MIT | |
| 1.0.11 | ^3.0.0 | MIT | |
| 1.0.10 | ^3.0.0 | MIT | |
| 1.0.9 | ^3.0.0 | MIT | |
| 1.0.8 | ^3.0.0 | MIT | |
| 1.0.7 | ^3.0.0 | MIT | |
| 1.0.6 | ^3.0.0 | MIT | |
| 1.0.5 | ^3.0.0 | MIT | |
| 1.0.4 | ^3.0.0 | MIT | |
| 1.0.3 | ^3.0.0 | MIT | |
| 1.0.2 | ^3.0.0 | MIT | |
| 1.0.1 | ^3.0.0 | MIT | |
| 1.0.0 | ^3.0.0 | MIT |