Wedding Agency Website Development on 1C-Bitrix
A wedding agency sells not a product, but emotion and trust. The website here functions as both a showcase of completed projects and as a tool for initial client qualification. The 1C-Bitrix platform allows combining both functions in one system: information blocks store portfolio and service catalog, web forms collect briefs, and the CRM module captures every contact up to contract conclusion.
Wedding Portfolio — Information Block Structure
Portfolio is the central section. Each wedding is formatted as an information block element with the following properties:
- Wedding style — list of values (classic, rustic, loft, minimalism, eco, boho). Property type — "List" with multiple selection, since one wedding can combine styles.
- Location — reference to a separate information block of venues (type "Element binding"). This allows filtering portfolio by specific venues.
- Guest count — numeric property. Used in faceted filtering by ranges: up to 30, 30–80, 80–150, 150+.
-
Photo gallery — property type "File" with multiple values. WebP support included; resizes generated via
CFile::ResizeImageGetfor preview and lightbox. - Video — string property with URL (YouTube/Vimeo). On front, loaded via iframe with lazy loading.
- Couple feedback — HTML/text property. Additionally: couple names, wedding date, couple photo (for quote).
For portfolio list output, use component bitrix:news.list with custom template. Detail page — bitrix:news.detail with gallery and video block. Filtering by style, location, and guest count is implemented via bitrix:catalog.smart.filter or custom AJAX filter.
Service Catalog and Packages
Agency services are grouped into packages: turnkey organization, day coordination, decor, floristry. Each package — information block element with composite content:
-
Package name and short description — standard fields
NAMEandPREVIEW_TEXT. - Package contents — multiple property type "String" (each line — one item: "Venue selection," "Vendor coordination," "Day timeline," etc.).
- Package type — list (turnkey / coordination / decor / custom).
- Recommended guest count — range "from–to," two numeric properties.
On catalog page, packages display as cards with expandable contents. Package comparison — table generated on front from information block data.
Vendor and Venue Catalog
Separate information block for vendors: photographers, videographers, hosts, catering, musicians. Properties:
- Category — list.
- Rating — numeric property (1–5), displayed as stars.
- Price category — list (budget / standard / premium).
- Portfolio — binding to information block elements of wedding portfolio where vendor participated.
Venues are placed in Highload block if count exceeds 200–300 — for performance on filtering. Properties: capacity, type (restaurant, country complex, tent, loft), geolocation for map.
Wedding Ideas Blog
Blog built on separate information block. Articles linked to styles, seasons, tags. Component bitrix:news with SEO-friendly URLs like /blog/wedding-idea-loft-style/. In each article — embedded links to relevant portfolio weddings and vendors. This increases page depth and internal linking.
Bride Brief — Detailed Questionnaire
Brief collected via web forms module (form) or custom component based on bitrix:main.feedback. Questionnaire fields:
- Couple names, wedding date, planned guest count
- Preferred style (checkboxes from style reference)
- Budget — range selection
- Venue, decor, entertainment preferences — text fields
- Reference upload (photos) — "File" field with multiple values
- Contact data and preferred communication method
On form submission, data goes to Bitrix24 CRM (if integration connected) or lead entity on site. Responsible manager assigned; initial processing business process launched.
Deep-dive: Wedding Budget Calculator by Expense Categories
The calculator is an interactive tool solving two tasks: giving the couple a cost estimate and simultaneously generating a qualified lead with detailed request. Implementation on 1C-Bitrix requires well-designed data architecture and server logic.
Calculator Data Structure
Rates stored in Highload block BudgetRates with following fields:
| Field | Type | Description |
|---|---|---|
| UF_CATEGORY | list | Expense item (venue, catering, decor, photo/video, host, music, transport, printed materials, styling, other) |
| UF_LEVEL | list | Level (budget, standard, premium) |
| UF_CALC_TYPE | list | Calculation type: "per guest," "fixed," "per hour" |
| UF_RATE | number | Base rate |
| UF_MIN_AMOUNT | number | Minimum amount for item |
| UF_SEASON_COEFF | number | Seasonality coefficient (summer × 1.3, winter × 0.85) |
Calculation Logic
User enters two parameters: guest count and overall celebration level. Based on this, calculator computes each item:
-
Rate selection — extract rows from Highload block with
UF_LEVELmatching chosen level. -
Type calculation — if
UF_CALC_TYPE= "per guest," result =UF_RATE × guest count. If "fixed" — takeUF_RATE. If "per hour" — multiply by average duration (6 hours by default). -
Apply minimum — if calculated amount below
UF_MIN_AMOUNT, substitute minimum. -
Seasonal coefficient — final sum multiplied by
UF_SEASON_COEFF, which depends on chosen month. - Summary — form table of items with amounts and grand total.
Front-end Implementation
Calculator works as AJAX component. User selects parameters via sliders and selects. On each change, request sent to controller (ajax.php in component), executing Highload block query and returning JSON with calculation. On front, data rendered as table with columns "Item," "Cost," "Budget Share (%)" and pie chart showing distribution.
Additional mechanics — manual adjustment. User can disable individual items (e.g., "transport not needed") or switch level for specific position (catering — premium, decor — budget). This transforms calculator into flexible budget constructor.
CRM Link
Calculation result saved in session. Below table — button "Get detailed estimate." On click, form opens with minimal fields (name, phone, wedding date). On submission, CRM creates lead with attached calculation: manager sees not just "want a wedding" but specific budget breakdown with each item's level. This radically increases initial consultation conversion.
Example Calculation for 80 Guests, "Standard" Level, Summer
| Expense Item | Calculation Type | Rate | Season. Coeff. | Total |
|---|---|---|---|---|
| Venue | per guest | — | 1.3 | — |
| Catering | per guest | — | 1.3 | — |
| Decor & floristry | fixed | — | 1.0 | — |
| Photo + video | fixed | — | 1.3 | — |
| Host | per hour | — | 1.2 | — |
| Music / DJ | per hour | — | 1.0 | — |
| Transport | fixed | — | 1.0 | — |
| Printed materials | per guest | — | 1.0 | — |
| Styling (bride + groom) | fixed | — | 1.0 | — |
Technical Aspects
- Caching: portfolio and venue catalog cached with auto-reset on information block changes (tagged cache).
- SEO: each portfolio element — separate landing page with unique title, description, and photo alt. SEO templates configured via block properties.
- Responsiveness: wedding sites viewed primarily on mobile (up to 70% traffic). Portfolio gallery uses swipe navigation; calculator adapted for touch interface.
- Performance: WebP images with lazy load, critical CSS inlined, calculator JS bundle loaded on demand.
Overall architecture combines emotional showcase (portfolio) with practical tool (budget calculator), converting visitor into qualified lead with specific numbers.