79 plain-English definitions, from Generative AI to Gzip. Terms with a link have a full explanation with a Jersey example. To search every term, go back to the Jargon Buster.
Generative AI produces new material, such as text, images or code, from instructions and learned patterns. It can help develop drafts, but output may be inaccurate or unsuitable. Review facts, rights and privacy before using generated material for a Jersey business’s public content or customer communications.
Geocoding converts address information into a geographic location, such as latitude and longitude, through a supported lookup service. Reverse geocoding works from a location towards address information. A Jersey business should review the returned result against its intended place and customer instructions; an accepted request or plausible marker does not prove that the correct premises or entrance was identified.
Also called: Address geocoding
GeoJSON is a JSON-based format for exchanging geographic features and related properties. It defines supported structures and coordinate conventions for the data. A Jersey business should identify the source, intended geography and receiving interpretation, then inspect the actual displayed result; a file parsing successfully does not prove its features describe current locations or approved business information.
Also called: Geographic JSON
A GeoJSON bounding box describes a spatial extent through the format’s bbox member and applicable coordinate ordering. It is separate from a complete feature geometry. Review the actual data and supported receiver when using it to frame a map; a useful view extent does not verify every location or area displayed within it.
Also called: GeoJSON bbox
A GeoJSON Feature connects geographic geometry with related properties under the supported format. OGC API Features specifies relevant feature-response arrangements. Keep the source record and intended meaning identifiable, then compare the actual location and properties; format handling alone does not verify that the displayed business information is current or complete.
Also called: Geographic feature object
A GeoJSON FeatureCollection groups feature objects within a supported geographic-data arrangement. OGC API Features specifies its use for relevant feature responses. Inspect the expected records and actual received collection; an exchange parsing successfully does not establish that every required business location was included or that unexpected records have been removed.
Also called: Geographic feature collection
A GeoJSON LineString geometry contains an array of two or more positions. It represents a line in the exchanged geographic data. Review the source meaning and actual display before presenting it as a customer route; a structurally valid line does not establish that every segment is accessible or that it represents approved navigation instructions.
Also called: LineString geometry
A GeoJSON Point geometry uses one position as its coordinates value. It represents geographic data, separate from independently verifying that the chosen place is correct. Compare a representative known location and the receiving map’s coordinate interpretation before using the source to display important business-location information.
Also called: Point geometry
A GeoJSON Polygon geometry uses coordinate arrays for an exterior ring and any interior rings. It represents an area in the exchanged geographic data. Define what the area means and compare the actual display; a valid shape is separate from approval of a business service region or another authoritative boundary.
Also called: Polygon geometry
Geolocation accuracy reports horizontal position accuracy in metres with a ninety-five-percent confidence level in the browser coordinates interface. It is separate from a verified address or entrance. Review the reported value and the actual feature’s interpretation rather than treat a displayed map point as a guarantee of exact device position.
Also called: Location accuracy
Geolocation altitude reports a position’s height in metres above the WGS84 ellipsoid in the browser coordinates interface. It can be null when the implementation cannot supply the information. Keep the reference surface and unavailable result explicit rather than treat the field as a verified floor number or elevation above every local sea-level convention.
Also called: Device altitude
Geolocation altitude accuracy reports the altitude accuracy in metres with a ninety-five-percent confidence level in the browser coordinates interface. It can be null when altitude measurement is unsupported. Review the actual available fields together; a value missing from the result should not silently become evidence that the location has zero uncertainty.
Also called: altitudeAccuracy
The Geolocation API lets a supported web application request device location with the visitor’s permission and relevant browser requirements. It can return coordinates with reported accuracy rather than guarantee an exact address. A Jersey business should explain the intended task, review unavailable or declined access and provide a useful alternative; receiving a location does not establish the complete customer result.
Geolocation clearWatch unregisters location and error monitoring handlers previously installed with watchPosition. It is part of controlling the lifetime of that supported monitoring arrangement. Review the actual feature lifecycle with the maintainer; stopping a watch is separate from deleting previously stored location information or defining the complete data-handling process.
Also called: clearWatch
Geolocation getCurrentPosition requests a device position through the supported browser interface, using success and optional error handling and relevant options. Permission and environment requirements still apply. Review the returned location and unavailable-result path; calling the method is separate from receiving suitable information or completing the customer’s intended task.
Also called: getCurrentPosition
Geolocation heading reports the device’s direction of travel in degrees clockwise from true north through the browser coordinates interface. It can be null when unavailable or speed is zero. It concerns reported movement rather than a guarantee about which way the person is looking; review the actual result before using it in a map feature.
Also called: Device travel heading
Geolocation enableHighAccuracy expresses a preference for the best possible position result in a supported request. The documented arrangement can involve slower results or more power use. It is separate from a guarantee of exact location; review the actual observation and customer task rather than treat the option as a universal accuracy certificate.
Also called: enableHighAccuracy
Geolocation maximumAge specifies the acceptable age of a cached position, in milliseconds, in the supported request options. It concerns how an available result may be reused rather than a guarantee of its current accuracy. Record the actual setting and returned observation when reviewing the feature’s suitability for the customer task.
Also called: maximumAge location option
Geolocation speed reports device velocity in metres per second through the browser coordinates interface. It can be null when the implementation cannot measure it. Keep unsupported information distinct from an observed zero value, then review the feature’s actual interpretation rather than assume every location result includes usable movement data.
Also called: Device movement speed
The geolocation timeout option specifies the allowed time for obtaining a position in milliseconds within the supported request arrangement. It needs an appropriate error and alternative task path. Review the actual unavailable-result experience rather than assume a chosen timeout guarantees a usable location or a complete customer response within that period.
Also called: Location timeout option
Geolocation watchPosition registers handling for position updates through the supported browser interface, with optional error handling. It is a monitoring arrangement rather than a one-time address verification. Have the maintainer define when the feature needs updates and when monitoring stops, then review the actual customer result and unavailable-information behaviour.
Also called: watchPosition
Element.getAttribute() reads an attribute’s string value, returning null when the named attribute is absent. Keep the expected attribute and meaning clear in the implementation. Review absence and representative values where relevant, then inspect what the feature does next rather than assume that reading markup establishes a correct customer response.
Also called: Element.getAttribute()
GET is an HTTP method used to request a representation of a resource. It is intended for retrieving information rather than changing server state. A website should not depend on a supposedly harmless retrieval link to perform an important action such as deleting a customer record.
Also called: HTTP GET
GIF is an image format that supports simple animation and a limited colour palette. Its limitations can affect quality and file size. Review appropriate modern image or video alternatives when adding animation, along with movement controls and the visitor’s experience.
A gift card provides a value that can be redeemed according to the shop’s arrangement, commonly using a code. It differs from a percentage discount. Review issuing, balance use and customer support, and obtain suitable advice for the actual regional terms instead of assuming every provider setting establishes compliance.
Git is a version control system that records project history and supports comparing and combining changes. Developers can work with branches and exchange history between repositories. A Jersey business should know where its website repository is kept, who controls access and how reviewed source changes connect to the actual build and release.
Also called: Git version control
Git bisect narrows a range of revisions using good and bad results to investigate the change associated with a regression. Its usefulness depends on a meaningful, repeatable check. Define the observed website problem and test conditions before classifying versions, so the investigation follows evidence instead of an inconsistent visual impression.
Git blame annotates file lines with revision information associated with their last changes. It helps investigate code history. Read that evidence alongside the surrounding implementation and requirement, rather than treat a name beside a line as a complete explanation of why a website problem occurred or who is responsible for its resolution.
Git cherry pick applies changes introduced by selected existing commits to the current development context, normally recording new commits. It can help bring a specific fix onto another branch. For a Jersey business, check the chosen change’s dependencies, review any conflicts and verify the resulting website before assuming that selecting one commit delivers a complete working improvement.
Also called: cherry-picking commits
A Git clone creates a local repository from an existing repository, with the content and history determined by the chosen options. It is a starting point for development. A clone does not automatically include external databases, service credentials or every asset needed to operate the complete website.
Detached HEAD means the Git checkout refers directly to a commit rather than through a named branch. It can support inspection of a particular version. Have the maintainer preserve any new work through an appropriate reference before moving away, and keep the reviewed state identifiable in the business’s handover.
Also called: detached HEAD state
A Git diff displays differences between selected versions or states of project content. It helps a reviewer understand what changed. Confirm which comparison is being shown and review relevant output and behaviour too, because a source difference alone does not establish the effect on the delivered website.
A Git fast-forward update advances a branch reference when the existing history is an ancestor of the target, without creating an additional merge commit. Keep the resulting version identifiable. The history relationship does not establish website quality, so review the included changes and relevant customer tasks before approving a release.
Also called: Git fast forward merge
Git fetch obtains relevant references and repository objects from another repository and updates the applicable remote-tracking information. It helps a maintainer inspect available remote work. Keep the distinction between acquiring history and integrating it into the current branch clear, and verify the actual checkout before describing the website as updated.
HEAD identifies the current Git checkout context, normally through a branch reference or directly through a commit in a detached state. Keep that context visible during a handover. A folder’s name is insufficient evidence of the version being reviewed, so verify the actual reference and files before accepting a website change.
The Git index stores the staged state used when preparing a commit and can also represent conflict information. Keep staged changes distinct from the files currently being edited. Ask the maintainer to inspect the intended commit contents, so a review does not accidentally include unrelated work or omit part of the approved change.
Also called: Git staging area
Git merge integrates changes from another development history into the current branch. Depending on the relationship between the histories, it can advance a branch reference or create a merge commit. For a Jersey business, review the combined website changes and resolve conflicts against the intended requirements before accepting the result or approving its release.
Also called: merging Git branches
A merge commit records a combined development result with the relevant parent commits. It helps represent how histories were brought together. Ask the maintainer to explain the included work and resolved decisions, then review the actual website result before treating the presence of a merge commit as evidence of business approval.
A Git object ID identifies a repository object, such as a commit. It helps make a review version traceable. Keep the relevant repository and object context with the identifier, and have the maintainer verify the actual content before assuming a copied short value establishes the website version the business intends to approve.
Also called: Git object identifier
A parent commit is a logical predecessor recorded by a Git commit; the parent list can be empty or contain multiple entries. It helps explain development history. Ask the maintainer to interpret the actual relationships when discussing a combined change, rather than infer release order or business approval solely from the graph’s appearance.
Git pull fetches remote work and integrates the selected remote branch into the current branch through the configured or chosen approach. Inspect the repository state and integration policy first. The team should review the resulting changes and any conflicts before describing a completed pull as a verified website improvement.
Git rebase reapplies a series of commits on another starting point. It can help reorganise development history or bring work onto a newer base, but rewritten commits need coordination when other people depend on them. For a Jersey business, agree the repository workflow, preserve the intended changes and review the website before treating a tidier history as a successful update.
Also called: rebasing
A Git ref is a name pointing to an object or another reference. Branch and tag references help identify repository states. Record the resolved version when a review matters, because a name alone needs context and may later refer to different work. Keep that evidence with the owner’s acceptance and release description.
Also called: Git reference
A Git reflog records updates to branch tips and other references in a local repository. It can help a maintainer locate an earlier reference position during an investigation or recovery task. For a Jersey business, preserve current work, inspect the candidate version and document the intended recovery rather than assume a local reference log is a complete permanent website backup.
Also called: reference log
A Git remote is a named reference to another repository used for exchanging project history. It can point to a repository hosting service or another location. Know which remote belongs to the business and who controls access; configuring a remote does not automatically transfer every local change.
Git reset can move HEAD or update selected staged content, with effects that depend on its mode and arguments. Ask the maintainer to explain the exact operation and preserve relevant work first. A generic request to reset the website is too vague to establish which files, references or release state should change.
Git restore replaces selected working-tree or index content from a specified or default source. Its scope and options matter. Review the intended paths and existing changes with the maintainer before using it, and inspect the resulting files rather than assume a command named restore automatically produces the business’s desired website version.
Git revert records new commits that reverse changes introduced by selected earlier commits. It preserves a record of the reversal in history. Review the actual effect and current dependencies before proposing it as a fix, and verify the customer-facing result through the project’s supported review and release process.
Git’s squash merge option prepares a combined working-tree and index result without automatically recording a merge commit or moving HEAD. The prepared result still needs review and an appropriate commit. Keep the selected changes and resulting history clear so the owner understands which work is proposed and how it will be identified.
Git stash saves local modifications for later inspection or application while returning the relevant checkout state towards HEAD. Review the selected scope and saved entry. It supports a local workflow, but the business still needs a deliberate record of accepted work and appropriate backups rather than rely on an unexplained stash as its release handover.
Git status reports relevant staged, working-tree and untracked paths in the checkout. It helps a maintainer account for local work before preparing a commit or integrating changes. Review what the output means for the intended task, rather than assume a directory contains only the approved website change because its name looks familiar.
A Git submodule is a repository embedded in another repository while keeping its own history. It adds a separate context to the project handover. Identify the required version, access and maintenance responsibility for each component, so a new maintainer can obtain and review the complete supported website setup.
The Git working tree contains the actual checked-out files and can include local changes beyond the referenced commit. Inspect that state when reviewing a website. A commit identifier alone does not establish that every visible file matches it, so account for existing edits before treating the preview as the exact proposed release.
Google Ads is Google’s advertising platform; PPC means pay per click, a charging model in which a click can incur a cost. Not every advertising campaign uses that model. Define the audience, destination page, budget and valuable customer action before paying to attract traffic.
Also called: PPC, pay per click, Google Ads
Google Analytics is a tool that collects information about visits and actions on a website or app, then organises it into reports.
Also called: GA4, Google Analytics 4
Google Analytics retention settings control how long certain user-level and event-level data remains available before deletion from Analytics servers. Their effect depends on the reporting surface and data involved. For a Jersey business, review the setting against the analysis you actually need, record its scope and avoid assuming that it defines every business record’s legal retention period.
Also called: GA4 data retention
A Google Business Profile is a free listing that an eligible business can claim and manage on Google Search and Maps.
Also called: Google Maps business listing, GBP, Google business listing, Google Business page, Google My Business
A Google Business Profile category describes the kind of business represented by a profile.
Also called: GBP category
A Google Maps listing is the business information people can see on Maps. An eligible business can manage relevant details through its Google Business Profile. It is not a separate website or a guarantee of top placement. Keep your location, hours and contact information accurate.
Also called: Maps listing
Google product category refers to classification in Google’s product taxonomy. It differs from a shop’s own product-type hierarchy. Review the relevant category and the service’s current submission rules for the actual offer. A category value does not prove that the product is approved, advertised or visible to customers.
Also called: google_product_category
Google reviews are public ratings and written feedback associated with a business or place on Google.
Also called: customer reviews
Google Search Console is a Google tool for monitoring how a website appears in Google Search and investigating crawling, indexing and related issues.
Also called: Search Console, GSC
A Google tag destination is a connected Google product context to which the tag sends measurement data, such as Analytics or Ads. Keep the actual destination list and responsibilities in the handover. A tag being present on a page is insufficient evidence that it sends the intended information to the business’s approved setup.
A grapheme cluster groups text according to defined segmentation rules to approximate a user-perceived character. It can include several Unicode code points, and this approximation can require tailoring for particular uses. Review an application’s actual counting and editing rules rather than assume one displayed character always equals one stored code point.
Also called: Unicode grapheme cluster
GraphQL is a query language and execution approach for APIs. A client selects fields supported by the service’s schema, while the server provides the requested result through its implementation. Queries, mutations and subscriptions serve different purposes. A Jersey business should still review permissions, data meaning, error handling and the actual task completed by the integration.
A GraphQL mutation is an operation for changing data or triggering supported effects through an API’s schema. Its top-level mutation fields define the relevant actions. Review inputs, permissions and the actual resulting state, because a valid mutation document alone does not establish that a business process completed correctly.
A GraphQL query requests selected fields supported by an API’s schema. It can use arguments and variables to specify the desired result. The server validates the operation and must apply appropriate access rules; asking for a field does not establish that the caller can see every underlying record.
A GraphQL resolver is implementation code used to produce the value for a requested field during execution. It can connect the API’s schema to underlying application data or services. The schema describes the field, while the resolver performs the relevant work; both need to match the intended behaviour and access rules.
A GraphQL subscription receives updates about supported events through a long-lived operation. The server chooses a transport arrangement, commonly WebSockets or server-sent events. It is distinct from an ordinary query and still needs suitable access and reconnection handling for the feature, including a way to establish the relevant current state.
A CSS grid area is a rectangular region made from one or more grid cells that can contain an item. It describes placement space, not a guarantee that the content fits or belongs there. Review the intended grouping and actual rendered information, including the sequence customers encounter through supported navigation.
Also called: CSS grid area
The CSS grid-auto-flow property controls how automatically placed items flow into a grid. It concerns the layout’s placement algorithm, while the content should retain a meaningful logical sequence. Have the maintainer explain the actual settings and review the visible and supported navigation order rather than assume automatic placement proves the information hierarchy.
Also called: grid-auto-flow
A CSS grid cell is the space between adjacent row lines and adjacent column lines, forming the smallest unit of the grid. A content item can span more than one cell. Keep the placement separate from the item’s meaning, then review its actual text, available space and customer action.
Also called: CSS grid cell
CSS grid lines divide the layout into row and column tracks and provide references for item placement. They are layout boundaries rather than necessarily visible rules on the page. Have the maintainer identify the intended placement and inspect the actual content sequence, so a visual position does not obscure the information’s logical order.
Also called: CSS grid line
The CSS grid-template-columns property defines column line names and track sizing functions. It is part of the grid’s implementation, while the business should review the resulting content arrangement. Check actual titles and actions in representative space rather than assume a valid column declaration proves the visible information remains readable.
Also called: grid-template-columns
The CSS grid-template-rows property defines row line names and track sizing functions. It helps establish the implemented row arrangement. Review the actual content and relevant optional or long-text cases; a declared row structure is separate from confirming that every business message fits and that the item sequence supports the intended task.
Also called: grid-template-rows
A CSS grid track is the space between two adjacent grid lines, forming a row or column track. It describes a layout relationship rather than an individual content item. Review track sizing with actual business content, since a technically valid arrangement can still need changes for long headings or meaningful comparisons.
Also called: CSS grid track
GTIN stands for Global Trade Item Number, an identifier used for trade items. In product data, supply the correct assigned identifier for the actual product rather than invent one or substitute an internal shop code. Requirements depend on the product and destination service; keep the identity linked to the appropriate variant.
Also called: Global Trade Item Number
Guest checkout allows a customer to place an order without being required to sign in to a customer account.
Gzip is a lossless compressed-data format used in files and supported web-response arrangements. The receiver decompresses it to recover the data. A Jersey business should verify which resources actually use it and review their delivered sizes and page behaviour; enabling compression alone does not establish that the complete website is fast or correctly configured.
We build and look after websites for Jersey businesses, and we explain the choices in plain English.
See what we can help with →