Adding Spanish translation for branding documentation

cache/701f9ca0fe8c144549990f999c36cfba25cfe46d.php

@@ -0,0 +1,10 @@
+<?php if(count($anchors) > 1): ?>
+    <ul class="pl-5">
+        <?php $__currentLoopData = $anchors; $__env->addLoop($__currentLoopData); foreach($__currentLoopData as $anchor): $__env->incrementLoopIndices(); $loop = $__env->getLastLoop(); ?>
+            <li class="anchor-<?php echo e($anchor['level']); ?>">
+                <a href="#<?php echo e($anchor['id']); ?>"><?php echo e($anchor['text']); ?></a>
+            </li>
+        <?php endforeach; $__env->popLoop(); $loop = $__env->getLastLoop(); ?>
+    </ul>
+    <hr>
+<?php endif; ?><?php /**PATH source/_layouts/anchors.blade.php ENDPATH**/ ?>

source/assets/build/mix-manifest.json

@@ -1,5 +1,4 @@
 {
-    "/js/app.js": "/js/app.js?id=30cd9bcc6259bd1c8ecf",
-    "/css/app.css": "/css/app.css?id=7a41c8164036b733705b",
-    "/js/app.js.map": "/js/app.js.map?id=c39569421d3d03ad1509"
+    "/js/app.js": "/js/app.js?id=b3cd2347d9cf9238800a",
+    "/css/app.css": "/css/app.css?id=a4df30e4eb02cf3f6dbc"
 }

source/en/docs/brand.md

@@ -20,8 +20,9 @@ To change the page header or footer, you must specify your own `blade` templates
 
 ## Change logo and name
 
-Create a new directory in the `brand` template section and the` header.blade.php` file.
-Then the full path will look like `/resources/views/brand/header.blade.php`.
+Create a new directory inside the `/resources/views` folder of your project, name it  `brand`, create a new blade file inside, and name it header.blade.php.
+Then the full path will look like: `/resources/views/brand/header.blade.php`.
+
 
 ```php
 resources          
@@ -34,6 +35,8 @@ resources
 Suppose that we are creating a system for a fictitious analytical agency, we will make changes to the file just created:
 
 ```php
+//resources/views/brand/header.blade.php.cd ..
+
 @push('head')
     <link
         href="/favicon.ico"
@@ -57,6 +60,8 @@ just as if passing an argument in the `view('brand.header')` helper:
 
 
 ```php
+//`config/platform.php`
+
 'template' => [
     'header' => 'brand.header',
     'footer' => null,
@@ -78,6 +83,8 @@ In the same way, we can change the bottom of the page, again create a new file `
 Also making changes to the configuration file:
 
 ```php
+//`config/platform.php`
+
 'template' => [
     'header' => 'brand.header',
     'footer' => 'brand.footer',

source/es/community/code-of-conduct.md

@@ -0,0 +1,52 @@
+---
+title: Community Guidelines
+description: Being involved in the Laravel Orchid community is an amazing experience
+extends: _layouts.documentation
+section: main
+lang: en
+---
+
+Being involved in the Laravel Orchid community is an amazing experience;
+you become part of something big, collaborate with people from all over the world,
+Help people make their computers amazing.
+But along with this there is an obligation to follow the rules,
+which provide the most comfortable environment for all participants.
+The following rules must be followed anytime, anywhere
+community related, be it Telegram, GitHub, an Laravel Orchid community resource, face-to-face chat, or something else.
+
+## Mutual respect
+
+Respect for others is paramount. Respect other people, their opinions, experience, personal life and ideas. The Laravel Orchid community is not a place for disrespectful or abusive language, regardless of the reason. Be constructive and respectful when criticizing. Personal attacks are not allowed. Constructive criticism should be perceived by you with prudence and respect, take note of it and thank the critic for his contribution, regardless of your position.
+
+## Content
+
+The Laravel Orchid community consists of thousands of users of different ages, creeds, as well as maturity levels. In this regard, you should be aware of the content that you create and the comments you leave. Adult materials, swearing, political or religious material, and any other inappropriate content should not appear in the context of Laravel Orchid. Ultimately, Laravel Orchid moderators have a decisive say in determining inappropriate content. If you doubt whether it is possible to write like that - imagine that you have an audience, including children and elderly people from around the world. And if you are still in doubt, then it is better to abstain.
+
+Screenshots distributed within Laravel Orchid communities should not contain themes that mimic other web systems, as well as photos and images pointing to certain individuals and any other content that violates our Code of Conduct in one way or another.
+
+## Rumors and speculation
+
+While the rapidly developing and exciting nature of Laravel Orchid fuels the desire to spread rumors or speculation, we ask you to refrain from this. The discussion of future plans is harmless in itself, but should not be presented as a confirmed fact - either make it clear that these are speculations, or do not discuss at all. Disseminating inaccurate information can be detrimental to the community, especially if information is disseminated in a negative way.
+
+## Substantive discussion
+
+Laravel Orchid is created by the joint efforts of many people in their free time, whose common goal is to create something special. It is important to always remember this and try to make your contribution to useful and meaningful discussions. At the meeting, support the topic of discussion and express your thoughts that are directly related to the subject of discussion. When commenting on a website, do not go far from the topic of the blog entry or the topic of the question. Taking part in discussions related to development, for example in mail correspondence or in Telegram, do not ask unnecessary questions and do not conduct conversations that are not directly related to the development process; thereby, you complicate the course of the discussion and overflow the logs of messages from developers that may not be in the conversation at that moment.
+
+First of all, you need to understand that we are an online community, on the basis of this we need to make every effort to avoid all the negative aspects that the global network has. No need to troll - verbal skirmishes and comments made for the sole purpose of making someone a fool are unacceptable and look at least infantile. Spam is also not allowed. Spam includes links to pages that are not related to the topic of discussion or repeated links to the same web page. If one of the users is engaged in trolling or spam, just ignore it and notify the moderators about it.
+
+## Avoiding Conflicts
+
+If you feel that someone, whether a beginner or an old-timer, is behaving rudely, politely inform him of this. Problems must be addressed before they become a disaster. Everyone must contribute so that communication in our unique (sometimes too unique) work environment runs smoothly.
+
+## Tactful retreat
+
+Life priorities, interests and hobbies can change. If you participate in an Laravel Orchid-related project, but feel that you must leave it, then make this the least problematic for the community. When we work together, the fruits of our work and ideas cease to be our own - they belong entirely to the Laravel Orchid community. Inform other team members that you are about to retire, and if possible, find someone who will continue your work. At the very least, make sure your work can continue when you leave.
+
+## Effects
+
+If you decide not to follow the above rules of behavior, or otherwise interfere with the community, we reserve the right to do the following: change or delete any content for you published; disable or block the account on third-party websites; disable account in Telegram; or in any other way to prevent your interaction with the community.
+
+----------
+
+_Laravel Orchid Code of Conduct distributed under license [Creative Commons Attribution-Share Alike 3.0](http://creativecommons.org/licenses/by-sa/3.0/). 
+Some points were inspired. [Ubuntu Code of Conduct](http://www.ubuntu.com/about/about-ubuntu/conduct)._

source/es/community/contributors.md

@@ -0,0 +1,112 @@
+---
+title: Contributors
+description: I urge everyone to contribute to the project.
+extends: _layouts.documentation
+section: main
+lang: en
+---
+
+
+[![Contributors](https://opencollective.com/orchid/contributors.svg?width=800&button=false)](https://github.com/orchidsoftware/platform)
+
+I urge everyone to contribute to the project. You can find the latest version of the code on GitHub at <https://github.com/orchidsoftware/platform>.
+
+## Problem tracking
+
+You can find unresolved issues on [GitHub Issues Tracker](https://github.com/orchidsoftware/platform/issues).
+ If you intend to work on a specific issue, leave a comment on the relevant task to inform other project participants.
+
+For active development, it is strongly recommended that you use only `pull request` requests, not just bug reports.
+
+If you created a bug report, then it should contain a title and a clear description of the problem. You should also include as complete information and sample code as possible to help reproduce the problem. The main goal of the bug report is to simplify the localization, reproduction of the problem and search for its solution.
+
+Also remember that error reports are created in the hope that other users with the same problems will be able to participate in solving them together with you. But do not expect others to quit and start fixing your problem. The bug report is designed to help you and others start working together to resolve a problem.
+
+## Participate in discussions
+
+You can offer new features and enhancements to your existing Laravel Orchid behavior. If you are proposing a new function, please be prepared to execute at least the code examples that will be needed to call / use this function.
+
+Informal discussion about bugs/problems and new features:
+
+ 1. [Telegram group @orchid_community](https://t.me/orchid_community)
+ 1. [Telegram group @orchid_russian_community](https://t.me/orchid_russian_community)
+
+## Security
+
+If you find a security vulnerability inside the platform, please send an e-mail message to `bliz48rus@gmail.com`.
+All appeals will be immediately considered.
+
+
+## Coding style
+
+Laravel Orchid follows [PSR-2](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide-meta.md) and [PSR-4](Https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-4-autoloader.md) standards.
+
+You can use [PHP-CS-Fixer](https://github.com/FriendsOfPHP/PHP-CS-Fixer) to fix your code style before publishing.
+
+To get started, install the tool on a global level and check the code style by executing the following command from the terminal of the root directory of your project:
+
+````bash
+php-cs-fixer fix
+````
+
+
+## Debug and submit change request
+
+
+At the stage of helping the project, questions may arise related to debugging and installation,
+This section is designed for those who want to send a request for the first time.
+
+### Development Installation
+
+To install the Laravel Orchid package as a developer, you must install the laravel framework.
+
+
+> First you have to make a fork [github repository](https://github.com/orchidsoftware/platform/fork) to post changes.
+
+
+Go to the directory and execute:
+
+```bash
+git clone https://github.com/yourname/platform.git
+```
+
+Add a local repository to the `composer.json` application:
+
+```php
+"repositories": [
+    {
+        "type": "path",
+        "url": "./platform"
+    }
+]
+```
+
+And add our package depending:
+
+```bash
+composer require orchid/platform:@dev
+```
+
+Composer adds the package from the repository that you specified.
+The remaining actions correspond to the section `Installations`.
+
+### Submit change request
+
+Create a new branch like this:
+
+```bash
+git checkout -b feature/issue_001
+```
+
+This will allow you to almost immediately understand that the created branch adds new functionality from the message number 001.
+
+Make changes and commit them:
+
+```bash
+git commit -am 'ref #001 [Docs] Fix misprint'
+```
+
+To send your branch you need to do:
+```bash
+git push origin feature/issue_001
+```

source/es/community/license.md

@@ -0,0 +1,29 @@
+---
+title: The MIT License (MIT)
+description: MIT License
+extends: _layouts.documentation
+section: main
+lang: en
+---
+
+## MIT License
+
+Copyright (c) Chernyaev Alexandr
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

source/es/community/promote.md

@@ -0,0 +1,59 @@
+---
+title: Promote
+description: There are many ways to contribute to the Laravel Orchid community
+extends: _layouts.documentation
+section: main
+lang: en
+---
+
+There are many ways to contribute to the Laravel Orchid community,
+lacking technical or programming skills that also contribute to promoting Laravel Orchid.
+
+## Web site
+
+Help on the website always appreciated.
+Of course, you will need a minimum knowledge of HTML, but no one needs you to have some cool know-how.
+You can clone the site from the git repository and submit the changes.
+
+## Use your graphics skills
+
+There are several ways you can use your graphic skills that can benefit the whole community.
+
+- Create new icon sets, add them to the appropriate repository and share them with the world.
+- If you think that you have an idea for a better design or even for the entire user interface - we are ready to experiment!
+
+## Help for other users
+
+Besides, creating a good development platform, it is also extremely important for us to create a strong community around it.
+  You can help us achieve this goal directly by helping other Laravel Orchid users.
+
+- **Create tutorials.** At all levels, new tutorials are welcome across the community;
+   from an Laravel Orchid novice to an advanced user and even to some development topics,
+   for example, how to create your own extensions.
+
+- **Participate in forums.** Ask questions, answer questions or solve problems of other Laravel Orchid users;
+  discuss issues and features; Share tips, tricks, and tricks 
+  participate in sweepstakes or contests; and meet new friends along the way.
+
+
+## Spread the word!
+
+First of all, keep in mind that we want to keep the community friendly, helpful, and polite; 
+therefore, please encourage good behavior through your own interactions with other people in the community.
+
+- **Write articles about Laravel Orchid** - publish articles in online magazines and blogs, or even in print.
+Do not forget to add the current link (or print URL)
+
+- **Create screenshots.** If you are aware of a new feature under development, consider creating one or more screenshots to illustrate this.
+
+- **Get more developers.** If you know or meet people with programming skills, introduce them to the community and ask if they might be interested in developing Laravel Orchid.
+
+## Sponsored the development 
+
+If you run a business and use the package in an income-generating product, it makes sense to finance the development: this ensures that the project on which your product relies remains healthy and actively supported. It can also help you understand the Laravel Orchid community and make it easier to get developers involved. If you are an individual user and use the product, consider donating in appreciation - for example, occasionally buying me coffee 😀
+
+## Backers
+
+Thank you to all our backers! 🙏 [[Become a backer](https://opencollective.com/orchid#backer)]
+
+<a href="https://opencollective.com/orchid#backers" target="_blank"><img src="https://opencollective.com/orchid/backers.svg?width=780"></a>