Glossary
What is DNS? How visitors find your event website
Understand how DNS connects a domain name to a website, why updates can take time, and what to check before sharing the address of your next event.
The Boletolibre journal
Ideas for better events
Practical guides, clear definitions and sourced comparisons for event organizers. Explore ticketing, websites, planning and regional requirements.
Glossary
What is a domain name? The name is not the whole website
Learn what a domain name is, how it differs from a URL or subdomain, and what registering a name means when you are planning a website for an event.
Websites & domains
Where to buy a domain name: choose a registrar you can manage
Find where to register a domain and compare renewal costs, account control, DNS access and support before choosing an address for your event website.
Websites & domains
How to manage a domain before, during and after an event
Keep control of your event domain with a practical routine for account access, renewals, DNS changes, suspicious notices and handoffs between team members.
Glossary
Domain vs. hosting: what each service does
Separate your website address from its hosting. Learn how registration, DNS and web hosting work together, and what to confirm before setting up an event site.
Websites & domains
DNS records for a custom domain: a practical setup worksheet
Prepare a custom-domain DNS change without guessing record values. Identify the right DNS account, preserve email settings and check the site after the change.
Glossary
Subdomain vs. domain: choose the right address structure
Compare a domain, a subdomain and a URL path using an event-site example. Learn which part DNS controls and what to confirm before choosing an address.
Glossary
What is SSL? TLS, HTTPS and the limits of a secure connection
Understand why “SSL” usually means TLS today, what HTTPS protects on an event page, and why an encrypted connection is not proof that an event is legitimate.
Glossary
What is an e-ticket for an event?
Understand how an e-ticket differs from an order confirmation, what to check before arriving, and why a code alone does not guarantee admission to an event.
Glossary
What is QR code ticketing?
Learn what a ticket QR code contains, how scanning differs from validation, and what organizers should test for duplicate use, multiple entrances and offline checks.
Glossary
General admission and VIP tickets: what is the difference?
Compare general admission and VIP without assuming reserved seats or extra perks. Use a fictional ticket matrix to make access, inclusions and limits clear.
Glossary
What is a ticket presale? Access, availability and early-bird pricing
Learn what ticket presales offer, how access differs from a ticket hold, and why early-bird pricing is a separate choice, with a fictional allocation example.
Ticketing
How to plan an event ticket refund policy: rights, decisions and payment checks
Build an event ticket refund policy around applicable rights, clear decisions and payment reconciliation, with a fictional example and a practical launch check.
Event planning
An event planning checklist built around owners, dependencies and readiness
Build an event planning checklist with accountable owners, task dependencies and current evidence, from first commitments to live operations and post-event review.
Event planning
How to build an event registration page: promises, fields and truthful confirmations
Make your event registration page match the real process: clear event facts, justified fields, useful error messages and confirmations that explain the actual state.
Event planning
Event capacity planning: limits, ticket allocations and people inside
Keep approved event limits, ticket allocations, attendance forecasts and live people counts separate. Work through a fictional ledger and controlled transfers.
Rules & regions
US event legal requirements: who owns each answer?
Map US event responsibilities to the right authority, evidence and owner. Separate venue assurances, applications, accessibility review and ticket-price duties.
Rules & regions
Mexico event legal requirements: build three separate evidence packets
Separate local event documents from Mexico’s consumer and private-sector privacy duties. Use a blank packet worksheet and a clearly fictional CDMX example.
Comparisons
Linktree vs an event website: choose the visitor task and its owner
Compare Linktree and an event website by visitor tasks, verified destinations and maintenance ownership—not assumptions about forms, fees or search performance.
Comparisons
Boletia vs Boletolibre: separate ticket operations from website evidence
Compare Boletia documentation with Boletolibre’s inspected website source, then record the demonstrations, terms and workflow owners your event still needs.
Comparisons
Eventbrite vs Boletolibre: who owns each step of the ticket journey?
Map discovery, checkout, ticket access, admission and support. Compare Eventbrite documentation with Boletolibre’s website source without assuming feature parity.
Event planning
Coordinating a European roadshow: one shared core, a manifest for every city
Plan a multi-city European event with local owners, exact-date clocks and accepted revisions. Use a blank city manifest and a clearly fictional Berlin–London case.
Event planning
Organizing live events in the USA: work backwards from evidence
Build an owner-led event schedule that separates local application horizons from internal buffers, launch decisions and load-in, with a Colorado example.
Event planning
Organizing live events in Mexico: make every production handoff explicit
Coordinate a Mexican concert through budget, rider, venue access, supplier acceptance, show cues and reconciliation, with a blank worksheet and fictional case.
Websites & domains
Choose a domain renewal budget: fund a defined window, not a launch offer
Build a dated renewal funding memo with applicable terms, optional charges and open questions. A blank worksheet comes before a clearly fictional USD example.
Websites & domains
Troubleshoot a domain that does not resolve: build an evidence handoff before changing anything
Record the exact DNS question, response context and missing evidence. Use a blank five-row ledger, then a clearly fictional example that makes no changes.
Websites & domains
Plan a DNS cutover: four checkpoints and a scoped reversal
Prepare a bounded DNS record-change runbook with readiness gates, separate publication evidence and a reversal packet. Includes a blank worksheet and fictional hold.
Websites & domains
Protect email during a website DNS change: find shared dependencies
Review MX target addresses, SPF dependencies and proposed automated changes before approving a website DNS move. Includes a blank register and a fictional hold.
Websites & domains
Choose DNS TTL values for a migration: record the assumptions
Choose a supported TTL candidate by separating old cached answers, provider-controlled settings and negative-cache policy. Includes a worksheet and fictional timing models.
Websites & domains
Export and document a DNS zone: preserve the source and record the gaps
Build a DNS export record with an untouched source, record-set inventory and provider-feature sidecar. A fictional example separates missing data from restore claims.
Websites & domains
Transfer a domain between registrars: eligibility and service preservation
Plan a registrar transfer with separate authority, policy and service evidence. Includes blank handoff records and a fictional case that stays on HOLD despite calendar lead.
Websites & domains
Renew an expiring event domain: deadline, status and completion evidence
Choose a domain renewal route from its actual deadline and status. Use a blank decision board to distinguish automation, accepted extension and event-service checks.
Websites & domains
Recover control of an organization domain: build an evidence brief
Prepare an organization-domain recovery brief with separate claim, control and authority records. Choose an escalation branch without treating an invoice as ownership proof.
Websites & domains
Hand over a domain after an agency contract: record recipient acceptance
Plan a cooperative agency exit with separate checks for domain control, recovery, renewal and services. Record recipient acceptance before closing the handover.
Event planning
Organizing live events in the Netherlands: an evidence handover runbook
Build a Dutch festival runbook linking arrivals, site access, vendors, weather decisions and audience messages. Track evidence, versions and recipient acceptance.
Comparisons
Compare event ticketing platforms: evidence before weighted scores
Compare ticketing providers with critical evidence gates, a blank weighted worksheet and matched quotes. Keep unknowns visible before choosing for your event.