DigiBouquet Editorial Policy

How DigiBouquet publishes

Content mission

DigiBouquet publishes people-first resources for readers who want help choosing flowers, understanding symbolism, building digital bouquets, and writing better notes. The purpose of a page is not to occupy a keyword. A page should help someone make a clearer decision inside the actual DigiBouquet workflow.

Research and sourcing

Pages that make factual claims about flower symbolism, botany, etiquette, or historical usage should cite a public source that directly supports the claim. Appropriate sources may include horticultural organizations, botanical references, museums, universities, and established reference publishers. General writing or search-quality guidance is not presented as evidence for flower facts.

Because flower symbolism varies across regions and traditions, DigiBouquet avoids presenting symbolic associations as universal facts. We prefer wording such as "commonly associated with" or "often used to express" when the meaning depends on context.

Article reference links are displayed in a visible Sources and claim support section. Every entry names the source, publisher, and the point for which it was consulted. A source list does not mean that the publisher endorses DigiBouquet or the page's original gifting recommendations. A page based only on a worked DigiBouquet scenario may have no external sources rather than padding the list with unrelated links.

Bouquet names and messages are not used as editorial research data. DigiBouquet does not publish claims about user percentages, sharing volume, recipient behavior, or other first-party audience trends unless a documented measurement method and reviewable supporting evidence exist.

Product alignment checks

When a major guide is updated, the maintainer checks it against the current DigiBouquet product. Automated content validation also rejects a worked example if it uses an unavailable flower, fewer than three flowers, duplicate flowers, or an unavailable card template. The check focuses on four questions:

1. Does the page still match the current bouquet-builder experience?
2. Does the page include a concrete example instead of only abstract advice?
3. Does each listed source explain the claim it supports?
4. Does the generated example link decode into a bouquet the viewer can render?

Product descriptions must also distinguish the current fragment-based /bouquet#b=... sharing flow from temporary legacy query links. Base64URL is described as encoding, not encryption, and content must not promise that links are confidential or permanent.

Editorial responsibility and review limits

Tommy Tang currently owns the product and is also the named author and maintainer for the public content. DigiBouquet does not have a separate independent editor, botanist, or medical reviewer. A same-person content check is described as a maintenance check, not as independent editorial approval. The site does not claim botanical or medical authority.

Use of AI on DigiBouquet

Some flower and foliage visuals are identified in project records as AI-assisted assets prepared for the service. The repository keeps an asset provenance ledger that separates known facts from evidence the owner still needs to retain, such as generation records, source files, and applicable service terms. Public guides are not published automatically, but automated or draft assistance may be used during preparation. The named maintainer remains responsible for checking the resulting page and correcting unsupported or inaccurate claims.

Updates and freshness

A guide is updated when one of the following is true:

• The page no longer reflects the current DigiBouquet product or bouquet creation flow
• A clearer example, stronger fit check, or better message set would materially improve the page
• A reader reports a factual issue or wording that could mislead
• We expand a topic to better cover a common user question

Each page displays publication and update dates so readers can judge freshness for themselves.

Corrections

If a claim is inaccurate or the page no longer matches the product, DigiBouquet corrects the page as soon as practical and updates the visible modification date. Issues that affect the main recommendation of a page are prioritized ahead of purely cosmetic changes. Corrections can be reported through the contact page.

Commercial independence

Editorial content is written to help readers make a better choice, not to inflate page count. DigiBouquet does not publish pages solely to host advertising. The bouquet builder, flower guides, and bouquet examples are expected to support each other, but each public page should still be useful on its own.