mirror of
https://github.com/tauri-apps/tauri-docs.git
synced 2026-01-31 00:35:16 +01:00
Add about pages, add navbar links (#1719)
* add trademark page * add governance page * add book * Add index page * Remove comment from footer * Remove rust page stub * Build References index page * Add nav menu * refactor sitetitle logic * add notes * Add index page * add redirect
This commit is contained in:
@@ -75,10 +75,10 @@ export default defineConfig({
|
||||
mastodon: 'https://fosstodon.org/@TauriApps',
|
||||
},
|
||||
components: {
|
||||
SiteTitle: 'src/components/overrides/SiteTitle.astro',
|
||||
Footer: 'src/components/overrides/Footer.astro',
|
||||
MarkdownContent: 'starlight-blog/overrides/MarkdownContent.astro',
|
||||
Sidebar: 'starlight-blog/overrides/Sidebar.astro',
|
||||
ThemeSelect: 'starlight-blog/overrides/ThemeSelect.astro',
|
||||
},
|
||||
head: [
|
||||
{
|
||||
@@ -227,7 +227,7 @@ export default defineConfig({
|
||||
'/blog/2023/06/14/tauri-1-4': '/blog/tauri-1-4',
|
||||
'/blog/2023/06/15/tauri-board-elections-and-governance-updates':
|
||||
'/blog/tauri-board-elections-and-governance-updates',
|
||||
//
|
||||
'about/intro': 'about/philosophy',
|
||||
// v1 /guides/development -> /guides/develop
|
||||
'/v1/guides/development/development-cycle': '/guides/develop/development-cycle',
|
||||
'/v1/guides/development/updating-dependencies': '/guides/develop/updating-dependencies',
|
||||
@@ -244,6 +244,5 @@ export default defineConfig({
|
||||
// i18n it
|
||||
'/it/v1/guides/development/development-cycle/': '/it/guides/develop/development-cycle/',
|
||||
'/it/v1/guides/development/updating-dependencies/': '/it/guides/develop/updating-dependencies/',
|
||||
//
|
||||
},
|
||||
});
|
||||
|
||||
143844
public/assets/brand_guidelines.pdf
Normal file
143844
public/assets/brand_guidelines.pdf
Normal file
File diff suppressed because one or more lines are too long
BIN
public/assets/logopack.zip
Normal file
BIN
public/assets/logopack.zip
Normal file
Binary file not shown.
78
src/assets/about/governance/diagram.svg
Normal file
78
src/assets/about/governance/diagram.svg
Normal file
File diff suppressed because one or more lines are too long
|
After Width: | Height: | Size: 256 KiB |
@@ -1,5 +1,4 @@
|
||||
---
|
||||
// src/components/EmailLink.astro
|
||||
import type { Props } from '@astrojs/starlight/props';
|
||||
import Default from '@astrojs/starlight/components/Footer.astro';
|
||||
const year = new Date().getFullYear();
|
||||
|
||||
146
src/components/overrides/SiteTitle.astro
Normal file
146
src/components/overrides/SiteTitle.astro
Normal file
@@ -0,0 +1,146 @@
|
||||
---
|
||||
// This is heavily adapted from Starlight components:
|
||||
// https://github.com/withastro/starlight/blob/main/packages/starlight/components/Select.astro
|
||||
// https://github.com/withastro/starlight/blob/main/packages/starlight/components/LanguageSelect.astro
|
||||
|
||||
import type { Props } from '@astrojs/starlight/props';
|
||||
import Default from '@astrojs/starlight/components/SiteTitle.astro';
|
||||
import { Icon } from '@astrojs/starlight/components';
|
||||
|
||||
type Link = {
|
||||
title: string;
|
||||
value: string;
|
||||
};
|
||||
|
||||
const links: Link[] = [
|
||||
{
|
||||
title: 'Guides',
|
||||
value: '/guides',
|
||||
},
|
||||
{
|
||||
title: 'References',
|
||||
value: '/2/reference',
|
||||
},
|
||||
{
|
||||
title: 'Blog',
|
||||
value: '/blog',
|
||||
},
|
||||
{
|
||||
title: 'About',
|
||||
value: '/about',
|
||||
},
|
||||
];
|
||||
---
|
||||
|
||||
<>
|
||||
<Default {...Astro.props}><slot /></Default>
|
||||
|
||||
<starlight-select class="mobile">
|
||||
<label>
|
||||
<select>
|
||||
<option value="" disabled selected>Menu</option>
|
||||
{links.map((link) => <option value={link.value} set:html={link.title} />)}
|
||||
</select>
|
||||
<Icon name="down-caret" class="icon caret" />
|
||||
</label>
|
||||
</starlight-select>
|
||||
|
||||
<div class="desktop">
|
||||
{links.map((link) => <a href={link.value}>{link.title}</a>)}
|
||||
</div>
|
||||
</>
|
||||
|
||||
<script>
|
||||
class StarlightLanguageSelect extends HTMLElement {
|
||||
constructor() {
|
||||
super();
|
||||
const select = this.querySelector('select');
|
||||
if (select) {
|
||||
select.addEventListener('change', (e) => {
|
||||
if (e.currentTarget instanceof HTMLSelectElement) {
|
||||
window.location.pathname = e.currentTarget.value;
|
||||
}
|
||||
});
|
||||
}
|
||||
}
|
||||
}
|
||||
customElements.define('starlight-select', StarlightLanguageSelect);
|
||||
</script>
|
||||
|
||||
<style>
|
||||
.desktop {
|
||||
display: none;
|
||||
align-items: center;
|
||||
gap: 1rem;
|
||||
padding-inline-start: 1rem;
|
||||
}
|
||||
@media (min-width: 72rem) {
|
||||
.desktop {
|
||||
display: flex;
|
||||
}
|
||||
.mobile {
|
||||
display: none;
|
||||
}
|
||||
}
|
||||
|
||||
a {
|
||||
color: var(--sl-color-white);
|
||||
font-weight: 600;
|
||||
text-decoration: none;
|
||||
}
|
||||
|
||||
/* From https://github.com/withastro/starlight/blob/main/packages/starlight/components/Select.astro */
|
||||
label {
|
||||
--sl-label-icon-size: 0.875rem;
|
||||
--sl-caret-size: 1.25rem;
|
||||
position: relative;
|
||||
display: flex;
|
||||
align-items: center;
|
||||
gap: 0.25rem;
|
||||
color: var(--sl-color-gray-1);
|
||||
}
|
||||
|
||||
label:hover {
|
||||
color: var(--sl-color-gray-2);
|
||||
}
|
||||
|
||||
.icon {
|
||||
position: absolute;
|
||||
top: 50%;
|
||||
transform: translateY(-50%);
|
||||
pointer-events: none;
|
||||
}
|
||||
|
||||
.label-icon {
|
||||
font-size: var(--sl-label-icon-size);
|
||||
inset-inline-start: 0;
|
||||
}
|
||||
|
||||
.caret {
|
||||
font-size: var(--sl-caret-size);
|
||||
inset-inline-end: 0;
|
||||
}
|
||||
|
||||
select {
|
||||
border: 0;
|
||||
padding-block: 0.625rem;
|
||||
padding-inline: calc(var(--sl-label-icon-size) + 0.25rem) calc(var(--sl-caret-size) + 0.25rem);
|
||||
width: var(--sl-select-width);
|
||||
background-color: transparent;
|
||||
text-overflow: ellipsis;
|
||||
color: inherit;
|
||||
cursor: pointer;
|
||||
appearance: none;
|
||||
}
|
||||
|
||||
option {
|
||||
background-color: var(--sl-color-bg-nav);
|
||||
color: var(--sl-color-gray-1);
|
||||
}
|
||||
|
||||
@media (min-width: 50rem) {
|
||||
select {
|
||||
font-size: var(--sl-text-sm);
|
||||
}
|
||||
}
|
||||
</style>
|
||||
18
src/content/docs/2/reference/index.mdx
Normal file
18
src/content/docs/2/reference/index.mdx
Normal file
@@ -0,0 +1,18 @@
|
||||
---
|
||||
title: References
|
||||
---
|
||||
|
||||
import { LinkCard, CardGrid } from '@astrojs/starlight/components'
|
||||
|
||||
<CardGrid>
|
||||
<LinkCard title="Tauri Configuration" href="/2/reference/config" />
|
||||
<LinkCard title="Command Line Interface (CLI)" href="/2/reference/cli" />
|
||||
<LinkCard title="JavaScript API" href="/2/reference/js" />
|
||||
<LinkCard title="Rust API (via Docs.rs)" href="https://docs.rs/tauri/~2.0.0-alpha" />
|
||||
</CardGrid>
|
||||
|
||||
:::caution[Tauri v1 References]
|
||||
|
||||
Links for Tauri v1 references coming soon.
|
||||
|
||||
:::
|
||||
@@ -1,3 +0,0 @@
|
||||
---
|
||||
title: Rust
|
||||
---
|
||||
31
src/content/docs/about/book.md
Normal file
31
src/content/docs/about/book.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
title: The Tauri Book
|
||||
---
|
||||
|
||||
:::note[Progress Update]
|
||||
|
||||
We're actively working on authoring and writing The Tauri Book. We've encountered delays due to the immense growth of Tauri but have recently re-prioritized this project. While we don't yet have details on the timelines of a release, you can keep an eye on this page for updates.
|
||||
|
||||
We'd like to apologize for this being delayed beyond the originally communicated publish date. If you've donated through GitHub Sponsors or Open Collective and would like to request a refund you may do so via Open Collective: [Contact Tauri on Open Collective](https://opencollective.com/tauri/contact).
|
||||
|
||||
:::
|
||||
|
||||
### Overview
|
||||
|
||||
The Tauri Book will guide you through the history of Tauri and the design decisions we've made. It will also talk in depth about why privacy, security and sustainability are important and fundamental discussions you can apply to any modern software project.
|
||||
|
||||
Topics included are:
|
||||
|
||||
- The method and reasoning behind the design of Tauri
|
||||
- The options you have when building with Tauri
|
||||
- That you don't have to choose between shipping fast and being sustainable and responsible
|
||||
- Why we chose the Rust language as a binding and application layer for Tauri
|
||||
- Why a binary review is important
|
||||
|
||||
### History
|
||||
|
||||
In 2020, the manufacture of native-apps has become easier and more accessible than ever before. All the same, beginners and seasoned developers alike are confronted with tough choices in a rapidly changing landscape of security and privacy. This is especially true in the semi-trusted environment of user devices.
|
||||
|
||||
Tauri takes the guesswork out of the equation, as it was designed from the ground up to embrace new paradigms of secure development and creative flexibility that leverage the language features of Rust and lets you build an app using any frontend framework you like. Find out how you can design, build, audit and deploy tiny, fast, robust, and secure native applications for the major desktop and mobile platforms, all from the exact same codebase and in record time - without even needing to know the Rust programming language.
|
||||
|
||||
Authors and Tauri co-founders Daniel and Lucas take you on a journey from theory to execution, during which you will learn why Tauri was built and how it works under the hood. Together with guest insights that specialize in Open Source, DevOps, Security and Enterprise Architecture, this book also presents discourse-formatted philosophical discussions and open-source sustainability viewpoints from which your next-gen apps will profit - and your users will benefit.
|
||||
49
src/content/docs/about/governance.md
Normal file
49
src/content/docs/about/governance.md
Normal file
@@ -0,0 +1,49 @@
|
||||
---
|
||||
title: Tauri Governance
|
||||
---
|
||||
|
||||
One of the main goals of the organizational structure of Tauri is to guarantee we stay true to our open source values and do so sustainably while respecting the health and well-being of contributors. [The Tauri Programme within the Commons Conservancy](https://dracc.commonsconservancy.org/0035/) was established to commit to those values, and facilitate an open, transparent and efficient governance process throughout the future development of the Tauri and its auxiliary materials.
|
||||
|
||||
## Tauri Working Group
|
||||
|
||||
The Tauri Working Group is the collective framework created to enable this governance process. It's composed of the following components:
|
||||
|
||||
- Working Group Members
|
||||
- Tauri Board & Board Directors
|
||||
- Domains & Domain Leads
|
||||
- Teams
|
||||
|
||||

|
||||
|
||||
### Working Group Members
|
||||
|
||||
All of the individuals that make up the Tauri Working Group.
|
||||
|
||||
### Tauri Board & Board Directors
|
||||
|
||||
The Tauri Board is the central decision making body for the Tauri Programme and is responsible for the overall health and stability of the Tauri Programme. The Board votes on major decisions within the Programme and issues raised by the Working Group.
|
||||
|
||||
An individual Board Director may be a technical contributor, be a stakeholder in Tauri's future, share experience from the industry, or have a passion for regulatory and legal aspects within Open Source.
|
||||
|
||||
### Domains & Domain Leads
|
||||
|
||||
Domains are organizational units that represent an area of interest within Tauri.
|
||||
|
||||
Domain Leads are trusted contributors within the Tauri community with expertise in the Domain they are leading. They are responsible for setting direction, overseeing and supporting the activities within that Domain.
|
||||
|
||||
The current Domains and Domain leads are outlined in the [Governance and Guidance repo on GitHub](https://github.com/tauri-apps/governance-and-guidance).
|
||||
|
||||
### Teams
|
||||
|
||||
Teams are small groups of contributors that support or maintain specific areas of the Tauri Programme. They are a means for Tauri to execute its longer-term tasks and goals, especially when ad-hoc contributions cannot achieve the same results.
|
||||
|
||||
## Get Involved
|
||||
|
||||
If you're interested in becoming a Tauri Board Director or a Domain Lead, elections for those positions are run throughout the year. For Domain Leads those take place in both the spring and fall and for Board Directors in the summer. Instructions for how to apply are posted to the [Tauri Blog](https://tauri.app/blog) leading up to the respective election.
|
||||
|
||||
## Additional Resources
|
||||
|
||||
- [Governance and Guidance Repository](https://github.com/tauri-apps/governance-and-guidance): More detailed information about Tauri's Governance and the current Domains and Domain Leads
|
||||
- [Social Contract](https://github.com/tauri-apps/governance-and-guidance/blob/main/SOCIAL_CONTRACT.md): The social contract informs our decision making and organization
|
||||
- [Code of Conduct](https://github.com/tauri-apps/governance-and-guidance/blob/main/CODE_OF_CONDUCT.md)
|
||||
- [Tauri Programme Statutes](https://dracc.commonsconservancy.org/0035/)
|
||||
25
src/content/docs/about/index.mdx
Normal file
25
src/content/docs/about/index.mdx
Normal file
@@ -0,0 +1,25 @@
|
||||
---
|
||||
title: About Tauri
|
||||
---
|
||||
|
||||
:::tip
|
||||
|
||||
If you're looking for a quick technical overview and to start building an app then visit the [What is Tauri page](/guides). If you'd like to learn more about the project's philosophy then keep reading.
|
||||
|
||||
:::
|
||||
|
||||
import { LinkCard, CardGrid } from '@astrojs/starlight/components';
|
||||
|
||||
<CardGrid>
|
||||
<LinkCard
|
||||
title="Tauri Philosophy"
|
||||
href="/about/philosophy"
|
||||
description="Learn more about the approach behind Tauri"
|
||||
/>
|
||||
<LinkCard
|
||||
title="Governance"
|
||||
href="/about/governance"
|
||||
description="Understand how the Tauri governance structure is setup"
|
||||
/>
|
||||
<LinkCard title="Trademark" href="/about/trademark" description="Guidelines for using the Tauri trademark" />
|
||||
</CardGrid>
|
||||
46
src/content/docs/about/philosophy.md
Normal file
46
src/content/docs/about/philosophy.md
Normal file
@@ -0,0 +1,46 @@
|
||||
---
|
||||
title: Tauri Philosophy
|
||||
---
|
||||
|
||||
Tauri is a toolkit that helps developers make applications for the major desktop platforms - using virtually any frontend framework in existence. The core is built with Rust, and the CLI leverages Node.js making Tauri a genuinely polyglot approach to creating and maintaining great apps.
|
||||
|
||||
<iframe
|
||||
style="width: 100%; aspect-ratio: 16/9;"
|
||||
src="https://www.youtube-nocookie.com/embed/UxTJeEbZX-0?si=mwQUzXb6mmCg7aom"
|
||||
title="YouTube video player"
|
||||
frameborder="0"
|
||||
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
|
||||
allowfullscreen
|
||||
></iframe>
|
||||
|
||||
## Security First
|
||||
|
||||
In today's world, every honest threat model assumes that the user's device has already been compromised. This puts app developers in a complicated situation because if the device is already at risk, how can the software be trusted?
|
||||
|
||||
Defense in depth is the approach we've taken. We want you to be able to take every precaution possible to minimize the surface area you present to attackers. Tauri lets you choose which API endpoints to ship, whether or not you want a localhost server built into your app, and it even randomizes functional handles at runtime. These and other techniques form a secure baseline that empowers you and your users.
|
||||
|
||||
Slowing down attackers by making static attacks crushingly difficult and isolating systems from one another is the name of the game. And if you are coming from the Electron ecosystem - rest assured - by default Tauri only ships binaries, not ASAR files.
|
||||
|
||||
By choosing to build Tauri with security as a guiding force, we give you every opportunity to take a proactive security posture.
|
||||
|
||||
## Polyglots, not Silos
|
||||
|
||||
Most contemporary frameworks use a single language paradigm and are therefore trapped in a bubble of knowledge and idiom. This can work well for certain niche applications, but it also fosters a kind of tribalism.
|
||||
|
||||
This can be seen in the way that the React, Angular, and Vue development communities huddle on their stacks, ultimately breeding very little cross-pollination.
|
||||
|
||||
This same situation can be seen in the Rust vs. Node vs. C++ battlefields, where hardliners take their stances and refuse to collaborate across communities.
|
||||
|
||||
Today, Tauri uses Rust for the backend - but in the not too distant future, other backends like Go, Nim, Python, Csharp, etc. will be possible. This is because we are maintaining the official Rust bindings to the [webview](https://github.com/webview) organization and plan to let you switch out the backend for your needs. Since our API can be implemented in any language with C interop, full compliance is only a PR away.
|
||||
|
||||
## Honest Open Source
|
||||
|
||||
None of this would make any sense without a community. Today software communities are amazing places where people help each other and make awesome things - open source is a very big part of that.
|
||||
|
||||
Open source means different things to different people, but most will agree that it serves to support freedom. When software doesn't respect your rights, then it can seem unfair and potentially compromise your freedoms by operating in unethical ways.
|
||||
|
||||
This is why we are proud that FLOSS advocates can build applications with Tauri that are "certifiably" open source and can be included in FSF endorsed GNU/Linux distributions.
|
||||
|
||||
## The Future
|
||||
|
||||
Tauri's future depends on your involvement and contributions. Try it out, file issues, join a working group or make a donation - every contribution is important. Please, at any rate, do get in touch!!!
|
||||
117
src/content/docs/about/trademark.md
Normal file
117
src/content/docs/about/trademark.md
Normal file
@@ -0,0 +1,117 @@
|
||||
---
|
||||
title: Trademark Guidelines
|
||||
---
|
||||
|
||||
This trademark policy was prepared to help you understand how to use the TAURI trademarks, service marks and logos owned by the Tauri Programme within the Commons Conservancy.
|
||||
|
||||
While our software is available under a free and open source software license, that copyright license does not include a license to use our trademark, and this Policy is intended to explain how to use our marks consistent with background law and community expectation.
|
||||
|
||||
**This Policy covers:**
|
||||
|
||||
- Our word trademarks and service marks: TAURI, TAO, WRY
|
||||
- Our logos: The TAURI, TAO, WRY logos (and all visual derivatives)
|
||||
|
||||
This policy encompasses all trademarks and service marks, whether they are registered or not.
|
||||
|
||||
## General Guidelines
|
||||
|
||||
Whenever you use one of our marks, you must always do so in a way that does not mislead anyone about what they are getting and from whom. For example, you cannot say you are distributing TAURI software when you’re distributing a modified version of it (aka a Fork), because recipients may not understand the differences between your modified versions and our own.
|
||||
|
||||
You also cannot use our logo on your website in a way that suggests that your website is an official website or that we endorse your website.
|
||||
|
||||
You can, though, say you like TAURI software, that you participate in the TAURI community, that you are providing an unmodified version of the TAURI software.
|
||||
|
||||
You may not use or register our marks, or variations of them as part of your own trademark, service mark, domain name, company name, trade name, product name or service name.
|
||||
|
||||
Trademark law does not allow your use of names or trademarks that are too similar to ours. You therefore may not use an obvious variation of any of our marks or any phonetic equivalent, foreign language equivalent, takeoff, or abbreviation for a similar or compatible product or service. We would consider the following too similar to one of our Marks:
|
||||
|
||||
- TAURIMAGE
|
||||
- Tauri Wallet App
|
||||
|
||||
## Acceptable Uses
|
||||
|
||||
### Applications
|
||||
|
||||
TAURI is a framework for making applications for computing devices. You may claim that your application uses TAURI, but care should be taken to avoid giving the impression that your application is approved by The Tauri Programme within the Commons Conservancy, or is an official application. Care must be taken, not to ship your application with the default ICON.
|
||||
|
||||
### Plugins & Templates
|
||||
|
||||
You may publish the code for plugins and templates using the appropriate naming conventions, but please mention that these works are not officially approved. Only such codebases that are managed by the organization within the GitHub organization `tauri-apps` are considered official.
|
||||
|
||||
## Core Modifications (Forks)
|
||||
|
||||
If you distribute a modified version of our software (TAURI CORE), you must remove all of our logos and naming from it. You must retain our original license in SPDX format. You may use our word marks, but not our logos, to truthfully describe the origin of the software that you are providing. For example, if the code you are distributing is a modification of our software, you may say, “This software is derived from the source code for TAURI software.”
|
||||
|
||||
### Statements About Compatibility
|
||||
|
||||
You may use the word marks, but not the logos, to truthfully describe the relationship between your software and ours. Any other use may imply that we have certified or approved your software. If you wish to use our logos, please contact us to discuss license terms.
|
||||
|
||||
### Naming Compatible Products
|
||||
|
||||
If you wish to describe your product with reference to the TAURI software, here are the conditions under which you may do so. You may call your software XYZ (where XYZ is your product name) for TAURI only if:
|
||||
|
||||
- All versions of the TAURI software you deliver with your product are the exact binaries provided by us, or manufactured by the core software and tooling we provide.
|
||||
- Your product is fully compatible with the APIs for the TAURI software.
|
||||
- You use the following legend in marketing materials or product descriptions: “TAURI is a trademark of The Tauri Programme within the Commons Conservancy. https://tauri.app/ ”
|
||||
|
||||
### User Groups
|
||||
|
||||
You can use the Word Marks as part of your user group name provided that:
|
||||
|
||||
- The main focus of the group is our software
|
||||
- The group does not make a profit
|
||||
- Any charge to attend meetings are to cover the cost of the venue, food and drink only
|
||||
|
||||
You are not authorized to conduct a conference using our marks.
|
||||
|
||||
### No Domain Names
|
||||
|
||||
You must not register any domain that includes our word marks or any variant or combination of them.
|
||||
|
||||
### Other For Profit Usage of the TAURI Marks
|
||||
|
||||
If you are making a video, tutorial series, book, or other educational material, for which you are receiving payment through subscriptions, sales, advertising or the like, then you must acquire explicit licensing permission from The Tauri Programme within the Commons Conservancy.
|
||||
|
||||
## How to Display Our Marks
|
||||
|
||||
When you have the right to use our mark, here is how to display it.
|
||||
|
||||
### Trademark Marking and Legends
|
||||
|
||||
The first or most prominent mention of a mark on a webpage, document, or documentation should be accompanied by a symbol indicating whether the mark is a registered trademark (“®”) or an unregistered trademark (“™”). If you don’t know which applies, contact us. (TAURI itself is a registered trademark.)
|
||||
|
||||
Place the following notice at the foot of the page where you have used the mark: TAURI is trademark of [The Tauri Programme within the Commons Conservancy].”
|
||||
|
||||
### Use of Trademarks in Text
|
||||
|
||||
Always use trademarks in their exact form with the correct spelling, neither abbreviated, hyphenated, or combined with any other word or words.
|
||||
|
||||
- Unacceptable: TAUREE
|
||||
- Acceptable: TAURI
|
||||
|
||||
Don’t pluralize a trademark.
|
||||
|
||||
- Unacceptable: I have seventeen TAURIs running on my computer.
|
||||
- Acceptable: I am running seventeen TAURI applications on my computer and have ram to spare.
|
||||
|
||||
Always use a trademark as an adjective modifying a noun.
|
||||
|
||||
- Unacceptable: This is a TAURI.
|
||||
- Acceptable: This is a TAURI software application.
|
||||
|
||||
### Use of Logos
|
||||
|
||||
You may not change any logo except to scale it. This means you may not add decorative elements, change the colors, change the proportions, distort it, add elements, or combine it with other logos.
|
||||
|
||||
We have a high-contrast version of the logo, which you can download below in the assets section.
|
||||
|
||||
## Assets
|
||||
|
||||
- Here you may download the entire [Brand Guidelines](/assets/brand_guidelines.pdf) - (PDF, 74.3 MB)
|
||||
- Here you may download SVG and PNG formats of the LOGO and Wordmark in the [Logopack](/assets/logopack.zip) - (ZIP, 203 KB)
|
||||
|
||||
---
|
||||
|
||||
The Tauri Programme within the Commons Conservancy retains all rights to the modification of these trademark guidelines at any time. If you have a question or enquiry, please send an email to `trademark@tauri.app`.
|
||||
|
||||
These guidelines are based on the Model Trademark Guidelines, available at http://www.modeltrademarkguidelines.org, used under a Creative Commons Attribution 3.0 Unported license: https://creativecommons.org/licenses/by/3.0/deed.en_EU. Version 1.0 dated 20th, August 2022
|
||||
Reference in New Issue
Block a user