|
| 1 | +# Branding & Attribution Guidelines |
| 2 | + |
| 3 | +These guidelines explain how to present **AspectReact** when you build, deploy, or talk about projects based on this codebase. They’re written to be practical for day‑to‑day use by developers, agencies, and integrators. |
| 4 | + |
| 5 | +> Short version: please credit the project clearly and avoid branding your distribution as “AspectReact” in a way that could confuse people about where it came from. |
| 6 | +
|
| 7 | +--- |
| 8 | + |
| 9 | +## 1) Names & how to refer to the project |
| 10 | + |
| 11 | +- **Project name:** **AspectReact** |
| 12 | +- **Repository name:** **AspectReact Store** (this particular demo implementation) |
| 13 | + |
| 14 | +Use **“AspectReact”** when you refer to the underlying framework/template. If you ship a tailored product to clients, give it **your own brand name**, and acknowledge that it’s built with AspectReact (see §3). |
| 15 | + |
| 16 | +**Please avoid** naming your product simply “AspectReact” or something that could be mistaken for the original project. |
| 17 | + |
| 18 | +--- |
| 19 | + |
| 20 | +## 2) Recommended credits (gentle, familiar pattern) |
| 21 | + |
| 22 | +Consistent credit helps users and other developers find the source project and updates. A familiar, unobtrusive pattern is a small footer line: |
| 23 | + |
| 24 | +```html |
| 25 | +<a href="https://github.com/dmsfiris/aspectreact-store" rel="noreferrer" target="_blank"> |
| 26 | + Built with AspectReact |
| 27 | +</a> |
| 28 | +``` |
| 29 | + |
| 30 | +If you prefer a badge, here’s a tiny **SVG** you can drop in as-is: |
| 31 | + |
| 32 | +```html |
| 33 | +<a href="https://github.com/dmsfiris/aspectreact-store" target="_blank" rel="noreferrer" aria-label="Built with AspectReact"> |
| 34 | + <svg xmlns="http://www.w3.org/2000/svg" width="156" height="24" viewBox="0 0 156 24" role="img"> |
| 35 | + <rect width="156" height="24" rx="4" fill="#111827"/> |
| 36 | + <text x="12" y="16" font-family="system-ui, -apple-system, Segoe UI, Roboto, Helvetica, Arial, sans-serif" |
| 37 | + font-size="12" fill="#F9FAFB">Built with AspectReact</text> |
| 38 | + </svg> |
| 39 | +</a> |
| 40 | +``` |
| 41 | + |
| 42 | +Or a simple **text link** with minimal Tailwind styling: |
| 43 | + |
| 44 | +```html |
| 45 | +<a class="text-neutral-600 hover:text-ink transition-colors" |
| 46 | + href="https://github.com/dmsfiris/aspectreact-store" target="_blank" rel="noreferrer"> |
| 47 | + Built with AspectReact |
| 48 | +</a> |
| 49 | +``` |
| 50 | + |
| 51 | +**SPA meta generator (optional):** add a meta tag so analytics and audits can detect the stack: |
| 52 | + |
| 53 | +```html |
| 54 | +<meta name="generator" content="AspectReact" /> |
| 55 | +``` |
| 56 | + |
| 57 | +--- |
| 58 | + |
| 59 | +## 3) Where to place the credit |
| 60 | + |
| 61 | +Choose one or more locations appropriate for your project: |
| 62 | + |
| 63 | +- **Site footer** (recommended): “Built with AspectReact” |
| 64 | +- **About / Credits** page: short sentence like _“This site is built with AspectReact.”_ |
| 65 | +- **Repository docs:** mention in `README` and/or `CHANGELOG` |
| 66 | +- **Marketing materials / case studies:** “Powered by AspectReact” works well |
| 67 | + |
| 68 | +If visual constraints prevent a footer line, keep a mention in your **/about** page and/or repository README. |
| 69 | + |
| 70 | +--- |
| 71 | + |
| 72 | +## 4) Using the name alongside your brand |
| 73 | + |
| 74 | +Suggested formats when you ship to clients: |
| 75 | + |
| 76 | +- **YourBrand**, _built with AspectReact_ |
| 77 | +- **YourBrand for AspectReact** (if you publish a theme or extension) |
| 78 | +- **YourBrand — based on AspectReact** |
| 79 | + |
| 80 | +Avoid implying official partnership or endorsement. If you contribute upstream or maintain an official integration, feel free to say so in your docs, linking to the relevant pull requests or repositories. |
| 81 | + |
| 82 | +--- |
| 83 | + |
| 84 | +## 5) Sample snippets for this repo |
| 85 | + |
| 86 | +This repository already includes an env toggle for a footer credit. If you use the provided config, you can show the credit like this: |
| 87 | + |
| 88 | +```jsx |
| 89 | +// Footer.jsx (excerpt) |
| 90 | +{SHOW_POWERED_BY && ( |
| 91 | + <a |
| 92 | + href="https://github.com/dmsfiris/aspectreact-store" |
| 93 | + target="_blank" |
| 94 | + rel="noreferrer" |
| 95 | + className="transition-colors text-neutral-600 hover:text-ink" |
| 96 | + > |
| 97 | + {POWERED_BY_TEXT /* default: "Built with AspectReact" */} |
| 98 | + </a> |
| 99 | +)} |
| 100 | +``` |
| 101 | + |
| 102 | +And in your environment config: |
| 103 | + |
| 104 | +```env |
| 105 | +REACT_APP_SHOW_POWERED_BY=true |
| 106 | +REACT_APP_POWERED_BY_TEXT="Built with AspectReact" |
| 107 | +``` |
| 108 | + |
| 109 | +--- |
| 110 | + |
| 111 | +## 6) Logos & visual identity |
| 112 | + |
| 113 | +There’s no official logo package yet. Until one exists, use plain text **AspectReact** with your standard body font. If you design a logo or badge for your deployment, please present it as your own brand element and use the text credit formats above to reference the project. |
| 114 | + |
| 115 | +--- |
| 116 | + |
| 117 | +## 7) What’s allowed / encouraged |
| 118 | + |
| 119 | +- Build commercial or non‑commercial projects on top of AspectReact. |
| 120 | +- Rebrand your shipped solution with your own product name. |
| 121 | +- Credit AspectReact prominently so users and developers can find the source. |
| 122 | +- Publish articles, tutorials, or showcases referencing AspectReact—link back to the repo. |
| 123 | + |
| 124 | +## 8) What to avoid |
| 125 | + |
| 126 | +- Branding your product **as if it were** the original “AspectReact”. |
| 127 | +- Suggesting official affiliation or endorsement where none exists. |
| 128 | +- Removing all mention of AspectReact in contexts where a short credit fits naturally (footer, about, README). |
| 129 | + |
| 130 | +--- |
| 131 | + |
| 132 | +## 9) License notes (very short) |
| 133 | + |
| 134 | +The code is licensed **GPL‑3.0‑or‑later**. When you redistribute the software (in source or compiled form), keep the license text and copyright notices, and provide the corresponding source to your recipients as required by the GPL. See `LICENSE` for the full terms. |
| 135 | + |
| 136 | +For questions about branding or licensing in specific situations, involve your organization’s legal or compliance team. |
| 137 | + |
| 138 | +--- |
| 139 | + |
| 140 | +## 10) Contact |
| 141 | + |
| 142 | +Project repo: <https://github.com/dmsfiris/aspectreact-store> |
| 143 | +Maintainer contact: **dmsfiris@otenet.gr** |
0 commit comments