文件列表:

.editorconfig (327, 2023-08-07)
.eslintrc.cjs (105, 2023-08-07)
.file-name-linter.json (338, 2023-08-07)
.markdownlint.json (266, 2023-08-07)
.nojekyll (0, 2023-08-07)
.travis.yml (113, 2023-08-07)
.vscode (0, 2023-08-07)
.vscode\settings.json (3148, 2023-08-07)
LICENSE.md (739, 2023-08-07)
Makefile (547, 2023-08-07)
config (0, 2023-08-07)
config\docker-compose.yml (136, 2023-08-07)
config\sitemap.xml (306, 2023-08-07)
docs (0, 2023-08-07)
docs\images (0, 2023-08-07)
docs\images\wechaty-jekyll.png (111347, 2023-08-07)
jekyll (0, 2023-08-07)
jekyll\Gemfile (632, 2023-08-07)
jekyll\Makefile (551, 2023-08-07)
jekyll\_config.yml (1682, 2023-08-07)
jekyll\_contributors (0, 2023-08-07)
jekyll\_contributors\7sdream.md (463, 2023-08-07)
jekyll\_contributors\abhishek.md (455, 2023-08-07)
jekyll\_contributors\aiamber.md (609, 2023-08-07)
jekyll\_contributors\aishiqi.md (311, 2023-08-07)
jekyll\_contributors\alex2010.md (383, 2023-08-07)
jekyll\_contributors\alienfist.md (337, 2023-08-07)
jekyll\_contributors\anaivebird.md (340, 2023-08-07)
jekyll\_contributors\antonia0912.md (335, 2023-08-07)
jekyll\_contributors\aquaindigo.md (805, 2023-08-07)
jekyll\_contributors\archy.md (762, 2023-08-07)
... ...

## Tutorials 1. [零基础小白在Wechaty社区发表自己的第一篇博客, @juzibot, Jul 02, 2021](https://wechaty.js.org/2021/07/02/how-to-publish-blog-on-wechaty/) 2. [入门:小白如何在wechaty社区发布自己的第一篇博客(一), @atorber, Apr 22, 2021](https://wechaty.js.org/2021/04/22/how-to-publish-blog-on-wechaty/) ## How To Post a Blog To submit a blog post for publication on [wechaty.js.org](https://wechaty.js.org), you can follow the steps below. 1. Fork this repository. If you don't know what is meant by forking a repository, read about it [here](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo) 2. Clone the forked repository to your local machine. If you don't know how to do that, [this article](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository) explains it well 3. Make sure your forked repository is in sync with the main repository. If you don't know how to sync a forked repository,read about it in [this article](https://help.github.com/cn/github/collaborating-with-issues-and-pull-requests/syncing-a-fork) 4. We prefer using [gitHub flow](https://guides.github.com/introduction/flow/). Therefore start by creating a branch for your blog using the command `git checkout -b name-of-blog-branch`. Give the branch a meaningful name 5. Create a markdown file in [jekyll/\_posts](./jekyll/_posts) folder. The file name should follow the format `YYYY-MM-DD-your-blog-slug.md`. For example `2016-12-03-welcome-to-wechaty.md` 6. Write your blog in markdown in the file you created in the previous step. If you are not familiar with markdown syntax, you can learn it [here](https://guides.github.com/features/mastering-markdown/) 7. Add related images to [jekyll/assets](./jekyll/assets) folder under `$YEAR/$MONTH-your-blog-slug/` directory 8. Add your info into `jekyll/_contributors/your_github_id.md` 9. Use mermaid: [URL](/jekyll#use-mermaid) 10. Commit your changes using the command `git commit -am "YOUR_BLOG_TITLE"`. `YOUR_BLOG_TITLE` is the title of your blog 11. Push your branch to github using the command `git push origin name-of-blog-branch`. 12. Create new Pull Request(PR) 13. Sign the [CLA](https://en.wikipedia.org/wiki/Contributor_License_Agreement) 14. Wait for the continuous integration workflow run to finish. If it is failing, fix whatever is making it to fail so that CI turns green 15. Wait for @wechaty/editors to review your PR That's it! ## Guidelines For Writing a Blog Post ### 1. Your blog post should have a Header The header of your blog post should have a title, author and image. This is illustrated in the example below: ```yaml --- title: "'Score Your Face Photo' a ML&Wechaty practice" author: your_github_username image: your_teaser_image_path --- ``` ### 2. Writing Style - You should keep all filenames and URLs as lowercase. Use `-` character between words instead of space when creating a new file or directory. e.g. `2017-10-06-wechat-pc-impactor` instead of `2017-10-06-WeChat PC Impactor`. No Chinese should be used in any filename. - Find a good image for the blog to make it more beautiful. - You should embed photos and videos before publishing, save all external files to the `/jekyll/assets/${YEAR}/$MONTH-your-blog-slug/` directory. ### 3. Do Not Commit Unrelated Files Please do not commit unrelated files. It will keep things tidy and make it easier to review your PR. ### 4. How To Add Videos and PDFs To Your Blog Post You can add videos and PDFs to your blog post by using the syntax below. Example of how to add video or pdf ```html {% include iframe.html src="https://www.youtube.com/watch?v=3eq8wJfCAWs" %} ``` or ```html {% include iframe.html src="/assets/2020/qijibot/final.pdf" %} ``` You can read more at: [Add iframe to wechaty blog](https://wechaty.js.org/2020/08/24/add-video-to-wechaty-blog/) ## How To Run Tests In order to make sure your changes have not broken anything, you can run the following commands before pushing your changes to gitHub. ```sh npm install npm test ``` ## How To Preview Your changes If you want to preview your blog post or changes on localhost, you need to have Jekyll installed in your machine. You can follow the [jekyll quickstart](https://jekyllrb.com/docs/) instructions to install jekyll. ### 1. Install Jekyll by Hand Run Jekyll at localhost to preview your blog post by running the commands below. ```sh make install cd jekyll; make serve # or either run `./scripts/jekyll-serve.sh` for a fresh new start by cleaning cache ``` ### 2. Preview the Blog You can view the blog by navigating to in your browser ## How To Make Other Contributions If you are not interested in writing a blog post but would still love to make a contribution, you are still welcome. We are delighted to have you around. ### Why contribute? As an open source product, Wechaty thrives from contributions of community members. Whatever your skill set is, there is a lot you can do to help us make Wechaty better! So start forking! At the same time, we also meet up offline all over the world. Here are some activities you are invited to join if you are interested: - [Wechaty Contributor Dinner](https://wechaty.js.org/2017/04/26/wechaty-meeting/) - [The memorabilia of The First Chatie WWDC Party](https://wechaty.js.org/2017/06/06/the-first-chatie-wwdc-party/) - [Shanghai WWDC - Wechaty Worldwide Developers Conference](https://wechaty.js.org/2017/08/28/wechaty-shanghai-meetup/) - [Wechaty Contributor Dinner with Data Girls](https://wechaty.js.org/2018/01/14/wechaty-contributor-dinner-data-girl/) - [Wechaty Country Wide Developer Conference](https://wechaty.js.org/2018/09/15/country-wide-developer-conference/) - ..... ### How to Run Locally 1. Clone this repository: `git clone "https://github.com/wechaty/wechaty.js.org"` 2. On the terminal navigate to the root directory `cd wechaty.js.org` 3. Run the commands : 1. `npm install` 2. `npm run docusaurus:build` 3. `npm run docusaurus:serve` 4. The site will be running locally on `http://localhost:3000` ### How To Contribute To the Documentation 1. Fork this repository 2. Create your documentation branch: `git checkout -b branch-name` 3. Make changes to the documentation in markdown 4. Add changes to the staging area `git add .` 5. Commit your changes using the command `git commit -m 'commit message'` 6. Push your changes to gitHub `git push origin branch-name` 7. Create new Pull Request ## Resources - [Migrating from gitbook to docsify.js](https://timdams.com/2019/05/02/migrating-from-gitbook-to-docsify-js/) - [Integrating GitBook with JSDoc to Document Your Open Source Project](https://gist.github.com/KevinAst/7e12***8245ff2a8e9c1557135014b933) - [Markdown Linting Rules Documents](https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md) ## Writers [](https://sourcerer.io/fame/huan/wechaty/wechaty.js.org/links/0) [](https://sourcerer.io/fame/huan/wechaty/wechaty.js.org/links/1) [](https://sourcerer.io/fame/huan/wechaty/wechaty.js.org/links/2) [](https://sourcerer.io/fame/huan/wechaty/wechaty.js.org/links/3) [](https://sourcerer.io/fame/huan/wechaty/wechaty.js.org/links/4) [](https://sourcerer.io/fame/huan/wechaty/wechaty.js.org/links/5) [](https://sourcerer.io/fame/huan/wechaty/wechaty.js.org/links/6) [](https://sourcerer.io/fame/huan/wechaty/wechaty.js.org/links/7) To get to know all our writers, see ## History ### main v0.11 (Apr 1, 2022) Split repo from one to two: Jekyll (this one) and [Docusaurus](https://github.com/wechaty/docusaurus). See: [Issue wechaty/wechaty.js.org#1](https://github.com/wechaty/wechaty.js.org/issues/1) ### v0.9 (Aug 23, 2021) 1. Add OpenAPI Specification docs at ([#1218](https://github.com/wechaty/wechaty.js.org/issues/1218)) ### v0.5 (Aug 12, 2020) 1. Using docusaurus for docs 1. Rename chatie to wechaty ### v0.3 (Mar 9, 2017) Rename wechaty to chatie ### v0.0.1 (Dec 4, 2016) Init version ## Maintainers 1. [@lijiarui](https://github.com/lijiarui), [Rui LI](https://wechaty.js.org/contributors/lijiarui), Microsoft AI MVP, Founder & CEO of Juzi.BOT (YC W19 Alumni) 1. [@huan](https://github.com/huan), [Huan LI](https://wechaty.js.org/contributors/huan), Tencent TVP of Chatbot, \ 1. [@wj-Mcat](https://github.com/wj-Mcat), [Jingjing WU](https://wechaty.js.org/contributors/wj-mcat), Author of [Python Wechaty](https://github.com/wechaty/python-wechaty) And [wechaty/contributors](https://github.com/orgs/wechaty/teams/contributors/members) ## Copyright & License - Code & Docs 2016-now Wechaty Contributors - Code released under the Apache-2.0 License - Docs released under Creative Commons

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：