Trademark & Brand-Use Policy

Effective date: 2025-01-01 Canonical domain: solidiom.org

This policy governs use of the Solidiom name, logos, and brand assets. “Solidiom” is a reserved brand name. While the Solidiom source code is open-source under the Apache 2.0 license, the brand identity is separately protected to prevent confusion about official project affiliation.

#Guiding Principles

1. Clarity of origin — users should always be able to distinguish official Solidiom materials from community or third-party works.
2. Community empowerment — we want the community to talk about, promote, and build upon Solidiom freely.
3. Brand integrity — the Solidiom name and logo should not be used in ways that imply false endorsement or mislead users.

#The Solidiom Brand Assets

The Solidiom brand includes:

• The name “Solidiom” (including capitalization and spelling).
• The Solidiom logo (all variants: wordmark, icon mark, and combined marks).
• The Solidiom color palette and visual identity as documented in official brand guidelines.
• The domain solidiom.org and associated official social media accounts.

#Permitted Uses (No Permission Required)

The following uses are allowed without prior written permission:

#Referring to Solidiom

• Using the name “Solidiom” in text to accurately refer to the project, its components, or its community (e.g., “Built with Solidiom,” “Compatible with Solidiom,” “A tutorial for Solidiom”).
• Writing blog posts, articles, tutorials, or documentation about Solidiom.
• Speaking about Solidiom at meetups, conferences, or in videos.
• Using the Solidiom name in academic or research contexts.

#Linking and Attribution

• Linking to solidiom.org or Solidiom’s official repositories.
• Including Solidiom in dependency lists, package metadata, or technology stack descriptions.
• Crediting Solidiom as a dependency or upstream project.

#Community Projects

• Creating community tools, plugins, adapters, or integrations that work with Solidiom, provided you follow the naming conventions below.
• Using the phrase “for Solidiom” or “with Solidiom” in your project name (e.g., “my-tool for Solidiom”).

#Social and Discussion

• Sharing links to Solidiom resources on social media.
• Discussing Solidiom in forums, chat rooms, or issue trackers.
• Creating community groups or channels focused on Solidiom (e.g., “Solidiom Users” Discord server), provided it is clear the group is community-run and not officially affiliated.

#Restricted Uses (Permission Required)

The following uses require prior written permission from the Solidiom maintainers:

#Implying Official Endorsement

• Using the Solidiom name or logo in a way that suggests your product, service, or organization is officially endorsed, sponsored, or affiliated with the Solidiom project.
• Stating or implying that the Solidiom maintainers recommend your product or service.

#Modified Logos

• Altering, distorting, recoloring, or combining the Solidiom logo with other graphics.
• Using portions of the Solidiom logo as part of another logo.
• Creating derivative marks that could be confused with the official Solidiom identity.

#Domain Names and Product Names

• Registering domain names that contain “solidiom” (e.g., solidiom-hosting.com, getsolidiom.io).
• Naming a product or service “Solidiom [something]” where it could be confused with an official offering (e.g., “Solidiom Pro,” “Solidiom Cloud,” “Solidiom Studio”).

#Commercial Use of Brand Assets

• Using the Solidiom logo on merchandise for sale.
• Including the Solidiom logo in paid advertising or promotional materials.
• Using Solidiom brand assets in a commercial product’s UI, marketing, or packaging.

#Misrepresentation

• Presenting a fork or substantially modified version of Solidiom as “Solidiom” without clear differentiation.
• Using the Solidiom name to sell support, consulting, or training without making clear that the service is not provided by the official project.

#Ecosystem Logo Criteria

Community projects that build adapters, integrations, or complementary tools for the Solidiom ecosystem may qualify to use an “ecosystem badge” or reference mark. This signals compatibility without implying official affiliation.

#Criteria for Ecosystem Logo Use

To qualify for ecosystem logo/badge usage, your project must:

1. Be functional — the project must actually integrate with or extend Solidiom in a meaningful way.
2. Be maintained — the project should be actively maintained and compatible with a current or recent Solidiom release.
3. Use clear naming — the project name must make clear it is a community/third-party project. Acceptable patterns:
   • [your-name]-solidiom (e.g., “acme-solidiom-adapter”)
   • solidiom-[category]-[your-name] (e.g., “solidiom-adapter-acme”)
   • [descriptive-name] for Solidiom (e.g., “Dark Theme for Solidiom”)
4. Include attribution — your project’s README or documentation must include a statement such as: “This is a community project and is not officially affiliated with or endorsed by Solidiom.”
5. Not mislead — the project must not use the official Solidiom logo as its own primary logo, and must not imply official status.
6. Respect the license — the project must comply with the Apache 2.0 license terms for any Solidiom code it uses.

#Ecosystem Badge Usage

If your project meets the criteria above:

• You may use the designated “Works with Solidiom” or “Solidiom Ecosystem” badge (when available) in your README, documentation, or website.
• The badge must link to solidiom.org.
• The badge must not be modified (no recoloring, resizing disproportionately, or adding effects).
• The badge must appear alongside a clear statement that your project is community-maintained.

#Revocation

The Solidiom maintainers reserve the right to request removal of ecosystem branding if a project:

• Becomes unmaintained and incompatible with current Solidiom releases.
• Misrepresents its relationship to the official project.
• Engages in practices harmful to the Solidiom community.

#Attribution Requirements

When referencing Solidiom in your project, the following attribution is appreciated:

#Minimal Attribution (Dependencies / Stack Lists)

Built with Solidiom (https://solidiom.org)

#Extended Attribution (Blog Posts / Tutorials / Talks)

Solidiom is an open-source component ecosystem for Solid.
Website: https://solidiom.org
License: Apache 2.0

#Code Attribution

When using Solidiom source code, follow the Apache 2.0 license requirements:

• Retain the original copyright notice and license text in any files you redistribute.
• State any changes you made to the original files.
• Include the NOTICE file if one exists in the original repository.

#Logo Usage Guidelines

When using the Solidiom logo with permission or in permitted contexts:

• Clear space — maintain adequate clear space around the logo (minimum equal to the height of the “S” in the wordmark).
• Minimum size — do not reproduce the logo smaller than 24px in height for digital use or 10mm for print.
• Backgrounds — use the appropriate logo variant for light and dark backgrounds. Do not place the logo on busy or low-contrast backgrounds.
• Do not — stretch, rotate, add effects (shadows, gradients, outlines), or animate the logo without permission.

#Forks and Derivatives

If you fork Solidiom:

• You must rename your fork to avoid confusion with the official project.
• You must remove or replace Solidiom logos and branding.
• You may state that your project is “based on Solidiom” or “forked from Solidiom” for attribution purposes.
• You must comply with the Apache 2.0 license requirements for the underlying code.

#Reporting Violations

If you believe someone is misusing the Solidiom brand, please report it by opening an issue on the Solidiom GitHub repository or contacting the maintainers through official channels.

#Permission Requests

To request permission for a use not covered by this policy, open an issue on our GitHub repository with:

• A description of the intended use.
• Where and how the brand assets will appear.
• The duration of the intended use.
• Your organization or project name and URL.

We aim to respond to permission requests within 14 business days.

#Changes to This Policy

We may update this policy to reflect changes in our brand strategy or community needs. Changes will be communicated through our usual project channels, and the commit history of this file serves as the official record of changes.