添加项目文件
This commit is contained in:
PhatenIoT-yan
2025-04-29 16:11:32 +08:00
parent 5412e97d37
commit 8d10d3da3f
978 changed files with 54843 additions and 0 deletions

120
zh/.circleci/config.yml Normal file
View File

@@ -0,0 +1,120 @@
version: 2.1
jobs:
#
# Build & Deploy
#
build-and-deploy:
machine:
image: ubuntu-2204:2022.04.1
docker_layer_caching: false
steps:
- checkout
- run:
name: Context Info Cmds
command: pwd && ls -ltra && git branch
- run:
name: Initialize Repo Makefiles
command: |
make init-makefiles
- run:
name: Deploy GitHub Pages Site w/ MkDocs
command: GOOGLE_ANALYTICS_KEY=$GOOGLE_ANALYTICS_KEY_LEVERAGE_G4 make docs-deploy-gh
- slack/notify:
event: fail
mentions: '@leverage-support'
custom: |
{
"blocks": [
{
"type": "header",
"text": {
"type": "plain_text",
"text": "Failed Pipeline! :rotating_light::fire::bash-fire::bangbang::video-games-doom-mad::stopp:",
"emoji": true
}
},
{
"type": "section",
"text": {
"type": "mrkdwn",
"text": ":negative_squared_cross_mark: *Project*: $CIRCLE_PROJECT_REPONAME \n :negative_squared_cross_mark: *User*: $CIRCLE_USERNAME \n :negative_squared_cross_mark: *Job*: $CIRCLE_JOB in *repo* $CIRCLE_PROJECT_REPONAME \n :negative_squared_cross_mark: *Branch:* $CIRCLE_BRANCH \n :negative_squared_cross_mark: *PR:* $CIRCLE_PULL_REQUEST \n :negative_squared_cross_mark: *Last Commit:* $CIRCLE_SHA1"
},
"accessory": {
"type": "button",
"text": {
"type": "plain_text",
"text": ":arrow_forward: View Job in CircleCi",
"emoji": true
},
"value": "click_me_123",
"url": "$CIRCLE_BUILD_URL",
"action_id": "button-action"
}
}
]
}
channel: 'tools-ci'
- slack/notify:
event: pass
custom: |
{
"blocks": [
{
"type": "header",
"text": {
"type": "plain_text",
"text": "Successful Pipeline! :checkered_flag: :video-games-star: :video-games-mario-luigi-dance: :tada: :binbash::bb-leverage: :heart: :open-source:",
"emoji": true
}
},
{
"type": "section",
"text": {
"type": "mrkdwn",
"text": ":heavy_check_mark: *Project*: $CIRCLE_PROJECT_REPONAME \n :heavy_check_mark: *User*: $CIRCLE_USERNAME \n :heavy_check_mark: *Job*: $CIRCLE_JOB in *repo* $CIRCLE_PROJECT_REPONAME \n :heavy_check_mark: *Branch:* $CIRCLE_BRANCH \n :heavy_check_mark: *PR:* $CIRCLE_PULL_REQUEST \n :heavy_check_mark: *Last Commit:* $CIRCLE_SHA1"
},
"accessory": {
"type": "button",
"text": {
"type": "plain_text",
"text": ":arrow_forward: View Job in CircleCi",
"emoji": true
},
"value": "click_me_123",
"url": "$CIRCLE_BUILD_URL",
"action_id": "button-action"
}
}
]
}
channel: 'tools-ci'
#
# CircleCI orbs are open-source, shareable packages of parameterizable reusable
# configuration elements, including jobs, commands, and executors.
#
orbs:
# sumologic: circleci/sumologic@1.0.6
slack: circleci/slack@4.1.1
#
# Jobs workflow
#
workflows:
version: 2
test_and_release:
jobs:
- build-and-deploy:
context: binbashar-org-global-context
filters:
branches:
only: # only branches matching the below regex filters will run
- master
# - sumologic/workflow-collector:
# context: binbashar-org-global-context

5
zh/.github/CODEOWNERS vendored Normal file
View File

@@ -0,0 +1,5 @@
# Use this file to define individuals or teams that are responsible for code in a repository.
# Read more: <https://help.github.com/articles/about-codeowners/>
* @binbashar/leverage-ref-architecture-aws-admin
* @binbashar/leverage-ref-architecture-aws-dev

3
zh/.github/FUNDING.yml vendored Normal file
View File

@@ -0,0 +1,3 @@
# These are supported funding model platforms
github: binbashar

33
zh/.github/ISSUE_TEMPLATE/bug_report.md vendored Normal file
View File

@@ -0,0 +1,33 @@
---
name: Bug report
about: Create a report to help us improve
title: ''
labels: 'bug'
assignees: ''
---
## Describe the Bug
A clear and concise description of what the bug is.
## Expected Behavior
A clear and concise description of what you expected to happen.
## Steps to Reproduce
Steps to reproduce the behavior:
1. Go to '...'
2. Run '....'
3. Enter '....'
4. See error
## Screenshots
If applicable, add screenshots or logs to help explain your problem.
## Environment (please complete the following information):
Anything that will help us triage the bug will help. Here are some ideas:
- OS: [e.g. Linux, OSX, WSL, etc]
- Version [e.g. 10.15]
## Additional Context
Add any other context about the problem here.

8
zh/.github/ISSUE_TEMPLATE/config.yml vendored Normal file
View File

@@ -0,0 +1,8 @@
blank_issues_enabled: false
contact_links:
- name: DevOps Cloud Services Program
url: https://www.binbash.com.ar
about: |-
At binbash Leverage, our focus is on creating reusable, high quality infrastructure code, such as our Reference Architecture for AWS backed by our DevOps Automation Code Library.

View File

@@ -0,0 +1,32 @@
---
name: Feature Request
about: Suggest an idea for this project
title: ''
labels: 'feature request'
assignees: ''
---
## Describe the Feature
A clear and concise description of what the bug is.
## Expected Behavior
A clear and concise description of what you expected to happen.
## Use Case
Is your feature request related to a problem/challenge you are trying to solve? Please provide some additional context of why this feature or capability will be valuable.
## Describe Ideal Solution
A clear and concise description of what you want to happen. If you don't know, that's okay.
## Alternatives Considered
Explain what alternative solutions or features you've considered.
## Additional Context
Add any other context or screenshots about the feature request here.

0
zh/.github/ISSUE_TEMPLATE/question.md vendored Normal file
View File

13
zh/.github/PULL_REQUEST_TEMPLATE.md vendored Normal file
View File

@@ -0,0 +1,13 @@
## What?
* Describe high-level what changed as a result of these commits (i.e. in plain-english, what do these changes mean?)
* Use bullet points to be concise and to the point.
## Why?
* Provide the justifications for the changes (e.g. business case).
* Describe why these changes were made (e.g. why do these commits fix the problem?)
* Use bullet points to be concise and to the point.
## References
* Link to any supporting github issues or helpful documentation to add some context (e.g. stackoverflow).
* Use `closes #123`, if this PR closes a GitHub issue `#123`

41
zh/.github/release-drafter.yml vendored Normal file
View File

@@ -0,0 +1,41 @@
name-template: 'v$RESOLVED_VERSION 🌈'
tag-template: 'v$RESOLVED_VERSION'
categories:
- title: '🚀 Features'
labels:
- 'feature'
- 'enhancement'
- title: '💣 Breaking Change'
label:
- 'breakingchange'
- 'breaking'
- title: '🐛 Bug Fixes'
labels:
- 'fix'
- 'bugfix'
- 'bug'
- title: '📝 Documentation'
label:
- 'doc'
- 'documentation'
- title: '🔨 Maintenance'
label:
- 'chore'
- 'maintenance'
change-template: '- $TITLE @$AUTHOR (#$NUMBER)'
change-title-escapes: '\<*_&' # You can add # and @ to disable mentions, and add ` to disable code blocks.
version-resolver:
major:
labels:
- 'major'
minor:
labels:
- 'minor'
patch:
labels:
- 'patch'
default: patch
template: |
## Changes
$CHANGES

View File

@@ -0,0 +1,28 @@
name: Release Management
on:
# push:
# # branches to consider in the event; optional, defaults to all
# branches:
# - master
# pull_request event is required only for autolabeler
pull_request:
# Only following types are handled by the action, but one can default to all as well
types: [opened, reopened, synchronize, labeled, unlabeled]
jobs:
update_release_draft:
runs-on: ubuntu-latest
steps:
# Drafts your next Release notes
- uses: release-drafter/release-drafter@v5
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
- uses: act10ns/slack@v1
with:
status: ${{ job.status }}
channel: $SLACK_CI_CHANNEL
env:
SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}
SLACK_CI_CHANNEL: ${{ secrets.SLACK_CI_CHANNEL }}

88
zh/.gitignore vendored Normal file
View File

@@ -0,0 +1,88 @@
# Hidden files #
################
.*
#
# Except
#
!*.env.example
!*.circleci
!*.dockeringnore
!*.hosts
!.hosts.example
!*.gitignore
!/.chglog
!/.gitallowed
!/.github
!*.gitkeep
!*.editorconfig
# SSH keys #
############
id_rsa
id_dsa
keys/
# OS generated files #
######################
.DS_Store
.DS_Store?
._*
.Spotlight-V100
.Trashes
ehthumbs.db
Thumbs.db
# Packages #
############
# it's better to unpack these files and commit the raw source
# git has its own built in compression methods
*.7z
*.dmg
*.gz
*.iso
*.jar
*.rar
*.tar
*.zip
*.tar.gz
#
# Except
#
!lambda_function.*.zip
!lambda_function.lambda_handler.zip
!lambda_function.*.zip
# Logs and databases #
######################
*.log
*.sql
*.sqlite
*.out
# IDE related files #
#####################
.classpath
.project
.settings
.idea
.metadata
*.iml
*.ipr
.vscode
/src
/venv
# Custom Project tools files #
########################
*.pyc
*.pyo
*.vault_pass
*.pgpass
*.vagrant
# Project specific files #
#################################
/@bin
site/
ab-results-*

693
zh/CHANGELOG.md Normal file
View File

@@ -0,0 +1,693 @@
# Change Log
All notable changes to this project will be documented in this file.
<a name="unreleased"></a>
## [Unreleased]
<a name="v0.1.34"></a>
## [v0.1.34] - 2021-05-18
- BBL-488 | Adding ES solutions comparison + VPC outbound traffic control solutions comparison + adding Ganalytics domain verification tag
<a name="v0.1.33"></a>
## [v0.1.33] - 2021-05-18
- BBL-192 | minor style and grammar fixes
- BBL-192 | Updating landing background color + adding testimonial and team sections
- BBL-192 | updating landing figures
- BBL-192 | adding and updating landing, testimonial and team figures
<a name="v0.1.32"></a>
## [v0.1.32] - 2021-05-05
- BBL-192 | removing le-helm-infra repo since we're favouring the definition of k8s resources at le-tf-aws-infra repo.
- BBL-192 | compressing landing images to gain page load time performance.
<a name="v0.1.31"></a>
## [v0.1.31] - 2021-04-26
- BIZDEV-26 | updating 1st landing section with cost optimization item
- BIZDEV-26 | landing illustration minor visual fix
- BIZDEV-26 | fixing table of conent menu color
<a name="v0.1.30"></a>
## [v0.1.30] - 2021-04-23
- BIZDEV-26 | Adding how it works code library forks workflow sub-section
<a name="v0.1.29"></a>
## [v0.1.29] - 2021-04-23
- BIZDEV-26 | Adding why our stack section content + fixing broken ref architecture links
- BIZDEV-26 | landing content added and updated
- BIZDEV-26 | upgrading to latest makefiles lib version supporting material mkdocs 7.1.2 docker img + Adding new How it works - Why our Stack section
- BIZDEV-26 | updating and adding landing figures
<a name="v0.1.28"></a>
## [v0.1.28] - 2021-03-03
- BBL-192 | updating material mkdocs via latest ver in makefilelib
- BIZDEV-26 | testing new material mkdocs multi-language experimental feature
<a name="v0.1.27"></a>
## [v0.1.27] - 2021-02-19
- BIZDEV-26 | several doc updates, home work with us image + work with us index
- BIZDEV-26 | 2021 Leverage roadmap has been added to the work with us section.
- BIZDEV-26 | updating landing page work with us section
<a name="v0.1.26"></a>
## [v0.1.26] - 2021-02-10
- BBL-192 | fixing carrers.md file name for careers.md
<a name="v0.1.25"></a>
## [v0.1.25] - 2021-02-08
- BIZDEV-19 | email contact section updated
- BIZDEV-19 | contact section updated
- BIZDEV-19 | Brand new Work with Us section added with carrers, contact, contribute, faqs and support.
- BIZDEV-19 | how-it-works image links updated
- BIZDEV-19 | reorganizing company related files in new work-with-us section
- BIZDEV-19 | updating to latets makefiles lib ver + mkdocs.yaml tree struture updated
- BIZDEV-19 | updating landing with new sections: Work with us + Subscription Plan & New images added.
- Merge branch 'master' into feature/BIZDEV-19-target-audience
- BIZDEV-19 | Adding carrers, contribute and faqs sections
<a name="v0.1.24"></a>
## [v0.1.24] - 2021-02-01
- BIZDEV-19 | rolling back latest css code segretation change
- BIZDEV-19 | latest material mkdocs ver + landing updated and style moved to extra.css
- BIZDEV-19 | centering components and fixing paddings
- BIZDEV-19 | adding footer to landing
- BIZDEV-19 | adjusting CSS for UI responsiveness, landing to fit both desktop and mobile versions.
- BIZDEV-19 | updating section 2 paragraph letter size
- BIZDEV-19 | poiting makefile lib to its latest version
- BIZDEV-19 | updating landing with 2 new leverage related sections
<a name="v0.1.23"></a>
## [v0.1.23] - 2021-01-20
- BBL-455 | minor landing adjustements
- BBL-445 | adding sudo to make apply-rclone to fix permissions denied error
<a name="v0.1.22"></a>
## [v0.1.22] - 2020-12-08
- BBL-445 | fixing typo
- BBL-445 | updating home illustration icons
- BBL-445 | mkdocs.yml updated with newest page tree structure
- BBL-445 | user-guide multiple sections updated - compute, identities, network and organization
- BBL-445 | user-guide base-configuration + base-workflow improved
- BBL-445 | how-it-works multiple sections updated: organization, reliability, security and storage
- BBL-445 | how-it-work sections updated and added - identities, monitoring and network
- BBL-445 | how it works content and format updated - sections: cdn, ci-cd, code-library, compute and costs
- BBL-445 | adding and updating figures and diagrams
- BBL-445 | upgrading Makefile live to use the lastest stable ver including latest stable material-mkdocs image
<a name="v0.1.21"></a>
## [v0.1.21] - 2020-11-16
- BBL-444 | circleci slack notif + latest makefile lib ver
- Merge branch 'master' of github.com:binbashar/le-ref-architecture-doc
- BBL-440 | improving Makefile init-makefiles w/ fixed version
<a name="v0.1.20"></a>
## [v0.1.20] - 2020-10-02
- BBL-381 | migrating mkdocs-material from 5.x to 6.x
- BBL-381 | updating makefile include sintaxt + circleci sumologic integration
<a name="v0.1.19"></a>
## [v0.1.19] - 2020-09-24
- Merge branch 'master' of github.com:binbashar/le-ref-architecture-doc
- BBL-381 | upgrading circleci vm executor
<a name="v0.1.18"></a>
## [v0.1.18] - 2020-09-22
- minor .gitignore sintax update
<a name="v0.1.17"></a>
## [v0.1.17] - 2020-09-22
- BBL-381 | implementing mkdocs-material.mk Makefile
<a name="v0.1.16"></a>
## [v0.1.16] - 2020-09-11
- BBL-381 | re-organizing Makefile blocks
<a name="v0.1.15"></a>
## [v0.1.15] - 2020-09-11
- BBL-381 | Makefile parametrizeing improvement
<a name="v0.1.14"></a>
## [v0.1.14] - 2020-09-11
- BBL-381 | improving makefile inline comment
<a name="v0.1.13"></a>
## [v0.1.13] - 2020-09-11
- BBL-381 | ignoreing Makefile changes during release ci stage
- BBL-381 | forgotten to comment Makefile lines as pre-req -> FIXED!
- BBL-381 | ci job typo fix
- BBL-381 | circleci job sintaxt indentation fixed
- BBL-381 | fixing circleci config
- BBL-381 | testing centralized makefile approach
<a name="v0.1.12"></a>
## [v0.1.12] - 2020-08-19
- BBL-19 | user-guide several sections and sub-sections updated
- BBL-19 | how-it-works several sections updated
- BBL-19 | mkdocs site tree updated + home.html colors updated
- BBL-19 | assets -> adding images + updating extra.css colors
- BBL-19 | Updating .gitignore + Makefile w/ latest mkdocs-material docker img + README.md improved
<a name="v0.1.11"></a>
## [v0.1.11] - 2020-08-11
- Merge branch 'master' into BBL-19-ref-arch-doc-content-updates
- BBL-19 | minor Makefile comment correction + inverting fg-colors for dark-theme still not readable
<a name="v0.1.10"></a>
## [v0.1.10] - 2020-08-11
- BBL-19 | upgrading to latest mkdocs-material docker image + fixing fg-color for dark-theme
<a name="v0.1.9"></a>
## [v0.1.9] - 2020-08-11
- BBL-19 | testing dark-mode color
<a name="v0.1.8"></a>
## [v0.1.8] - 2020-08-10
- BBL-19 | removing not necessary code
- BBL-19 | unnesessary comments clean-up
- BBL-19 | updating identities.md icon
- BBL-19 | user-guide/network/vpc updated + minor changes
<a name="v0.1.7"></a>
## [v0.1.7] - 2020-08-07
- BBL-19 | user-guide/identities/credentials.md read more link added
- BBL-19 | completing user-guide/identities documentation
- BBL-19 | formatting html cover code
- BBL-19 | Customizing color palette
- BBL-19 | upgrade to squidfunk/mkdocs-material:5.5.3
- BBL-19 | updating CircleCi config to release if the build-and-deploy stage successfully finish
<a name="v0.1.6"></a>
## [v0.1.6] - 2020-07-31
- BBL-19 minor adjustments to user-guide identities files
- BBL-19 small sintaxt improvement
- BBL-19 | user-guide/identities completed
<a name="v0.1.5"></a>
## [v0.1.5] - 2020-07-29
<a name="v0.1.4"></a>
## [v0.1.4] - 2020-07-29
<a name="v0.1.3"></a>
## [v0.1.3] - 2020-07-29
- BBL-19 user-guide/organizations email pre-req doc added
<a name="v0.1.2"></a>
## [v0.1.2] - 2020-07-29
<a name="v0.1.1"></a>
## [v0.1.1] - 2020-07-29
- BBL-19 user-guide/base-configuration/overview adding pre-reqs
- BBL-19 user-guide/network/dns updated
<a name="v0.1.0"></a>
## [v0.1.0] - 2020-07-20
- BBL-19 since how-it-works its complete we're releasing v0.1.0 minor ver
- BBL-19 integrating Google Analytics
<a name="v0.0.49"></a>
## [v0.0.49] - 2020-07-16
- BBL-19 Several how it work sections updates - 1st release should be done for this section
- BBL-19 structure update + adding 1st steps section
- BBL-19 new diagrams and screenshots have been added
<a name="v0.0.48"></a>
## [v0.0.48] - 2020-07-10
<a name="v0.0.47"></a>
## [v0.0.47] - 2020-07-10
<a name="v0.0.46"></a>
## [v0.0.46] - 2020-07-10
- BBL-19 fixing user-guide/organizations doc steps order
<a name="v0.0.45"></a>
## [v0.0.45] - 2020-07-06
<a name="v0.0.44"></a>
## [v0.0.44] - 2020-07-06
<a name="v0.0.43"></a>
## [v0.0.43] - 2020-07-06
<a name="v0.0.42"></a>
## [v0.0.42] - 2020-07-06
<a name="v0.0.41"></a>
## [v0.0.41] - 2020-07-06
<a name="v0.0.40"></a>
## [v0.0.40] - 2020-07-06
<a name="v0.0.39"></a>
## [v0.0.39] - 2020-07-06
- BBL-119 user-guide sub-sections extended to map the how-it-works
- BBL-19 Makefile, mkdocs, main doc files updated + examples
- BBL-19 several how-it-works sections / sub-sections added and updated
- BBL-19 updating .gitignore to avoid 'make docs-check-dead-links' resulting files to be added by mistake.
- Merge branch 'master' into BBL-119-mkdocs-gh-updates
- BBL-19 fixing typo in how-it-works/compute
<a name="v0.0.38"></a>
## [v0.0.38] - 2020-06-26
<a name="v0.0.37"></a>
## [v0.0.37] - 2020-06-26
- BBL-19 Mkdocs, home and README.md have been updated
- BBL-19 docs/user-guide sections re-organized and updated
- BBL-19 docs/how-it-words several sections updated
- BBL-19 docs/assets/images new images added
<a name="v0.0.36"></a>
## [v0.0.36] - 2020-06-25
<a name="v0.0.35"></a>
## [v0.0.35] - 2020-06-25
- BBL-19 fixing how it works link in the welcome page
<a name="v0.0.34"></a>
## [v0.0.34] - 2020-06-25
- BBL-19 improving landing text
- BBL-19 reviewing landing text grammar
<a name="v0.0.33"></a>
## [v0.0.33] - 2020-06-25
<a name="v0.0.32"></a>
## [v0.0.32] - 2020-06-25
<a name="v0.0.31"></a>
## [v0.0.31] - 2020-06-25
<a name="v0.0.30"></a>
## [v0.0.30] - 2020-06-25
- BBL-19 fixing welcome to how-it-works hyperlink
<a name="v0.0.29"></a>
## [v0.0.29] - 2020-06-25
<a name="v0.0.28"></a>
## [v0.0.28] - 2020-06-25
<a name="v0.0.27"></a>
## [v0.0.27] - 2020-06-25
- BBL-119 updating landing link to point to the support section
<a name="v0.0.26"></a>
## [v0.0.26] - 2020-06-25
<a name="v0.0.25"></a>
## [v0.0.25] - 2020-06-25
- BBL-19 upgrading home (landing) with custom html
<a name="v0.0.24"></a>
## [v0.0.24] - 2020-06-25
<a name="v0.0.23"></a>
## [v0.0.23] - 2020-06-25
<a name="v0.0.22"></a>
## [v0.0.22] - 2020-06-25
<a name="v0.0.21"></a>
## [v0.0.21] - 2020-06-25
<a name="v0.0.20"></a>
## [v0.0.20] - 2020-06-25
<a name="v0.0.19"></a>
## [v0.0.19] - 2020-06-25
<a name="v0.0.18"></a>
## [v0.0.18] - 2020-06-25
- BBL-119 make docs-deploy-gh cmd in place for circleci job
<a name="v0.0.17"></a>
## [v0.0.17] - 2020-06-25
- BBL-119 dockerizeing mkdocs gh-deploy cmd
<a name="v0.0.16"></a>
## [v0.0.16] - 2020-06-25
- BBL-119 Adding pip install markdown package
<a name="v0.0.15"></a>
## [v0.0.15] - 2020-06-25
- BBL-119 updating Makefile cmd to install mkdocs
<a name="v0.0.14"></a>
## [v0.0.14] - 2020-06-25
- BBL-119 removing not necessary files + circleci updated to autodeploy GitHub Pages site + Makefile update
<a name="v0.0.13"></a>
## [v0.0.13] - 2020-06-24
<a name="v0.0.12"></a>
## [v0.0.12] - 2020-06-24
- Merge branch 'master' into BBL-119-mkdocs-gh-updates
- BBL-119 fixing changelo
<a name="v0.0.11"></a>
## [v0.0.11] - 2020-06-24
<a name="v0.0.10"></a>
## [v0.0.10] - 2020-06-24
- Merge branch 'master' into BBL-119-mkdocs-gh-updates
- BBL-119 fixing typo
<a name="v0.0.9"></a>
## [v0.0.9] - 2020-06-24
- BBL-119 adding dns.md
- BBL-119 small repo reference link fix
<a name="v0.0.8"></a>
## [v0.0.8] - 2020-06-24
- Merge branch 'master' into gh-pages
- Deployed 03ca8fd with MkDocs version: 1.1.2
- Deployed 0fc2215 with MkDocs version: 1.1.2
- Deployed 0fc2215 with MkDocs version: 1.1.2
- Deployed 0fc2215 with MkDocs version: 1.1.2
- Deployed 0fc2215 with MkDocs version: 1.1.2
- Deployed 0fc2215 with MkDocs version: 1.1.2
- Deployed 0fc2215 with MkDocs version: 1.1.2
<a name="v0.0.7"></a>
## [v0.0.7] - 2020-06-24
- BBL-119 minor fixes
<a name="v0.0.6"></a>
## [v0.0.6] - 2020-06-24
- BBL-119 updating .gitignore to avid pushing temporary /site dir by mistake
- BBL-119 updating makefile and removing site dir
<a name="v0.0.5"></a>
## [v0.0.5] - 2020-06-24
- BBL-119 adding .gitignore
- Merge branch 'master' into gh-pages
- BBL-119 mergin gb-pages to master branch
- Deployed fb59342 with MkDocs version: 1.1.2
- Merge branch 'BBL-119-mkdocs-gh-updates' into gh-pages
- Deployed d2f6694 with MkDocs version: 1.1.2
<a name="v0.0.4"></a>
## [v0.0.4] - 2020-06-24
- BBL-119 updating dns.md
- Merge branch 'master' into BBL-119-mkdocs-gh-updates
- BBL-119 adding site folder updates
- BBL-119 adding DNS md file
<a name="v0.0.3"></a>
## [v0.0.3] - 2020-06-24
- Merge branch 'master' into gh-pages
- Deployed 24beaf5 with MkDocs version: 1.1.2
<a name="v0.0.2"></a>
## [v0.0.2] - 2020-06-24
- BBL-119 adding site dir
- BBL-119 commiting docs dir
<a name="v0.0.1"></a>
## v0.0.1 - 2020-06-24
- BBL-119 re ading std structure files to the repo
- BBL-119 small fix in README.md link
- Merge branch 'gh-pages' into BBL-119-mkdocs-gh-updates
- BBL-119 mkdocs deploy
- Deployed d9a8047 with MkDocs version: 1.1.2
- BBL-119 fixing typo in repo name
- BBL-119 updating site url
- BBL-119 adding CNAME file for gp custom domain
- Create CNAME
- Merge branch 'BBL-119-mkdocs-gh-updates' of github.com:binbashar/le-ref-architectre-doc into BBL-119-mkdocs-gh-updates
- BBL-19 | sync deployment w/ locak mkdoc generated site
- Merge branch 'BBL-119-mkdocs-gh-updates' into gh-pages
- Deployed 19f1521 with MkDocs version: 1.1.2
- BBL-119 how-it-works/network sections updated
- BBL-119 minor readme.md image url fix
- BBL-19 sync with master
- Merge branch 'master' into gh-pages
- Deployed a3e72ab with MkDocs version: 1.1.2
- BBL-119 404.html
- Merge branch 'master' of github.com:binbashar/le-ref-architectre-doc
- BBL-119 initialiting repo
- BBL-119 adding docs folder
- BBL-119 adding std repo structure files
- Deployed 8851b11 with MkDocs version: 1.1.2
- Deployed 8851b11 with MkDocs version: 1.1.2
- Deployed 8851b11 with MkDocs version: 1.1.2
- Delete CNAME
- Create CNAME
- Deployed with MkDocs version: 1.1.2
[Unreleased]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.34...HEAD
[v0.1.34]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.33...v0.1.34
[v0.1.33]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.32...v0.1.33
[v0.1.32]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.31...v0.1.32
[v0.1.31]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.30...v0.1.31
[v0.1.30]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.29...v0.1.30
[v0.1.29]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.28...v0.1.29
[v0.1.28]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.27...v0.1.28
[v0.1.27]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.26...v0.1.27
[v0.1.26]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.25...v0.1.26
[v0.1.25]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.24...v0.1.25
[v0.1.24]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.23...v0.1.24
[v0.1.23]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.22...v0.1.23
[v0.1.22]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.21...v0.1.22
[v0.1.21]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.20...v0.1.21
[v0.1.20]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.19...v0.1.20
[v0.1.19]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.18...v0.1.19
[v0.1.18]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.17...v0.1.18
[v0.1.17]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.16...v0.1.17
[v0.1.16]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.15...v0.1.16
[v0.1.15]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.14...v0.1.15
[v0.1.14]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.13...v0.1.14
[v0.1.13]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.12...v0.1.13
[v0.1.12]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.11...v0.1.12
[v0.1.11]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.10...v0.1.11
[v0.1.10]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.9...v0.1.10
[v0.1.9]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.8...v0.1.9
[v0.1.8]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.7...v0.1.8
[v0.1.7]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.6...v0.1.7
[v0.1.6]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.5...v0.1.6
[v0.1.5]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.4...v0.1.5
[v0.1.4]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.3...v0.1.4
[v0.1.3]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.2...v0.1.3
[v0.1.2]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.1...v0.1.2
[v0.1.1]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.1.0...v0.1.1
[v0.1.0]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.49...v0.1.0
[v0.0.49]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.48...v0.0.49
[v0.0.48]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.47...v0.0.48
[v0.0.47]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.46...v0.0.47
[v0.0.46]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.45...v0.0.46
[v0.0.45]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.44...v0.0.45
[v0.0.44]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.43...v0.0.44
[v0.0.43]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.42...v0.0.43
[v0.0.42]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.41...v0.0.42
[v0.0.41]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.40...v0.0.41
[v0.0.40]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.39...v0.0.40
[v0.0.39]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.38...v0.0.39
[v0.0.38]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.37...v0.0.38
[v0.0.37]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.36...v0.0.37
[v0.0.36]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.35...v0.0.36
[v0.0.35]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.34...v0.0.35
[v0.0.34]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.33...v0.0.34
[v0.0.33]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.32...v0.0.33
[v0.0.32]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.31...v0.0.32
[v0.0.31]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.30...v0.0.31
[v0.0.30]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.29...v0.0.30
[v0.0.29]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.28...v0.0.29
[v0.0.28]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.27...v0.0.28
[v0.0.27]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.26...v0.0.27
[v0.0.26]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.25...v0.0.26
[v0.0.25]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.24...v0.0.25
[v0.0.24]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.23...v0.0.24
[v0.0.23]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.22...v0.0.23
[v0.0.22]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.21...v0.0.22
[v0.0.21]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.20...v0.0.21
[v0.0.20]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.19...v0.0.20
[v0.0.19]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.18...v0.0.19
[v0.0.18]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.17...v0.0.18
[v0.0.17]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.16...v0.0.17
[v0.0.16]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.15...v0.0.16
[v0.0.15]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.14...v0.0.15
[v0.0.14]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.13...v0.0.14
[v0.0.13]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.12...v0.0.13
[v0.0.12]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.11...v0.0.12
[v0.0.11]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.10...v0.0.11
[v0.0.10]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.9...v0.0.10
[v0.0.9]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.8...v0.0.9
[v0.0.8]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.7...v0.0.8
[v0.0.7]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.6...v0.0.7
[v0.0.6]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.5...v0.0.6
[v0.0.5]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.4...v0.0.5
[v0.0.4]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.3...v0.0.4
[v0.0.3]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.2...v0.0.3
[v0.0.2]: https://github.com/binbashar/le-ref-architecture-doc/compare/v0.0.1...v0.0.2

1
zh/CNAME Normal file
View File

@@ -0,0 +1 @@
leverage.binbash.co

8
zh/CODE-OF-CONDUCT.md Normal file
View File

@@ -0,0 +1,8 @@
# binbash Leverage Community Code of Conduct
binbash follows the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting
the binbash Code of Conduct responsibles via:
- <leverage@binbash.co>
- <info@binbash.co>

39
zh/CONTRIBUTING.md Normal file
View File

@@ -0,0 +1,39 @@
# Contributing
When contributing, please discuss the change you wish to make via issue
with the owners of this repository before making a change.
Please note we have a code of conduct, please follow it in all your interactions with the project.
## Pull Request Process
1. Make sure that all build or compilation dependencies are removed when performing a build.
2. Update the README.md with details of changes to the interface, this includes new environment
variables, exposed ports, useful file locations and container parameters.
3. Increase the version numbers in any examples files and the README.md to the new version that this
Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you
do not have permission to do that, you may request the second reviewer to merge it for you.
### Collaborate on fixes for security vulnerabilities in private forks
Working in the open means that it is impossible to hide things. And yet, sometimes you will want
to work on some changes to the code in private, for example when fixing a security vulnerability.
Working on a fix in the open might allow attackers to reverse engineer the bug and attack our users.
Since GitHub provides a mechanism to easily create a private fork of our repo, please use these
private forks to collaborate on a security fix.
### Publish maintainer advisories for security fixes
Fixing a security vulnerability is no small feat and we should tell our users about it.
We will do it in a way that will make it easy for you to learn about it and patch
Since GitHub provides an easy way to publish a security advisory, this will
be incorporated and you could add it into your security scanning tools, the ones you
depend on to keep your applications secure.
## Read More
[Leverage Open Source Modules management](https://leverage.binbash.com.ar/how-it-works/infra-as-code-library/infra-as-code-library-forks/)

21
zh/LICENSE.md Normal file
View File

@@ -0,0 +1,21 @@
### The MIT License (MIT)
Copyright (c) 2020 Binbashar Inc
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.

22
zh/Makefile Normal file
View File

@@ -0,0 +1,22 @@
.PHONY: help
SHELL := /bin/bash
MAKEFILE_PATH := ./Makefile
MAKEFILES_DIR := ./@bin/makefiles
MAKEFILES_VER := v0.2.17
help:
@echo 'Available Commands:'
@grep -E '^[a-zA-Z_-]+:.*?## .*$$' $(MAKEFILE_LIST) | sort | awk 'BEGIN {FS = ":.*?## "}; {printf " - \033[36m%-18s\033[0m %s\n", $$1, $$2}'
#==============================================================#
# INITIALIZATION #
#==============================================================#
init-makefiles: ## initialize makefiles
rm -rf ${MAKEFILES_DIR}
mkdir -p ${MAKEFILES_DIR}
git clone https://github.com/binbashar/le-dev-makefiles.git ${MAKEFILES_DIR} -q
cd ${MAKEFILES_DIR} && git checkout ${MAKEFILES_VER} -q
-include ${MAKEFILES_DIR}/circleci/circleci.mk
-include ${MAKEFILES_DIR}/release-mgmt/release.mk
-include ${MAKEFILES_DIR}/mkdocs/mkdocs-material.mk

42
zh/README.md Normal file
View File

@@ -0,0 +1,42 @@
<a href="https://github.com/binbashar">
<img src="https://raw.githubusercontent.com/binbashar/le-ref-architecture-doc/master/docs/assets/images/logos/binbash-leverage-banner.png" width="1032" align="left" alt="binbash"/>
</a>
<br clear="left"/>
# binbash Leverage™ Documentation
## Overview
This repository contains all files used to create
[binbash Leverage Reference Documentation](https://leverage.binbash.co)
### Branches
- `master` --> contains the source code
- `gh-pages` --> deployable (builded) version
## Deployed Documentation
Check it out [here](https://leverage.binbash.co/).
## Development / Contributing
1. Clone the repo locally
2. Config your MkDocs env including the navigation tree directory via `mkdocs.yml` file.
3. Spin up your MkDocs local dev web server environment (`http://localhost:8000`) (real time updates we'll be shown) (docker daemon needed) via `Makefile` cmd
```bash
make init-makefiles # needed only the first time
make docs-live
```
4. Update necessary `*.md` files inside the `docs/` folder and check your updates through the local environment
browser
5. And create your PR from `BBL-XXX` to `master` branch.
6. The Github Pages site [https://leverage.binbash.co](https://leverage.binbash.co/) will be automatically deployed
via CircleCI job to the `gh-pages` branch (currently being built from this branch).
- It currently uses the `make docs-deploy-gh` cmd which could be locally executed if needed too.
### TODO
- Several sections needs completion or update.
## About Diagrams
Some of them have editable version under `docs/assets/diagrams/editable`.
Others are directly exported from `https://docs.google.com/presentation/d/1t2SWgWlGvuIOqYHkpzxQSVLafI_MCsA3gNz6Kkyf6TE/edit#slide=id.p6`.

0
zh/docs/.gitkeep Normal file
View File

1
zh/docs/CNAME Normal file
View File

@@ -0,0 +1 @@
phaten-audio.com

View File

@@ -0,0 +1,21 @@
---
title: 联系我们
---
# 联系我们
## :fontawesome-solid-location-dot:公司地址
地址:深圳市飞腾云科技有限公司 深圳市光明区松柏路7002号埃迪蒙托工业园A栋6楼
Address: 602,Building 1,Edmonto Industrial Park, No.4 Industrial Zone,Shutianpu Community, Matian Street, Guangming District, Shenzhen, China
## :telephone_receiver:线下销售
Angel胡小姐<br>
邮箱angel@phaten.com
## :technologist:技术咨询及选型评估
Allen宿永标<br>
邮箱hua@phaten.com

View File

@@ -0,0 +1,8 @@
---
title: 关于我们
---
# 关于我们
飞腾云音频事业部承袭飞腾云科技在无线音频和物联网领域深厚的研发和生产底蕴专注于XMOS高性能Hi-Fi音频及麦克风的Turnkey解决方案。凭借与XMOS稳固的战略合作伙伴关系我们不仅为客户提供创新应用的核心技术更确保为客户带来前沿的音频体验和市场领先优势。飞腾云音频事业部是您值得信赖的合作伙伴共创明日无线音频新篇章。

View File

@@ -0,0 +1,31 @@
---
title: 加入我们
---
# 加入我们
公司处于快速发展期,现面向社会广泛招聘人才
如有意向请发送简历至zhanghuan@phaten.com并注明岗位
## 音频硬件工程师 2人
### 岗位职责:
- 负责设计硬件PCBA ,能够独立负责SCH, PCB Layout 测试,调试,过认证等工作
- 负责PCBA设计时的物料选型测试工装的设计样机和批量生产的跟产等工作
- 负责物料供应商对接PCBA尺寸形态讨论工作把握生产良率优化产能效率优化
- 编写PCBA音频参数测试报告datasheet规格书参考设计指引说明等文档工作
### 岗位要求:
- 3年以上音频硬件设计经验者
- 有较好的硬件设计理论基础,对所用器件的特点特性有较好的把握
- 能够把握模拟音频信号Layout把握SNR和THD优化数字和模拟的互扰排查
- 熟悉TI, AKM, Cirrus logic, JRC, ESS顺芯等品牌选型熟悉电源Codec运放等功能特性
- 熟悉音频频谱特性熟悉使用硬件设计软件工具音频AP测试设备等

10
zh/docs/about_us/xmos.md Normal file
View File

@@ -0,0 +1,10 @@
---
title: 关于XMOS
---
# 关于XMOS
XMOS是一家总部位于英国半导体公司。XMOS的使命是改变系统在硅芯片上部署的方式 - 通过使嵌入式软件工程师能够简单地将软件加载到我们独特的灵活且易于使用的硬件平台上,打破系统级芯片投入产出的经济性和上市时间。
XMOS是音频领域芯片供应的领导者专注提供音频接口(USB AUDIO)和音频DSP算法在Hi-Fi音频市场拥有绝对的领导地位。

View File

@@ -0,0 +1,6 @@
---
title: 提交成功
---
<div class="goback">
<input type="button" onclick="history.go(-1)" value="返回"/>
</div>

View File

@@ -0,0 +1,28 @@
---
title: 咨询及服务
---
# 咨询及服务
--8<-- "common/phaten_xmos_support_img.md"
--8<-- "common/customer_form.md"
## :fontawesome-solid-location-dot:公司地址
地址:深圳市飞腾云科技有限公司 深圳市光明区松柏路7002号埃迪蒙托工业园A栋6楼
Address: 602,Building 1,Edmonto Industrial Park, No.4 Industrial Zone,Shutianpu Community, Matian Street, Guangming District, Shenzhen, China
## :shopping_cart:产品在线购买
[1688商城](https://ftytec.1688.com/page/offerlist_187437931.htm?spm=a2615.2177701.wp_pc_common_topnav_category.0)
## :telephone_receiver:线下销售
Angel胡小姐<br>
邮箱angel@phaten.com
## :technologist:技术咨询及选型评估
Allen宿先生<br>
邮箱hua@phaten.com

File diff suppressed because one or more lines are too long

View File

@@ -0,0 +1 @@
<mxfile host="Electron" modified="2022-05-25T16:25:31.366Z" agent="5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) draw.io/18.0.6 Chrome/100.0.4896.143 Electron/18.2.3 Safari/537.36" etag="iFSvXINKhewnZkmYtAYJ" version="18.0.6" type="device"><diagram id="hcnf7RYopiIAxkdAj1nI" name="Audit">7VtZb+M2EP41BtqHGqIOH4+xE2+PLLBttligLwEj0TI3tGhQlO3013coUdZBOk6aeGMncgyEHA0PDeeb+UjJPW+63H4SeLX4zCPCeq4TbXveZc91ERoN4J+SPBSSoRsUgljQSCtVghv6L9FCR0szGpG0oSg5Z5KumsKQJwkJZUOGheCbptqcs+aoKxwTQ3ATYmZKv9FILgrpKHAq+a+ExotyZOToK0tcKmtBusAR39RE3lXPmwrOZVFabqeEKeOVdinazfZc3U1MkEQ+pQH7RMf+1/vv42/p+M/J71sn+mf+i1/0ssYs0zd8Q8JMUPkA0osw5Bl0XkxfPpQ2WXGayNyuwQS+MOzU6QVwZapqfbXCDUG7PmwKkFlTfTQF7fqwKUDt7lFrfNSeYE1g1BrdO63xndoE4etNeCYZTch054EOCGOBIworM+WMC5AlPAHrTRZyyaCGoLhZUEluVjhUVt0AekA254nUGEBuWdeGV72Cl0sMYwndR74SRFytSbEghQ5jeJXSu10roZY0pWvyF0mLzpUU/HGlysttrKDbx5vU78eCZ6t8+r/BWNart1C8DRnPItWJFPyelDfZcz34myn/m8wpY62bXxMhKUDrgtFY9S25GgrrGiNzqXoEi9Akvs5rl56jrWAbIsLpgkT6drQjwxBkuxchaIc7CFiEL4kUytHLBiV2daxyPV3fVMj3Sp1FDfVeqYh1tIl3fVeAhILG5DPwGZj49KA+ycJ7YgIzBWG40AaxuuU+U+5x1/oigro3Gw1c31h2rdxYjnKtr/EdYV94SiXN/emOS8mXB50hJMqvm4A5BA6croobndOtmoeBDrTP6+8Kcz7RifYH0v2ehYL+eOBUH9RwtMD0M3/Ud0ampwXHcrQy39a8iUSQCXWVC7ngMU8wu6qkEwgHSbRb8krnmqvFzO39nUj5oFcNZ5I3l7QYUw30P6wNk+WZCMkjepp8SCxi8lh/Q/vqCcKwhLjZZBWvbfqBgfGpiq5SYMoeh7g1EVuTsS0hW5OymZgbanmqtIzQFtpkQ1OITLUyu5pCm8xGJdqtkaU1arXOE3lnzlc154sSEFybeb4/cmvXLikwGZ1HEhVtzAw1mSIvGNiIyTz/nGKasqYkQYrgVtAwoHCpjZCFVaA4ZvJq0SLfTFcDCysaHCtXjd9jqho+MVUFb5mqhkaqekKCMhlYsQ922mCsWdtKMFtY9yE++IENUayF5h1MXwvu1tDWxvF6HfUZj29h2uoE43j4dP0GPtEQmdsW18SnfzQuiQw3uYiWNOm5A6ZY9p2AUqxKP82yvDswJCw4+/mH72hy9cv3t6PJ0nysY7lceYi3f/8SWBLC0TYvljD0DjJCeXB49JSQN70QAj/UFDQZrnr+ogQ1F/AGzagTtI4fW/rIdx7Th0Ixg8oLdrfyAsdwuoR1eglrdyR+KgnLdw03+ePzTbf3PqfNYuAP/fHzNovTIfLQ7MNsFu/Jw+0SJzgmS5jJLTCENVUJ6Hg4P7F9IzJh3u/3DZh3j7e6x1vPerylwk/+ORgC3v4Zl+81QelZuLuVvKOjPeNC5kOu7gC8OwA/f3N2B+DncgBeMIO9QdMbN2PmW/OYsREw/wY2l3anZ694evayDfABh0KHPeqHHqCV49dPbFcrcCjnkqw7gtwR5A9EkEuQldAcvzlB9sznKR1B7gjy+ZuzI8jnQpCL2HYuBLl8eNAR5JMlyAcc6uQIsvmSpibIX0TUEeSOIH8ggjxsEmTfHb85QTbfS+sIckeQz9+cHUE+G4I8OCuCPOoI8qkT5Mcd6uQI8qm+lK9FB9+29J76An7tx9uv+gY+VKsfgxcvQFY/qfeu/gM=</diagram></mxfile>

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

View File

@@ -0,0 +1,6 @@
//左后 // ccb85e5bf4e9
// 右后 // ccb85e5bf4e4
// 左前 // 0cc119b12530
// 右前 // 0cc119b125c3
// 中前 // ccb85e5bf554
// 低重音 // ccb85e5bf4f3

Binary file not shown.

Binary file not shown.

Binary file not shown.

After

Width:  |  Height:  |  Size: 265 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 270 KiB

Binary file not shown.

Binary file not shown.

After

Width:  |  Height:  |  Size: 241 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 4.4 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 331 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 301 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 293 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 291 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 285 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 278 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 291 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.4 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 59 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.3 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 3.7 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 302 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 54 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 21 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 29 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 876 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 46 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 29 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 31 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 32 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 33 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 35 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 29 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 32 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 47 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 997 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.4 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.1 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.9 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 376 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 692 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 245 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.7 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 23 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 18 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 8.1 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 23 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 766 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 24 KiB

Some files were not shown because too many files have changed in this diff Show More