--- title: Tick Social case study description: MXTOK Case study · 2025 A short-video platform delivered in 6 working days. Tick Social needed a short- url: https://miracuves.com/portfolio/tick-social date_modified: 2026-08-18 author: miracuves language: en_US --- MXTOK Case study* · 2025* # A short-video platform delivered in 6 working days. Tick Social needed a short-video platform. The TikTok Clone base already carried the mechanics, so the engagement went where their product was actually different. We built the product; they launched the brand. - **TikTok Clone** · MXTok - **6 working days** our build time on the base - **Source code transferred** to Tick Social’s own account [Read the case study](#summary) [Start a project](https://miracuves.com/schedule-consultation/) *TS***Tick Social***TikTok Clone · 2025* *TS***Tick Social** SolutionTikTok Clone ProductMXTok Delivered2025 StackPHP LARAVEL · MYSQL · FLUTTER Build time6 working days Blocks reused18 of 22 Source codeTransferred **4**applications shipped **18**blocks reused unchanged **4**built for this client **9**integrations, each isolated **100%**source code transferred [Summary](#summary)[Scope](#scope)[Brief](#brief)[Discovery](#discovery)[Challenges](#challenges)[Strategy](#strategy)[What we built](#built)[Architecture](#architecture)[Reused](#reused)[Decisions](#decisions)[Process](#process)[Product](#surfaces)[Security](#security)[Integrations](#integrations)[Stack](#stack)[Timeline](#timeline)[Scale](#scale)[Results](#results)[Handover](#handover)[FAQ](#faq) Viewer*Content policy*Creator*Ranking weights*Manager*Creator programme*Admin*Brand & theming*API gatewayViewer*Content policy*Creator*Ranking weights*Manager*Creator programme*Admin*Brand & theming*API gateway ## What already existed, and what did not. The distinction that decides a project like this: the mechanics were proven before the engagement started, so the time went into the part that was theirs. We build the product; the client launches the brand. That is the arrangement, and it only works if the handover is real: Tick Social owns the source code, had a launch date in writing before work started, and can check every figure on this page against a public ledger. Starting from a base that already ran elsewhere took the risk out of the feed, upload pipeline and creator tools. We spent the time on our content policy and creator programme, which is the only part our customers can see. Tick Social team, Founding team · Tick Social Reuse on this build Blocks reused18 of 22 Built for Tick Social4 Solution familyTikTok Clone Other builds on it0 ## The line between reused and built. The work sat where it always sits on this base: content policy, ranking weights, creator programme. Everything else on the list below arrived already built and proven on other engagements running the same base. **4**Applications and consoles shipped, each with its own permissions and release path*Delivered* **18**Platform modules reused unchanged from the TikTok Clone base*Delivered* **4**Decisions built for Tick Social: content policy, ranking weights, creator programme*Delivered* **3**Environments: development, staging and production*Delivered* **100%**Source code transferred to Tick Social’s own account*Contractual* ## What Tick Social actually needed. A short-video platform is not one feature. It is 22 distinct pieces that all have to work together before a single customer can be served, and most of them already existed and had been proven elsewhere. That distinction decides the shape of a project like this. A business does not need a dispatch engine or a settlement ledger to be invented again; it needs one that already works, then it needs the handful of decisions that make the product theirs rather than anyone else’s. The four below are the load-bearing pieces Tick Social would otherwise have spent months building before proving anything to a customer. Every platform of this kind has the same shape underneath: a set of load-bearing parts that must be correct before a single customer can be served, and a much smaller set of decisions that make it one business rather than another. Building the first set from zero would have consumed the window before the second was even discussed. That is the decision this engagement turned on, and it was taken before any code was written. **Viewer**feed, follow, react **Creator**record, edit, publish **Manager**talent, campaigns, rights **Admin**moderation, payouts ## What we settled before building. Which of the 22 pieces were already solved, and which were genuinely Tick Social’s to decide. Getting that line in the right place before any code is written is what keeps a TikTok Clone engagement short, and it is the conversation we would rather have honestly than optimistically. Where a scope genuinely does not fit a proven base, we say so during scoping and quote it as a custom build instead, even when that costs us the larger and more comfortable project. *01* #### Read the requirement back to first principles What must exist at launch, separated from what a business can add once it has customers. Those are different lists and conflating them is what makes projects run long. *02* #### Base versus build, capability by capability Each of the 22 capabilities assessed against the existing base as covered, partial or absent. Partial is treated as absent, because a half-fitting module costs more than a new one. *03* #### Mark what only Tick Social could decide 4 decisions were commercial or jurisdictional rather than technical. Those were theirs, and the engagement is where they got implemented. *04* #### Agree the line before writing anything 18 pieces reused unchanged, 4 built. Fixing that line up front is what turns a platform of this size into a six-working-day build. ## The parts that are genuinely hard. Not marketing difficulty, actual difficulty. These are the problems any serious TikTok Clone has to solve properly, and the reason building one from a blank page is a multi-quarter commitment rather than a sprint. Each was solved once, on the base, and has been under load on other builds since. Tick Social inherited the solutions rather than the problems. 01 ### Capture quality on cheap phones Recording, effects and sound have to work on the devices the audience actually owns, not the ones the team tests on. **Already solved in the base:** Viewer 02 ### Ranking shapes the platform Interest, recency and watch time decide reach, and reach decides who keeps creating. The weights are a product strategy, not a setting. **Already solved in the base:** Creator 03 ### Moderation at upload speed Policy has to be enforced as content arrives, because after it is seen the damage is already done. **Already solved in the base:** Manager ## What we did not have to build for Tick Social. Every platform is made of the same mechanics underneath. This is the account of which of them Tick Social paid attention to, and which were already solved. Built from nothing, Tick Social would have meant paying for the mechanics again: the accounts, the sessions, the payments, the admin, the permissions. That work is real, it is slow, and none of it is what makes this product different from the next one. Starting from the TikTok Clone base moved that cost out of the project entirely, and the platform itself was deployed in 6 working days. What that bought is attention. The engagement went into the 4 parts that were actually different, instead of being spread thin across 22 of them. **Shipped ready-made***18 of 22* *01***Viewer**feed, follow, react *02***Creator**record, edit, publish *03***Manager**talent, campaigns, rights *04***Admin**moderation, payouts *05***API gateway**auth, rate limits, *06***Realtime channel**live counts, gifts *07***Event bus**transcode jobs, *08***Capture**record, effects, sound *09***Upload & transcode**renditions, thumbnails *10***Moderation**policy, automated checks *11***Post catalogue**posts, owners, *12***Feed ranking**interest, recency, watch *13***Social graph**follows, likes, shares *14***Gifts & ads**creator share, splits *15***Analytics**reach, retention, *16***store**posts, accounts, *17***realtime**feeds, counters, *18***Object storage**masters, renditions **Made for Tick Social***4 of 22* *01***Content policy**what you allow *02***Ranking weights**what your feed rewards *03***Creator programme**how creators earn *04***Brand & theming**the app Build all 22 from nothing, mechanics included 18 already solved, so the effort went to the 4 that were not The account Shipped ready-made18 Made for this client4 Parts in total22 Build window6 working days The ready-made side is not a shortcut taken on quality. It is work that was already finished, and finished work does not get charged for twice. ## Everything that shipped with it. The full working set Tick Social took delivery of. Each piece was already built and proven on other engagements before this one started, which is the only honest reason a platform of this size stands up in six working days rather than months. None of it is a demo or a scaffold. These are the same components running under other businesses in other markets, which means the failure modes are already known and already handled rather than waiting to be discovered by Tick Social’s first real customers. ### Reused from the TikTok Clone base **Viewer**feed, follow, react **Creator**record, edit, publish **Manager**talent, campaigns, rights **Admin**moderation, payouts **API gateway**auth, rate limits, **Realtime channel**live counts, gifts **Event bus**transcode jobs, **Capture**record, effects, sound **Upload & transcode**renditions, thumbnails **Moderation**policy, automated checks **Post catalogue**posts, owners, **Feed ranking**interest, recency, watch **Social graph**follows, likes, shares **Gifts & ads**creator share, splits **Analytics**reach, retention, **store**posts, accounts, **realtime**feeds, counters, **Object storage**masters, renditions ### Built for Tick Social **Content policy**what you allow **Ranking weights**what your feed rewards **Creator programme**how creators earn **Brand & theming**the app ## The base this was built on. The same architecture carries every TikTok Clone on this page. The filled blocks are the parts built for Tick Social. **TikTok Clone architecture** MXTok / filled = built for this client TikTok Clone: the architecture, and one post traced through it 4 client surfaces reach an edge of gateway, realtime channel and event bus. The base holds 8 services, of which Post catalogue is the source of truth, and 4 blocks are built for each client. Partner services sit behind a boundary and are chosen by the client. Underneath, one post is traced across 5 steps. 18 of 22 blocks are reused unchanged. .fdiag{--dg-ink:#1c1618; --dg-sub:#6e6264; --dg-rule:#e3d2d5; --dg-rail:#faf5f6; --dg-card:#ffffff; --dg-accent:#a70d2a; --dg-track:#efe9ea; --dg-made:#a70d2a; --dg-made-ink:#ffffff; --dg-zone:rgba(28,22,24,.028); --dg-zone-core:rgba(167,13,42,.05); --dg-zone-line:#e3d2d5; --dg-zone-core-line:#f0c9d1} .lbl{font-size:13px;font-weight:700;fill:var(--dg-ink);letter-spacing:-.014em} .sub{font-size:10.5px;fill:var(--dg-sub)} .note{font-size:10px;fill:var(--dg-sub);font-style:italic} .mono{font-family:'JetBrains Mono',ui-monospace,monospace;font-size:10px; letter-spacing:.14em;text-transform:uppercase;font-weight:500;fill:var(--dg-accent)} .zn{font-family:'JetBrains Mono',ui-monospace,monospace;font-size:10px;font-weight:500; letter-spacing:.13em;text-transform:uppercase;fill:var(--dg-sub)} .zn.zh{fill:var(--dg-accent)} .tag{font-family:'JetBrains Mono',ui-monospace,monospace;font-size:7.5px;font-weight:500; letter-spacing:.1em;fill:var(--dg-accent)} .h2{font-size:30px;font-weight:800;fill:var(--dg-ink);letter-spacing:-.034em} .deck{font-size:13px;fill:var(--dg-sub)} .zone{fill:var(--dg-zone);stroke:var(--dg-zone-line)} .zone-core{fill:var(--dg-zone-core);stroke:var(--dg-zone-core-line)} .card{fill:var(--dg-card);stroke:var(--dg-rule)} .auth{fill:var(--dg-card);stroke:var(--dg-accent);stroke-width:2} .made{fill:var(--dg-made);stroke:none} .made-l{fill:var(--dg-made-ink);font-size:13px;font-weight:700;letter-spacing:-.014em} .made-s{fill:var(--dg-made-ink);font-size:10.5px;opacity:.95} .step{fill:var(--dg-card);stroke:var(--dg-rule)} .dot{fill:var(--dg-accent)} .dotn{fill:#fff;font-family:'JetBrains Mono',ui-monospace,monospace;font-size:11px;font-weight:500} .flow{stroke:var(--dg-rule);stroke-width:1.5;fill:none;marker-end:url(#mxtok-ar)} .hot{stroke:var(--dg-accent);stroke-width:2;fill:none;marker-end:url(#mxtok-ah);opacity:.55} .cnt{font-family:'JetBrains Mono',ui-monospace,monospace;font-size:10px; letter-spacing:.1em;fill:var(--dg-sub)} TikTok Clone MXTok One documented build runs on this base. Only the filled blocks are built for you. Ships ready-made Built for this client Surfaces Edge The base - already built Partner boundary Data Viewer feed, follow, react Creator record, edit, publish Manager talent, campaigns, rights Admin moderation, payouts API gateway auth, rate limits, devices Realtime channel live counts, gifts Event bus transcode jobs, fan-out Capture record, effects, sound Upload & transcode renditions, thumbnails Moderation policy, automated checks Post catalogue posts, owners, eligibility SOURCE OF TRUTH Feed ranking interest, recency, watch time Social graph follows, likes, shares Gifts & ads creator share, splits Analytics reach, retention, earnings Built for this client Content policy what you allow Ranking weights what your feed rewards Creator programme how creators earn Brand & theming the app chosen by the client Transcoding their encoder CDN their edge network Moderation service their classifier Payments their gateway Push & email their sender Transactional store posts, accounts, ledger Cache & realtime feeds, counters, sessions Object storage masters, renditions one post, end to end every step below runs on blocks that already existed 1 Capture record, effects, sound 2 Upload transcode, thumbnails 3 Screen policy checks before reach 4 Rank interest, recency, watch time 5 Earn gifts and ad share credited PHP LARAVEL · MYSQL · FLUTTER 18 of 22 blocks reused unchanged 4 built for you This is the TikTok Clone base, drawn as it was actually assembled for Tick Social. The plain blocks are the ready-made platform and shipped as they are. The filled blocks are the ones we built for this client. 18 of 22 blocks were reused, 4 were built. ## Why none of this had to be written again. Each of these was already running on other builds of the same base before Tick Social started. That is the whole reason the platform was standing in days rather than months. **Viewer**feed, follow, react **Creator**record, edit, publish **Manager**talent, campaigns, rights **Admin**moderation, payouts **API gateway**auth, rate limits, **Realtime channel**live counts, gifts **Event bus**transcode jobs, **Capture**record, effects, sound **Upload & transcode**renditions, thumbnails **Moderation**policy, automated checks **Post catalogue**posts, owners, **Feed ranking**interest, recency, watch **Social graph**follows, likes, shares **Gifts & ads**creator share, splits **Analytics**reach, retention, **store**posts, accounts, **realtime**feeds, counters, **Object storage**masters, renditions ## The decisions that were actually theirs. A ready-made base does not remove these; it removes everything underneath them. Each one below is a choice Tick Social had to make, and the engagement is where those choices got implemented. **01** ### Content policy What is allowed on the platform, and how it is enforced. **Why it sat with them**Where the line sits is theirs to draw, and it moves with their audience. We built the controls and left the thresholds to them. **02** ### Ranking weights Configured for Tick Social during the engagement. **Why it sat with them**Commercial rather than technical. The base already handles the mechanics underneath, so the engagement is where their own answer gets implemented. **03** ### Creator programme Configured for Tick Social during the engagement. **Why it sat with them**Who is allowed to sell here is a commercial and legal question about their own market. No base can pre-answer it. **04** ### Brand & theming The identity carried across every surface, so it reads as the client’s product rather than a template. **Why it sat with them**The base has to disappear behind their identity, so this is applied across every surface rather than skinned on one. ## What the six days actually cover. Our build time on a ready-made base, and nothing else. The parts that sit with the client are named plainly. Phase 01Phase 02Phase 03Phase 04 01 ### White-label The base is rebranded to the client’s identity across every surface. 02 ### Deploy Stood up on the client’s own hosting, not ours. 03 ### Publish Apps submitted from the client’s own developer accounts. 04 ### Handover Source, schema, deployment configuration and architecture notes transferred. The client supplies the hosting and domain, a verified developer account we publish from, branding and business details, an onboarded payment gateway with KYC complete, and any third-party API keys. Store review and merchant onboarding are controlled by Apple, Google and the payment provider, so those sit outside our window. [Every figure here is defined on the facts page](https://miracuves.com/facts/#fact-005). ## Who uses it, and for what. Rather than screenshots of a product that has moved on since delivery, this is the set of surfaces that shipped and what each one is for. Tick Social received every one of them, with the source behind each. Every role here is a separate application with its own permissions, its own state and its own release path. Building them to work as one system is most of the engineering in a platform of this kind, and it is the part that was already finished before this engagement began. Viewer feed, follow, react Creator record, edit, publish Manager talent, campaigns, rights Admin moderation, payouts ## What guards the platform. Built into the base and hardened across every engagement running it, rather than bolted on at the end of this one. Security added late is security that has to be argued for; the controls below were load-bearing from the first deployment. We claim the process, not a certificate. Miracuves does not hold ISO 27001, and we do not say otherwise: we build to the controls those frameworks require, and the evidence trail is there for an auditor who asks. #### Moderation policy, automated checks. Part of the base, so it was proven before this engagement started. #### Role separation Each surface sees only what its role permits, enforced server-side rather than hidden in the interface. #### Audit trail Who changed what and when, retained so a dispute can be answered with a record rather than a recollection. #### Transport and storage TLS end to end, credentials hashed, and anything sensitive at rest encrypted rather than merely obscured. #### Secrets handling Keys live in environment configuration on their own infrastructure, never in the repository we hand over. #### Card data stays out Payment details go to the gateway directly. The platform holds a reference, not a card number. #### Backups and restore Scheduled backups with a restore that was actually run, because an untested backup is a guess. #### What an auditor can actually see We claim the process, not a badge. Everything below was handed to Tick Social with the source. - Commit history for every change in the build window - Environment configuration separated from application code - Database schema with the migration that produced it - Deployment steps written down rather than remembered - Named team and a daily written progress record ## What it connects to. The connection points are part of the base and were already written and tested. Which providers sit behind each one was Tick Social’s decision, because those choices are commercial and jurisdictional rather than technical. This is also where the client-side dependencies live. Gateway onboarding, KYC approval and merchant review are controlled by the provider, not by us, which is why they sit outside the build window rather than inside it. Every one of these was already wired and tested in the base. What changed for Tick Social was which account sat on the far side of it. **Payments and payouts**gateway of their choosing **Object storage and CDN**their bucket, their region **Product analytics**events, funnels, retention **Media pipeline**transcode and delivery **Search and indexing**catalogue, filters, ranking **Market data feeds**rates and reference prices **Push and transactional email**sent under their sender identity **App store developer accounts**published from their own accounts **Error and uptime monitoring**handed over with the source ## What it runs on. The platform stack for MXTok. This describes the base as it stands today; Tick Social took delivery of the source and has owned it since. **Platform**PHP LARAVELMYSQLFLUTTER The stack the MXTok base runs on, already in production elsewhere **Surfaces**ViewerCreatorManagerAdmin Each a separate application with its own permissions and release path **Client decisions**Content policyRanking weightsCreator programmeBrand & theming Configured for Tick Social during the engagement **Handover**SourceSchemaDeployment configArchitecture notes Transferred at the end of the build ## Where the six days went. Our build time only. Store review and merchant onboarding are controlled by Apple, Google and the payment provider, so they sit outside this window and we do not count them as ours. Stating that plainly is the difference between a build time and a promise we cannot keep. [Every figure here is defined on the facts page](https://miracuves.com/facts/#fact-005). The six working days are guaranteed. If a ready-made platform is not live in six, we keep working free until it is. A deadline nobody is accountable for is not a deadline, and a guarantee nobody pays for is not a guarantee. Throughout, a named team worked the build and sent Tick Social progress on WhatsApp every working day. There was never a week where nobody knew where it stood, which is the part clients tell us they notice more than the date itself. **6 working days** our side of the window The bar below is that window, day by day. Nothing outside it is counted as ours, and nothing inside it waits on someone else. #### What Tick Social supplied A build window only holds if both sides arrive ready. These sat with them, and the clock does not start until they are in place. - Hosting and a domain, on their own account - A verified developer account we publish from - Branding and business details - A payment gateway onboarded, with KYC complete - Third-party keys for the services they chose **Day 1**Base stood up and white-labelled*Base stood up and white-labelled* **Days 2-4**4 client decisions implemented*4 client decisions implemented* **Day 5**Deployed, apps submitted*Deployed, apps submitted* **Day 6**Source, schema and config handed over*Source, schema and config handed over* ## This base has done this before. Tick Social was not the experiment. The base underneath this build had already carried other businesses in other markets before it carried theirs, which is the whole argument for reuse: the risk was retired by somebody else’s project, not by this one. Across everything delivered since 2010 that is more than 9,000 products for over 6,000 businesses across 35+ industries. The eighty-four documented on this site are the ones with a named client and permission to show the work; most of the rest sits under NDA or white-label and is deliberately not here at all. Every number on this page is defined and sourced on a public facts ledger. That is the whole instinct behind how this company is run: most vendors ask you to trust them, and we would rather you checked us. If we cannot back a claim, we do not make it, which is why you will not find a satisfaction percentage or an unnamed award anywhere on this site. **18 of 22** Blocks reused unchanged on this build, each already under load on other engagements. *Architecture* **1** Documented builds running on the TikTok Clone base, in different markets. *Portfolio* **9,000+** Products delivered for more than 6,000 businesses across 35+ industries since 2010. *Company record* **3,900+** Apps published under clients’ own brands, counted per store release. *Company record* ## What we can state plainly. No client figures were supplied for this build, so these are architectural and contractual facts rather than outcomes. **Source code transferred** blocks reused unchanged Full repository history, to the client’s own account Miracuves delivery record **6 working days**Our build time on the ready-made base **6 working days**Our build window on this engagement.Miracuves delivery record **100%**Source code transferred to Tick Social’s own account.Contractual TS > Starting from a base that already ran elsewhere took the risk out of the feed, upload pipeline and creator tools. We spent the time on our content policy and creator programme, which is the only part our customers can see. > > > **Tick Social team**Founding team, Tick Social ## What Tick Social holds now. The same on every engagement. What happened to the platform after handover was theirs to decide. *GIT***Application source**Full repository history, transferred to their account*Delivered* *APP***Mobile projects**Sources with signing documented*Delivered* *SQL***Schema and migrations**Reproducible from empty, not a dump*Delivered* *ENV***Deployment configuration**Another team can run it unaided*Delivered* *MD***Architecture notes**What was chosen, what was rejected, why*Delivered* *60d***Support window**Sixty days included, six and twelve month options*Delivered* ## The questions that decide this. Answered for this build. The same answers hold for every TikTok Clone in the portfolio. Do we own the code? Yes. The full repository history transferred to Tick Social’s own account at handover, with deployment configuration and architecture notes. It is not a licence and it is not held against a support contract. How is six working days realistic? Because 18 of the 22 pieces were built and proven before the engagement started. The six days are our build time on that base, not a calendar promise. What sat with Tick Social? Hosting and domain, a verified developer account we publish from, branding and business details, an onboarded payment gateway with KYC complete, and any third-party API keys. Will it look like everyone else’s? No. The base supplies mechanics, not identity. Branding, flows and every customer-facing screen were built for this product. Is this what the platform looks like today? This describes what was delivered in 2025. What happened afterwards was Tick Social’s to decide; the source transferred at handover. Clients move on, rebuild, or sell up, and none of that changes what was delivered or how it went. Would you have said no to this project? We are a good fit for a founder who wants a proven model launched fast, a deadline they can hold us to, and code they own outright. We are a poor fit for anyone who needs a team embedded in their office full-time, or who wants a blank page and a six-month roadmap. Being straight about that up front saves everyone a call. Who actually worked on it? A named team, not a rotating pool. Our leadership is public with real profiles rather than a stock-photo team page, and progress went to Tick Social on WhatsApp every working day of the build. ## Building something like this? Tell us what you are building and we will say plainly whether a ready-made base fits it, including when the answer costs us the larger project. [Book a technical call](https://miracuves.com/schedule-consultation/) [See all case studies](/portfolio/) - Ready-made platform deploys in 6 working days - Custom builds run 2 to 8 weeks - Source code transfers on every engagement - [Every figure here is defined on the facts page](https://miracuves.com/facts/#fact-005) (function(){ var reduce=matchMedia('(prefers-reduced-motion: reduce)').matches; /* read-progress bar */ var bar=document.getElementById('progbar'); if(bar){ var prog=function(){var h=document.documentElement.scrollHeight-innerHeight; bar.style.width=(h>0?(scrollY/h)*100:0)+'%';}; addEventListener('scroll',prog,{passive:true}); prog(); } if(!('IntersectionObserver' in window)) return; /* reveal on scroll */ if(!reduce){ document.documentElement.classList.add('js-anim'); var io=new IntersectionObserver(function(es){es.forEach(function(e){ if(e.isIntersecting){e.target.classList.add('in');io.unobserve(e.target);}});}, {rootMargin:'0px 0px -8% 0px',threshold:.06}); [].forEach.call(document.querySelectorAll('.rv'),function(el,i){ el.style.setProperty('--d',(i%4*80)+'ms'); io.observe(el);}); } /* numeric counters - text metrics are left alone (no data-count) */ /* no count-up on trust figures: it dropped the thousands separator and showed a wrong number while running. The markup already holds the formatted value. */ /* sticky sub-nav scroll-spy */ var links=[].slice.call(document.querySelectorAll('.snav a')); var sio=new IntersectionObserver(function(es){es.forEach(function(e){ if(!e.isIntersecting) return; links.forEach(function(a){a.setAttribute('aria-current', a.getAttribute('href')==='#'+e.target.id?'true':'false');});});}, {rootMargin:'-30% 0px -60% 0px',threshold:0}); links.forEach(function(a){var t=document.getElementById(a.getAttribute('href').slice(1)); if(t) sio.observe(t);}); /* kinetic headline + gantt bars + line reveals */ var kio=new IntersectionObserver(function(es){es.forEach(function(e){ if(e.isIntersecting){e.target.classList.add('in');kio.unobserve(e.target);}});}, {rootMargin:'0px 0px -10% 0px',threshold:.18}); document.querySelectorAll('.kin,.reveal,.gr').forEach(function(el){kio.observe(el);}); /* drag-to-scroll rails + progress thumb */ document.querySelectorAll('.rail,.hstrip,.strip').forEach(function(r){ var down=false,sx=0,sl=0; r.addEventListener('pointerdown',function(e){down=true;sx=e.clientX;sl=r.scrollLeft; r.classList.add('drag');}); r.addEventListener('pointermove',function(e){if(!down)return;r.scrollLeft=sl-(e.clientX-sx);}); ['pointerup','pointerleave','pointercancel'].forEach(function(ev){ r.addEventListener(ev,function(){down=false;r.classList.remove('drag');});}); var thumb=r.parentElement&&r.parentElement.querySelector('.rthumb'), track=r.parentElement&&r.parentElement.querySelector('.rtrack'); if(thumb&&track){ var upd=function(){var max=r.scrollWidth-r.clientWidth,p=max>0?r.scrollLeft/max:0; thumb.style.transform='translateX('+(p*(track.clientWidth-thumb.clientWidth))+'px)';}; r.addEventListener('scroll',upd,{passive:true}); addEventListener('resize',upd); upd(); } }); /* custom cursor */ var cur=document.getElementById('cur'); if(cur && matchMedia('(hover:hover) and (pointer:fine)').matches && !reduce){ var cx=0,cy=0,tx=0,ty=0; addEventListener('mousemove',function(e){tx=e.clientX;ty=e.clientY;},{passive:true}); (function loop(){cx+=(tx-cx)*.16;cy+=(ty-cy)*.16; cur.style.transform='translate3d('+(cx-17)+'px,'+(cy-17)+'px,0)'; requestAnimationFrame(loop);})(); document.querySelectorAll('a,button,summary,.sdev,.hdevice,.rcd').forEach(function(el){ el.addEventListener('mouseenter',function(){cur.classList.add('on');}); el.addEventListener('mouseleave',function(){cur.classList.remove('on');});}); } /* process spine fill + node activation */ var sf=document.getElementById('sfill'), phs=[].slice.call(document.querySelectorAll('.pdeck .phase')), nds=[].slice.call(document.querySelectorAll('.snode')), nls=[].slice.call(document.querySelectorAll('.snl')); if(sf&&phs.length){ var deck=document.querySelector('.proc .pdeck'); var upd=function(){ var r=deck.getBoundingClientRect(),h=r.height-innerHeight*0.5; var p=Math.min(Math.max((innerHeight*0.5-r.top)/(h||1),0),1); sf.style.height=(p*100)+'%'; var act=Math.round(p*(nds.length-1)); nds.forEach(function(n,i){n.classList.toggle('on',i<=act);}); nls.forEach(function(n,i){n.classList.toggle('on',i<=act);}); }; addEventListener('scroll',upd,{passive:true}); addEventListener('resize',upd); upd(); } /* architecture tabs */ var tbs=[].slice.call(document.querySelectorAll('.tb')), pns=[].slice.call(document.querySelectorAll('.tpane')); tbs.forEach(function(t,i){t.addEventListener('click',function(){ tbs.forEach(function(x,j){x.setAttribute('aria-selected',i===j?'true':'false');}); pns.forEach(function(x,j){x.classList.toggle('on',i===j);});});}); /* product screen gallery */ var thumbs=[].slice.call(document.querySelectorAll('.thumb')), shots=[].slice.call(document.querySelectorAll('.shot')); if(thumbs.length&&shots.length){ var show=function(n){shots.forEach(function(x,i){x.classList.toggle('on',i===n);}); thumbs.forEach(function(t,i){t.setAttribute('aria-selected',i===n?'true':'false');});}; thumbs.forEach(function(t,i){ t.addEventListener('click',function(){show(i);}); t.addEventListener('keydown',function(ev){ if(ev.key==='ArrowRight'||ev.key==='ArrowDown'){ev.preventDefault(); var n=(i+1)%thumbs.length;thumbs[n].focus();show(n);} if(ev.key==='ArrowLeft'||ev.key==='ArrowUp'){ev.preventDefault(); var p=(i-1+thumbs.length)%thumbs.length;thumbs[p].focus();show(p);}});}); } })(); /* Everything pinned at the top of the viewport, measured rather than assumed. The theme header is position:fixed and its height is not constant (70px wide, 93px at 1280 where its own nav wraps). When an editor is logged in, the WordPress admin bar sits above it and the header is pushed down, so the top of the window is a STACK of fixed bars, not one. Probing only y=1 finds the topmost bar and nothing else - which pinned the section nav at 32px, directly behind the header, for every logged-in user while looking perfect logged out. So walk down the top edge until we run out of bars and take the deepest. A measurement of 0 means "not found yet" - the theme does not make its header fixed until the first scroll - and must never be written, or it would override the CSS default and pin the nav at the very top. */ (function(){ var scope = document.querySelector('.mcvcs,.mcvhub') || document.documentElement; var nav = document.querySelector('.snav'), last = -1; function measure(){ var h = 0, cx = Math.round(innerWidth / 2), maxY = Math.min(300, Math.round(innerHeight * 0.4)), y, i, e, c, b, found, stack; for (y = 1; y <= maxY; y += 4){ found = 0; stack = []; try { stack = document.elementsFromPoint(cx, y) || []; } catch (err) {} for (i = 0; i innerWidth * 0.6 && b.height > 12 && b.height < innerHeight * 0.4 && b.top = y){ found = 1; if (b.bottom > h) h = b.bottom; } } } if (!found && h) break; // past the bottom of the bar stack } h = Math.round(h); if (!h || h === last) return; last = h; scope.style.setProperty('--site-h', h + 'px'); var navH = nav ? Math.round(nav.getBoundingClientRect().height) : 0; document.documentElement.style.scrollPaddingTop = (h + navH + 14) + 'px'; } measure(); addEventListener('load', measure); var t; function later(){ clearTimeout(t); t = setTimeout(measure, 120); } addEventListener('scroll', later, {passive:true}); addEventListener('resize', function(){ last = -1; later(); }); })();