1<!doctype html> 2<html lang="en"> 3 <head> 4 <meta charset="utf-8"> 5 <meta name="viewport" content="width=device-width, initial-scale=1"> 6 <title>Use Cases - OmniStyler - Visual Web Styling, Experience Cloud Specialists</title> 7 <meta name="description" content="How people use OmniStyler: Experience Cloud portal owners, seasonal campaign themes, internal teams, freelancers, agencies and SI partners, marketing and landing pages, and developer handoff. The same visual loop works on any site you own."> 8 <link rel="canonical" href="https://omnistyler.com/use-cases/"> 9 <link rel="icon" type="image/png" sizes="64x64" href="/assets/favicon-64.png"> 10 <link rel="stylesheet" href="/guide/guide.css">
vendor: 104 bytes, lines 10-11
10 11 <script defer src="https://static.cloudflareinsights.com/beacon.min.js" data-cf-beacon='{"token": "
113e510a2eb2a54de4b3c7a00b39c5cfd9
vendor: 16 bytes, lines 11-12
11"}'></script> 12
12</head> 13 <body> 14 <div class="topbar"><div class="wrap"> 15 <nav class="nav"> 16 <a class="nav-brand" href="/"><img src="/assets/logo-192.png" alt="OmniStyler logo">OmniStyler</a> 17 <input type="checkbox" id="nav-toggle" class="nav-toggle" aria-hidden="true"> 18 <label for="nav-toggle" class="nav-burger" aria-label="Toggle menu"><span></span><span></span><span></span></label> 19 <div class="nav-links"> 20 <a href="/guide/">Styling guide</a> 21 <a href="/use-cases/" class="active">Use cases</a> 22 <a href="/manual/">Manual</a> 23 <a href="/pricing/">Pricing</a> 24 <a href="/evaluate/">Evaluate</a> 25 <a href="/app/" class="studio">Account</a> 26 <a class="launch" href="https://chromewebstore.google.com/detail/omnistyler/keopkdabbbbcidgbcoknekioohabodid" target="_blank" rel="noopener">Get the extension</a> 27 </div> 28 </nav> 29 </div></div> 30 31 <div class="wrap"> 32 <div class="layout"> 33 <aside class="side" aria-label="Website pages"> 34 <strong>OmniStyler</strong> 35 <a class="active" href="/use-cases/">Use cases</a> 36 <a href="/manual/">Manual</a> 37 <a href="/pricing/">Pricing</a> 38 <a href="/evaluate/">Evaluate</a> 39 <a href="/guide/">Styling guide</a> 40 </aside> 41 42 <main> 43 <article class="page"> 44 <p class="eyebrow">Use cases</p> 45 <h1>However you run your sites, the loop is the same</h1> 46 <p class="lede">Point at the live page, restyle it, ship one clean stylesheet. We perfected the loop on the hardest surface on the web, Salesforce Experience Cloud, so it holds up whether you run one landing page or a network of client portals. What changes between a solo admin and an agency with thirty client portals is everything around that loop: organization, review, history, and handoff. That's what the account layer is for.</p> 47 48 <div class="card-grid"> 49 <section class="info-card"> 50 <h3>Experience Cloud portal owner</h3> 51 <p>Restyle your live Experience Cloud portal yourself, copy the CSS, and test it in a sandbox the same afternoon, even through shadow DOM, FlexCards, and churned class names. Upgrade later if the portal becomes ongoing work that deserves sync, history, and a deploy kit.</p> 52 </section> 53 <section class="info-card"> 54 <h3>One site, many styles</h3> 55 <p>Holiday, event, dark-mode, campaign, and rebrand variants, all under the same portal or page. Approve one, archive the rest, and bring any of them back next season.</p> 56 </section> 57 <section class="info-card"> 58 <h3>Company with many portals</h3> 59 <p>Customer, partner, dealer, and support portals stay organized separately, while admins, designers, and developers share access to the themes that matter to them.</p> 60 </section> 61 <section class="info-card"> 62 <h3>Agency or SI partner</h3> 63 <p>A book of client portals and sites in one account: client workspaces, reusable base themes, review notes, and team roles, without unrelated customers ever mixing.</p> 64 </section> 65 <section class="info-card"> 66 <h3>Marketing and landing pages</h3> 67 <p>The same loop works on any site you own. Restyle a marketing site or landing page visually, watch the live match count so you never break something you cannot see, and hand developers clean CSS instead of screenshots. No Salesforce required.</p> 68 </section> 69 <section class="info-card"> 70 <h3>Freelancer or consultant</h3> 71 <p>Each client site stays cleanly separated. Duplicate a concept for a pitch, export a review preview the client can open in a browser, and hand off deploy-ready output.</p> 72 </section> 73 <section class="info-card"> 74 <h3>Developer handoff</h3> 75 <p>Stable selectors, a merge conflict report, head-ready CSS, and on Salesforce, a CLI deploy kit. The developer gets a project to run, not snippets to interpret.</p> 76 </section> 77 </div> 78 79 <h2>How the pieces fit together</h2> 80 <table class="ref"> 81 <tr><th>Piece</th><th>What it does for you</th><th>Who lives in it</th></tr> 82 <tr><td><strong>Extension</strong></td><td>Pick elements on any live site, style them visually, test selectors, and preview everything in place, from a marketing page to an Experience Cloud portal.</td><td>Designers, admins, developers.</td></tr> 83 <tr><td><strong>Account</strong></td><td>Named themes per site, brands, variants, review status, merge, version history, and the deploy kit, all in any browser with no install.</td><td>Teams, freelancers, agencies.</td></tr> 84 </table> 85 86 <h2>How client work stays organized</h2> 87 <pre><code>Workspace 88 Client or organization 89 Site or portal 90 Theme 91 Versions</code></pre> 92 <p>A one-company account stays flat and simple. Freelancers and agencies get a clean place to separate clients, so a dealer portal rebrand never sits next to an unrelated customer's landing page or support portal.</p> 93 94 <div class="page-nav"> 95 <a href="/">Back to homepage</a> 96 <a href="/manual/">Next: Manual</a> 97 </div> 98 </article> 99 </main> 100 </div> 101 102 <footer class="site">
103 <span><strong>OmniStyler</strong></span> 104 <span>Support: <a href="/cdn-cgi/l/email-protection#097a7c7979667b7d49666467607a7d70656c7b276a6664"><span class="__cf_email__" data-cfemail="bbc8cecbcbd4c9cffbd4d6d5d2c8cfc2d7dec995d8d4d6">[email protected]</span></a> · <a href="/privacy.html">Privacy</a></span> 105 </footer> 106 </div>
vendor: 111 bytes, lines 106-107
106 107 <script data-cfasync="false" src="/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js"></script>
107<script type="module" src="https://static.cloudflareinsights.com/beacon.min.js/v31edd6df95cf4e85bb4c19e7a9bdbcba1788362987495" integrity="sha512-iIg7k2xntmwu6/uSb5tpc/hySgZc4eoL31yB29W6tJFo2akwjPWcEqnCEdJvGexCL0KEQwVYv5BlowfhVz26hg==" data-cf-beacon='{"version":"2024.11.0","token":"90aa17fb70924cba933cf052576a0a8a","r":1,"spa":2}' crossorigin="anonymous"></script>
107 108</body> 109</html>
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.