Internal

Parked components

Sections kept here for reference and reuse. Each one below is a complete, self-contained block that can be copied back onto a live page.

Unify Technology Group

Specialist expertise.
Broader capabilities when you need them.

Megnity is one of five specialist companies in Unify Technology Group, 650+ professionals in all. Five different strengths, one shared way of working — and one partner accountable for the outcome.

  • Cloud infrastructure

    Microsoft Azure

    Conch

  • Data integration

    Informatica

    Axxel

  • Megnity

    Life Sciences engagement

    Commercial, medical, clinical and patient teams — on Salesforce and Databricks.

    Your partner

  • Analytics and ML

    Google Cloud

    MeridianSoft

  • Cybersecurity

    Enterprise defence

    Cyber Infotech

Unify Technology Group One delivery model · one accountable owner unifytech.group You stay with Megnity throughout.

Our team

The people behind the work

Good technology still depends on people who understand the business, ask the right questions and take responsibility for what gets delivered.

Our teams in the US and India work as one delivery organization, bringing business, platform, data and AI expertise together.

Ramesh Mudunuri
Ramesh Mudunuri Chief Executive Officer
Greg Lueck
Greg Lueck Advisory Board
Vinay Indukuri
Vinay Indukuri Chief Operating Officer
Ranganath Atmakuri
Ranganath Atmakuri Chief Success Officer
Abhiketh Namburi
Abhiketh Namburi Chief Financial Officer
Lavanya Kothapalli
Lavanya Kothapalli Chief Growth Officer
Sandeep Alluru
Sandeep Alluru Chief Delivery Officer
Teja Indukuri
Teja Indukuri People Success Manager
Vinod Mistry
Vinod Mistry Go-to-Market Leader — UK

Components

Ledger hero banner

Pattern ID: component-ledger-hero-banner · component: src/components/LedgerHeroBanner.astro

The page-opening dark field: a full-bleed photograph bled to all four edges, a navy veil heaviest at the left and bottom so the copy keeps contrast, a breadcrumb (or mono eyebrow), a large two-line display claim low-left, a short deck, one or two pill CTAs, and a mono micro-label strip along the bottom. It is the page’s FIRST dark field, and it must stay dark so the transparent SiteNav reads over it. This is the exact hero used by /industries (lifted and generalised here); the Life-Sciences segment and platform pages open on the same component. Reach for it on any new inner page’s hero instead of re-rolling the photo + veil + reveal stack.

Section claim goes here

The first deck paragraph sits here, set a step stronger than the rest, carrying the hero’s core claim.

A second, quieter paragraph can follow to orient the reader before the CTAs.

MONO · MICRO-LABEL · STRIP

Components

Ledger deep hero

Pattern ID: component-ledger-deep-hero · component: src/components/LedgerDeepHero.astro

The Ledger-system page opener: a ledger-face--deep navy field with the photograph dropped to a faint underlay (not a hero photo), the site’s one signature cyan→purple gradient spent here, an optional halftone texture plate, a two-column grid (eyebrow + display heading with a ledger-pill on the left, lead/body prose + one on-dark Button on the right), and an optional "parties" chip row — the doc’s subject stated as a row rather than a sentence. This is the exact hero used by /life-sciences/clinical-cros (lifted and generalised here); the same idiom opens /platforms/life-sciences. Reach for it on any new Ledger-system inner page instead of re-rolling the underlay + veil + gradient + halftone stack. Pair it with the lighter LedgerHeroBanner above when a full-bleed photo opener fits the page better.

Industry segment

Connect key teams, systems and data

The lead paragraph sits here, set stronger than the rest, carrying the hero’s core claim.

A supporting paragraph can follow to orient the reader before the call to action.

Information moves between

  • Party one
  • Party two
  • Party three
  • Party four

Components

Industry index row

Pattern ID: component-industry-index-row · component: src/components/IndustryIndexRow.astro

One row of the editorial-index spread first built on /industries — a full-bleed image plate on one side and a copy column (a mono kicker carrying the row’s two-digit code, a display title, one or more body paragraphs, and an arrow CTA) on the other. The sides alternate down the list, driven by each row’s index (even → image leads, odd → image trails) rather than a CSS :nth-child, so the zig-zag holds now each row is its own component. The two demo rows below show both sides; the second is the flipped "Education, Government and Nonprofits" row the pattern was extracted from. Reach for it on any new editorial index of sectors, services or case studies instead of re-deriving the plate + copy grid.

  1. Industry

    Section title goes here

    The first body paragraph sits here — one or two short sentences describing the row.

    A second paragraph can follow before the arrow link.

    Explore our services
  2. A civic bridge over a river beside a city

    Industry

    Education, Government and Nonprofits

    Educational institutions, government organizations and nonprofits often work across multiple systems, teams and processes while serving very different communities.

    We help organizations use Salesforce, data and AI to connect information, improve engagement and make everyday processes and services easier to manage.

    Explore our services

Components

Ledger pull section

Pattern ID: component-ledger-pull-section · component: src/components/LedgerPullSection.astro

A ledger-split--7-5 band: a copy column (mono eyebrow, display heading, one or more body paragraphs — the first set as the lead) on the left, and a ledger-pull statement pulled out of the measure with its leading edge ruled in the house highlight on the right. The band sits on a tinted ground and is capped top and bottom with the halftone dot-screen texture. This is the exact section used by /life-sciences/how-to-choose-a-salesforce-life-sciences-partner (the "Beyond certs" / "Look beyond certifications" §3), lifted and generalised here. Reach for it on any new page that needs a claim balanced against a short, pulled statement.

The texture is the shared pattern-halftone-caps primitive. The component bundles its three tunings as one halftone prop — halftone-cap-light, halftone-cap-bright, halftone-cap-on-dark — plus "none" to drop it. The three variants are shown back to back below (each on the ground it is tuned for).

Variant · light

Section claim goes here

The lead paragraph sits here, set stronger than the rest, carrying the section’s claim.

A second body paragraph can qualify or expand it.

A third paragraph can direct the reader toward what to ask or do next.

The pulled statement sits here, ruled on its leading edge, balancing the claim on the left.

Variant · bright

The bright halftone variant

The bright cap variant uses the solid house accent at a larger dot, for a light or surface ground where the quiet light variant reads as near-invisible.

Everything else about the band is unchanged — only the halftone tuning differs.

Pick bright when the light dot screen disappears into the ground.

Variant · on-dark

The on-dark halftone variant

The on-dark cap variant uses a white dot at reduced opacity, for a dark or navy ground. Pair it with face="deep" or face="ink".

On a dark face the pulled statement switches to the on-face ink automatically.

On a dark field the texture is white dots, dialled back so it reads as grain, not snow.

Components

Convergence diagram section

Pattern ID: component-convergence-diagram-section · component: src/components/ConvergenceDiagramSection.astro

A two-column band: a copy column (mono eyebrow, display heading, an italic lead and body paragraphs) beside a DIAGRAM that argues the claim — scattered SOURCE chips, hairline curves fanning IN to one point, and a single white record PLATE, so many sources resolve into one complete view. A looping signal pulse rides each curve so the sources read as data flowing into the record (gated behind prefers-reduced-motion). This is the exact diagram from /life-sciences/commercial-operations-hcp-engagement §2 ("A complete view" / "Build a more complete HCP view"), lifted here.

The diagram is kept verbatim but is now DYNAMIC: the chips, the curves, the pulses and the record rows are all derived from the sources / recordRows props, and the curve geometry is computed from sources.length — so the fan draws the right number of lanes for any list, not the five the page hard-coded. diagramSide places the diagram "right" (default) or "left". The two demos below show a 4-source fan on the right and a 6-source fan on the left.

A complete view

Build one complete view

Information can come from several systems — a CRM, past activity, events and other enterprise data sources.

The component brings the relevant pieces together so a team can understand the whole without searching across multiple systems.

The result is a clearer view of who the record is, what has happened and what needs attention.

  • Source A
  • Source B
  • Source C
  • Source D

Complete view

  • Who the record is
  • What has happened
  • What needs attention

Diagram on the left

Six sources, mirrored

With diagramSide set to left the fan-in takes the leading column and the copy runs on the right — the mirror of the default.

This demo also passes six sources, so the diagram draws six converging lanes instead of four — the geometry is computed from the source count.

  • Field
  • Medical
  • Events
  • Virtual
  • Digital
  • Service

Connected relationship

  • One connected relationship
  • Role-relevant context
  • The right controls

Components

Closing CTA band

Pattern ID: component-closing-cta-band · component: src/components/ClosingCtaBand.astro

The site’s second (and almost always final) dark field: a navy field over a photograph, one eyebrow, one heading, one or two body paragraphs, and one on-dark Button. This exact section — same gradient scrim, same type ramp — was hand-copied onto eight pages before ClosingCtaBand.astro existed: /about, /industries, /life-sciences/pharma-biotech, /life-sciences/cdmo-api-manufacturers, /life-sciences/medtech, /life-sciences/commercial-operations-hcp-engagement, /services/ai-and-data-strategy and /accelerators/lead-capture-agent — all eight now render through the shared component. Reach for it on any new page’s closing section instead of re-deriving the two-layer gradient style= block.

Contact

Section claim goes here

Body copy sits here — one or two short paragraphs that invite the next step.

Talk to us

Components

Marquee strip

Pattern ID: component-marquee-strip · component: src/components/MarqueeStrip.astro

A slow looping mono-label ticker for dark bands (props: items, rule, class). Used on /leadership.

Components

Platform toolkit section

Pattern ID: component-platform-toolkit-section · component: src/components/PlatformToolkitSection.astro

The house 7/5 "Platforms" band: a claim column on the left (mono eyebrow, display heading, one or more body paragraphs, an optional arrow CTA) beside a two-up grid of calm paper tiles on the right, each tile a brand mark + the platform name over a masked blueprint grid (.plat-tile / .hstat-grid / .plat-mark). This exact section — same grammar, tile for tile — was hand-copied onto four Life Sciences pages before this component existed: /life-sciences/medtech, /life-sciences/pharma-biotech, /life-sciences/cdmo-api-manufacturers and /life-sciences/commercial-operations-hcp-engagement — all four now render through the shared component. Reach for it on any new page that needs to present a "technology we bring together" toolkit.

Each tile carries EITHER a logo (a brand mark in /public, the common case) OR an icon (inline SVG path data for an abstract capability with no brand mark, the house .jicon convention) — logo XOR icon. The demo below mixes both so the fallback glyph slot is visible.

Platforms

Technology that supports the business

Our work can bring together these platforms.

The technology depends on the problem we’re solving, not the other way around.

Explore our platforms
  • Life Sciences
  • Data 360
  • Databricks
  • Claude
  • Tableau
  • MuleSoft
  • A capability with no brand mark

Components

Stage deck section

Pattern ID: component-stage-deck-section · component: src/components/StageDeckSection.astro

The "How we deliver" band: a ledger-face--panel ground wrapping a ledger-split items-end heading row (mono eyebrow + display heading) above the shared LedgerStageDeck — a Swiper carousel of white cards, each with an oversized mono index, a serif title, a one-line description and a category-tinted progress bar. This exact band was hand-written on three Ledger pages before this component existed: /services/salesforce-implementation ("From requirements to everyday use"), /platforms/life-sciences ("From opportunity to working agent") and /life-sciences/move-to-life-sciences-cloud ("Move in clear stages"). Reach for it on any new page that lays a method out as an ordered run of stages.

The stage cards themselves stay in LedgerStageDeck (its Swiper deck, controls, no-JS fallback and card CSS); this component owns only the surrounding section and forwards the deck props through. Pass linkLabel to add the trailing "the method, in full" link on the deck’s control row (the agentforce page uses it; the other two don’t).

How we deliver

From requirements to everyday use

01

Understand

Learn the business processes, users, systems and goals.

02

Design

Define how the platform should support the work.

03

Build

Configure the platform around the agreed requirements.

04

Connect

Integrate the systems and data the process depends on.

05

Test and validate

Confirm that workflows, integrations and data work as expected.

06

Launch

Prepare users and move the solution into everyday use.

07

Improve

Continue supporting and evolving the platform after go-live.

Components

Approach quote band

Pattern ID: component-approach-quote-band · component: src/components/ApproachQuoteBand.astro

The Ledger case-study "quote-band" composition on the house surface panel: a mono eyebrow + display heading, then a two-column row — a narrow image plate (~30%) on the left and, on the right, a large pulled display statement, a supporting paragraph and an optional arrow link. This is the exact section used by /industries §3 ("One approach" / "Technology that adapts to the business"), lifted and generalised here. Reach for it on any new page that balances a short, pulled claim against a supporting image.

The statement and support strings may carry HTML entities / smart quotes. The arrow link is optional: pass link and leave showLink at its default, or set showLink={false} to drop it on a page that has no target route yet. Set headingId to wire the heading’s aria-labelledby, or omit it (as /industries now does) for no id.

One approach

Section heading goes here

A connected city at work across many sectors
“The industry may change, but our approach stays consistent.”

We start with the business problem, understand the processes and systems around it, and then bring together the Salesforce, data, AI and integration capabilities needed to solve it.

Explore our platforms

Components

Data foundation console

Pattern ID: component-data-foundation-console · component: src/components/DataFoundationConsole.astro

The house 7/5 "console" band: a claim column (mono eyebrow, display heading, an italic lead, one or more body paragraphs, an optional arrow CTA) beside a frosted-glass console — a panel floating on an ambient background image, with a mono cap label, a stack of cards and an optional dashed base row (.df-scene / .df-panel / .df-cap / .pf-card). This is the exact section used by /life-sciences/pharma-biotech §7 ("Build a stronger data foundation"), lifted and generalised here. Reach for it on any new page that presents a layered "platforms / data / governance" stack.

Two card variants, picked by cardVariant: "platform" (default — larger single-label cards with an optional brand tint key: sf · d360 · dbx — paired with a dashed base row) and "task" (tighter, smaller-label cards for a list of short phrases, usually no base). The same page’s §8 "AI, applied" band is the task variant. mediaSide ("right" default | "left") flips which column the console takes. The two demos below show both variants, mirrored.

Data foundation

Build a stronger data foundation

The italic lead sits here, framing the console alongside it.

A body paragraph carries the claim in house body voice, naming the platforms and sources the console stacks together.

Explore data and analytics
Reporting · Analytics · AI
Salesforce
Other enterprise data sources
Data 360
Databricks

AI, applied

Put AI to work on specific tasks

The task variant uses tighter, smaller-label cards for a list of short phrases, and (usually) no base row.

This demo also sets mediaSide=“left”, so the console takes the leading column and the copy runs on the right — the mirror of the default.

Explore AI and agents
Business rules · Access controls · Human oversight
Process inquiries
Review documents
RFQ Response
Find information
Prepare the next action

Backgrounds

Dark-room ground

Pattern ID: bg-pattern-darkroom-ground

A photographic field, a navy veil deepening the edges, and an inverted white blueprint grid laid over the top — the dark "room" treatment used by the homepage’s "Start with the problem" section, the CDMO page’s "Process RFQs faster" section, and (currently) the MedTech page’s "Help field teams work with better information" section. Pull the three ground layers and the on-dark text ramp below onto any section that needs this effect — only the content inside changes.

Eyebrow

Section claim goes here

A short italic lead line sits here, same treatment as the lead paragraph in the sections that use this ground.

Body copy runs at white/70 against the veil so it clears contrast without competing with the brighter lead line above it.

Example link

Patterns

Halftone edge caps

Pattern ID: pattern-halftone-caps · variants: halftone-cap-light, halftone-cap-bright, halftone-cap-on-dark

A dot-screen strip masked to fade inward from an edge — the same texture SiteFooter uses, and the one PrincipleStatement puts on both the top and bottom of its band (ledger-halftone-cap + ledger-halftone-cap ledger-halftone-cap--bottom). Three named variants below bundle a dot colour/size/tile tuning for the ground the cap sits on, so a page reaches for a class instead of re-deriving an inline style every time.

light

On paper / white

bright

On surface tint

on-dark

On a dark field

Components

Takeaway card list

Pattern ID: component-takeaway-card-list · component: src/components/TakeawayCardList.astro

A 5/7 split on a blurred blue-wash ground: an eyebrow glass chip, a heading, an optional italic lead and body on the left; a mono lead-in line and a stacked list of frosted-glass cards — each with a circular accent icon badge and a tabular index — on the right. Reach for it when a section needs to present a short, ordered set of "what you get" / "what to ask" items as scannable cards rather than prose. All copy is prop-driven and each item supplies its own inner SVG icon path.

Deliverables

Section claim goes here

A short italic lead sits here, orienting the reader before the cards.

An optional body paragraph adds one more line of context under the lead.

A preview list can include

  • First takeaway card, with its own accent icon badge.
  • Second takeaway card in the stacked, scannable list.
  • Third takeaway card closing out the sample set.

Components

Principle statement

Pattern ID: component-principle-statement · component: src/components/PrincipleStatement.astro

A centered single-statement band on a white ground: a mono eyebrow with a trailing slash at the top, one large centerd serif statement below it (with an optional <mark> highlight pill on the operative phrase), and a halftone dot screen capping the top and bottom edges. Reach for it when a page needs its one sharp “principle” or stance line to stand alone as a quiet band between denser sections. The statement is passed via the default slot so each page keeps its own sentence and places its own <mark>. Live on /life-sciences/clinical-cros, /platforms/life-sciences, /life-sciences/medical-affairs and /services/salesforce-implementation.

An optional link prop ({ label, href? }) renders a single centerd ledger-link (arrow glyph) BELOW the statement, inside the same band, so a page’s principle line and its follow-on CTA read as one section. Omit it and no link renders; href defaults to "#". The preview below demonstrates the link-enabled variant.

Principle

The goal isn’t to replace specialized systems. It is to make the processes around them work better together.

Components

Ledger logo-plate grid

Pattern ID: component-ledger-logoplate-grid · component: src/components/LedgerLogoPlateGrid.astro

A soft-teal Ledger "stack band" capped by a halftone dot screen: a label rail on the left (eyebrow + serif heading + lead-in) and, on the right, a grid of brand logo-plates (the headline plate can span two tracks via wide), a closing line and a trailing arrow link. Reach for it to present a technology stack or capability set as branded chips rather than a bullet list. All copy is prop-driven and each plate rides an existing /public logo.

The stack

Section claim goes here

A sample stack can span:

  • Platform Core platform
  • Analytics Analytics
  • Integration Integration

The right combination depends on the process, systems and information already in place.

Explore the stack

Components

Opportunity media plate

Pattern ID: component-opportunity-media-plate · component: src/components/OpportunityMediaPlate.astro

A 7/5 split: a claim on the left (eyebrow + heading + optional italic lead + body paragraphs + optional arrow link) and, on the right, a house media card carrying a photo with a floating frosted "plate" that lists supporting points (its live dot is motion-gated). Reach for it to pair a narrative claim with an image and a short captioned callout. All copy is prop-driven and the image is an existing /public asset.

Where to look

Section claim goes here

A short italic lead sits here, framing the media card alongside it.

A first body paragraph carries the claim in house body voice.

A second, quieter paragraph can follow before the arrow link.

Example link
Supporting points
  • First floating-plate row
  • Second floating-plate row
  • Third floating-plate row

Components

Info-work card grid

Pattern ID: component-info-work-card-grid · component: src/components/InfoWorkCardGrid.astro

An index-labelled card run on the house grid-blueprint ground: a mono eyebrow + serif heading + optional lead introduce a real <ul> of white cards, each carrying a mono index label, a serif title, a one-line body, and a hairline footer with a derived descriptive tag plus an arrow that reveals on hover. Reach for it to lay out a run of short, labelled "where this fits" items without inventing numbers. Rendered in the Megnity palette; live on /services/ai-agents block 06. It renders NO fabricated metrics, statistics, or promotional badges — only the prop strings passed in appear.

Where it helps

Information-heavy work this fits

A short lead sentence introduces the card run.

  • P.01

    First card title

    A one-line body describing the first item.

    Category
  • P.02

    Second card title

    A one-line body describing the second item.

    Category
  • P.03

    Third card title

    A one-line body describing the third item.

    Category

An optional quiet closing line can follow the grid.

Components

Environment mosaic

Pattern ID: component-environment-mosaic · component: src/components/EnvironmentMosaic.astro

A 5/7 split with ALL the copy in the left column (eyebrow + serif heading + lead/body + optional arrow link) and, on the right, a STAGGERED two-column mosaic of mixed tiles. "Label" tiles are glass cards floating on a blurred background photo under an accent-tint veil (the house blue identity); "media" tiles are sharp placeholder photos with a mono caption. The component deals the tiles into two columns in order and offsets the second down, so a four-tile list reads as a composed board. Reach for it to contrast two environments or facets (first used for "Connect Salesforce and Databricks" — operational vs analytical). All copy is prop-driven and the images are existing /public assets.

A + B

Section claim goes here

A lead sentence frames the two environments the mosaic contrasts.

A supporting paragraph can follow, then a quieter third before the link.

A third line sits here in house body voice.

Example link

First

Sub-label

A short description of the first environment.

Photo caption /
Photo caption /

Second

Sub-label

A short description of the second environment.

Components

Claim plate split

Pattern ID: component-claim-plate-split · component: src/components/ClaimPlateSplit.astro

The house 7/5 split with the CLAIM in one column (mono eyebrow, display heading, an optional italic serif lead, body paragraphs and an OPTIONAL arrow link) and a single picture in the house .plate instrument shell — white, one hairline, generous radius, navy-tinted shadow — in the other. It is the quiet counterpart to OpportunityMediaPlate : no floating frosted plate, no pulse, no list, just a readable claim balanced against one framed visual. This is the exact section used by /services/salesforce-implementation ("Useful data" / "Bring data into the picture", §6), lifted and generalised here. Reach for it on any section that needs a claim beside a supporting (often decorative) image instead of re-rolling the split + plate shell.

All copy is prop-driven. cta, eyebrow and lead are each optional; mediaSide flips the split so the picture can lead on alternating sections; mediaSpan (4/5/6) narrows the picture column and the claim takes the remainder; ground picks the section ground (paper / surface / blueprint / none) so a page’s light-loud alternation holds. The three demos below show the source arrangement, a flipped link-free variant, and a narrowed blueprint-ground variant.

Useful data

Bring data into the picture

The italic serif lead sits here, carrying the section’s claim in one sentence.

The first body paragraph follows, describing what the claim means in practice for the reader.

A second paragraph can name the systems, products or people involved before the link.

Example link

Variant · picture leads, no link

The same band, flipped and link-free

Pass mediaSide="left" and the picture takes the leading column on desktop, so consecutive sections can alternate. On small screens the claim always reads first.

Omitting the cta prop drops the arrow link entirely — correct for a section whose claim has no onward destination.

Narrowed picture on the blueprint ground

mediaSpan={4} shrinks the picture column to a third and the claim column widens to 8, for a section whose copy carries most of the weight.

ground="blueprint" lays the house guide-line texture under the band; eyebrow and lead are both omitted here.