├── .github ├── label-actions.yml ├── ISSUE_TEMPLATE │ ├── feature_request.md │ ├── others---question.md │ └── bug_report.md └── workflows │ └── process-labels.yml ├── SECURITY.md ├── README.md └── CODE_OF_CONDUCT.md /.github/label-actions.yml: -------------------------------------------------------------------------------- 1 | stale: 2 | close: true 3 | close-reason: '' 4 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | # Security Policy 2 | 3 | ## Reporting a Vulnerability 4 | 5 | Please report to directly. 6 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature_request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Feature request 3 | about: Suggest an idea for this project 4 | title: "[Feature]" 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | 15 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/others---question.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Others / Question 3 | about: Describe this issue template's purpose here. 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | 15 | -------------------------------------------------------------------------------- /.github/workflows/process-labels.yml: -------------------------------------------------------------------------------- 1 | name: Actions 2 | # This workflow is triggered when a label is added to an issue. 3 | on: 4 | issues: 5 | types: labeled 6 | 7 | jobs: 8 | processLabelAction: 9 | name: Process Label Action 10 | runs-on: ubuntu-latest 11 | steps: 12 | - uses: actions/checkout@v2 13 | - name: Process Label Action 14 | uses: hramos/label-actions@v1 15 | with: 16 | repo-token: ${{ secrets.GITHUB_TOKEN }} 17 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug_report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report 3 | about: Create a report to help us improve 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | - [ ] Searched existing issues to avoid creating duplicates. 11 | 12 | - [ ] Confirmed that it can be reproduced in built-in themes without customized css. 13 | 14 | If it only exists in 3rd party themes or css, you can still report it, but please attach the theme target or the css file. We may not "fix" it, if it is caused by 3rd party themes or css styles that we cannot support. 15 | 16 | - [ ] Searched http://support.typora.io/ 17 | 18 | ---- 19 | 20 | **Describe the bug** 21 | A clear and concise description of what the bug is. 22 | 23 | **To Reproduce** 24 | Steps to reproduce the behavior: 25 | 1. Go to '...' 26 | 2. Click on '....' 27 | 3. Scroll down to '....' 28 | 4. See error 29 | 30 | **Expected behavior** 31 | A clear and concise description of what you expected to happen. 32 | 33 | **Screenshots / Screencasts** 34 | If applicable, add screenshots / screencasts to help explain your problem. 35 | 36 | **Sample Markdown File** 37 | Please attach or send us the sample md file that may reproduce this. 38 | 39 | **Desktop (please complete the following information):** 40 | - OS: [e.g. Windows 10 32bit] 41 | 42 | **Typora Version** 43 | e.g: 0.10.11 44 | 45 | **Additional context** 46 | Add any other context about the problem here. 47 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Typora 2 | 3 | > Note: Our offical website is and . All other websites without those two domain suffix is phishing site. 4 | 5 | [Typora](http://typora.io) is a minimal markdown editor, providing new ways for reading and writing markdown. 6 | 7 | Typora is commercial software (not open source). [Typora on GitHub](https://github.com/typora) supports collaboration between its developer, and its *user community*, providing a place to transparently report issues, collect feedback and discuss future direction. It also provides open source resources for user customization of themes. 8 | 9 | # The Typora Issues Repo 10 | 11 | The repo you are looking at is the Typora Issues Repo. It exists as a public forum to gather users' feedback and discussions on bugs, missing features or desired enhancements. For questions on how to use Typora, see [How to find support](#how-to-find-support). 12 | 13 | While you can use email to send bug reports or suggestions, I and the Typora community prefer you use this public forum for the sake of transparency and efficiency. 14 | 15 | As a developer I want to make Typora perfect. I welcome all user ideas and opinions. 16 | 17 | ## How to report a bug, missing feature, or suggest an enhancement 18 | 19 | 1. Open the `Issues` tab above. Search existing issues to see if someone else has already beat you to it. 20 | 2. If someone has, feel free to vote that issue up or add your own feedback in a comment. 21 | 3. If not, click the `New Issue` button and explain. 22 | - For bug reports, **please provide your OS version, Typora version, and if possible, detailed steps to reproduce the bug**. 23 | - Please make sure your issue are searchabale (provide English key words or descriptions) 24 | 25 | If you have multiple bugs or requests that are not closely related, please separate them into different issues. 26 | 27 | # How to get support 28 | 29 | If you want help on using Typora, first search the [Support Site](http://support.typora.io). 30 | 31 | If you can't find what you need there, follow the steps above for reporting a bug. It is ok to use the Issues database to ask a question. You may also email us if you prefer. 32 | 33 | If you want to help improve the Support Site, please feel free to make a pull request on the [Support Site repo](https://github.com/typora/wiki-website). 34 | 35 | # How to customize a theme 36 | 37 | See [quick start about Typora themes](http://support.typora.io/About-Themes/), You could also find detailed documents about how to write/share a Typora theme from [here](http://theme.typora.io/doc/). 38 | 39 | # How to share a tip 40 | 41 | If I have some tips to share, fork our [Support Site](http://support.typora.io)! 42 | 43 | # Help translate Typora 44 | 45 | Fork this project -> https://github.com/typora/Typora-i18n 46 | 47 | 48 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. 6 | 7 | ## Our Standards 8 | 9 | Examples of behavior that contributes to creating a positive environment include: 10 | 11 | * Using welcoming and inclusive language 12 | * Being respectful of differing viewpoints and experiences 13 | * Gracefully accepting constructive criticism 14 | * Focusing on what is best for the community 15 | * Showing empathy towards other community members 16 | 17 | Examples of unacceptable behavior by participants include: 18 | 19 | * The use of sexualized language or imagery and unwelcome sexual attention or advances 20 | * Trolling, insulting/derogatory comments, and personal or political attacks 21 | * Public or private harassment 22 | * Publishing others' private information, such as a physical or electronic address, without explicit permission 23 | * Other conduct which could reasonably be considered inappropriate in a professional setting 24 | 25 | ## Our Responsibilities 26 | 27 | Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. 28 | 29 | Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. 30 | 31 | ## Scope 32 | 33 | This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. 34 | 35 | ## Enforcement 36 | 37 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at abner@typora.io. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. 38 | 39 | Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. 40 | 41 | ## Attribution 42 | 43 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version] 44 | 45 | [homepage]: http://contributor-covenant.org 46 | [version]: http://contributor-covenant.org/version/1/4/ 47 | --------------------------------------------------------------------------------