Django 项目
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
本页面包含 Google 文档季接受的技术写作项目的详细信息。
项目摘要
- 开源组织:
- Django
- 技术文档工程师:
- Gabbyprecious
- 项目名称:
- 重写了贡献指南,使其更易于使用和浏览
- 项目时长:
- 标准时长(3 个月)
Project description
ABSTRACT
与所有其他文档一样,Django 的贡献指南旨在指导用户(在本例中为开源贡献者)了解如何以及在哪些方面贡献力量,以便让 Django 变得更好、更可持续。
我们始终需要编写文档,尤其是对社区和 Django 本身有重大影响的文档。
今年,Django 参与 Google 文档之夏活动的目标是,让贡献指南更易于访问,内容更通俗易懂,让贡献者感到宾至如归。这一目标至关重要,因为它鼓励贡献者(我本人就是其中之一)开始为这个出色的框架做出贡献。
当前状态
您可以在此处找到当前阶段的文档,但它并不像指南那样实用,因为内容太多且结构不清晰,导致人们对 Django 中的贡献了解不深,也不欢迎新贡献者。
项目目标
我在论坛上与我的导师 Carlton Gibson 讨论了有关文档的建议,他认为这些建议有助于解决当前文档存在的大量问题。以下是我计划通过重构文档来实现的目标:
重构文档
添加各部分的“应做”和“不应做”事项
为“请求和制作功能”等琐碎部分创建单独的页面
精简文档并直奔主题
提供字词术语表
根据新指南构建内部索引
撰写更贴近用户的文档
将内容划分为两个主要部分(新手贡献者和高级贡献者部分)
为新手技术文档撰写者/贡献者构建指南和样式,以确保文档保持最新状态并遵循标准。
目前的文档已面向高级贡献者,不适合新手贡献者和 Django 新手贡献者,因此我们为新手贡献者准备了一些额外的内容:
为不同贡献者(技术文档撰写者、设计师和开发者)提供指导的部分
记录新手问题和可解决的简单问题的页面。
从当前文档中取出几个部分,进行重写,然后添加到“新手”部分。
用于解释高级部分中使用的要点或字词的部分。
时间轴
下面将详细介绍我打算如何使用 Google 提供的日历来实现上述项目目标。
社区互动周(8 月 17 日至 9 月 13 日)
与社区进行更多互动
继续为文档做出贡献
从贡献者那里获得更多建议
更多地研究当前文档和预期工具
第 1 周至第 4 周
开始根据等级对文档进行分区
创建文档的初学者部分
第 4 周至第 6 周
整理“应做”和“不应做”清单
编写分区“应做”和“不应做”清单
为各部分创建其他页面
第 7 周至第 9 周
重写并将当前文档移至“高级贡献者指南”
缩减文档内容
第 10 周至第 12 周
准备术语表
将内部索引更新为新文档
为新加入的技术文案撰写者/贡献者创建指南和样式
Sphinx - 当前文档的当前工具。
请参阅文档。
为什么要开展此项目?
我坚信,编写出优质的文档和文章,可以让世界各地的所有人都能受益。除此之外,我还喜欢 Django 和开源。作为一名初学者,我一直想为 Django 做出贡献,我认为这是为自己喜爱的工具做出贡献的绝佳方式,同时还可以熟悉代码库,以便作为开发者(和技术文档撰写者)做出更多贡献。与与我的观点相符且对我的整个职业生涯有很大帮助的组织合作,将会是一件愉快而美好的事。
为什么我适合参与此项目?
我认为自己符合以下条件,因此是合适的候选人:
我一直在为 Django 做出贡献,撰写文章来帮助初学者更好地理解 Django 的概念。
我是一名开发者,并且很期待为 Django 做贡献,我了解其他开发者的需求,以及如何为他们提供良好的文档记录。
我是一个团队合作者,在导师 Carlton Gibson 的监督下,我会更加努力地工作。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-25。
[null,null,["最后更新时间 (UTC):2025-07-25。"],[[["\u003cp\u003eThis Google Season of Docs project aims to rewrite Django's contributor guide, making it more user-friendly and accessible for all levels of contributors.\u003c/p\u003e\n"],["\u003cp\u003eThe project focuses on restructuring the guide, adding clear sections for beginners and advanced contributors, and incorporating practical elements like dos and don'ts, a glossary, and an internal index.\u003c/p\u003e\n"],["\u003cp\u003eThe current documentation is considered overwhelming and poorly structured, leading to this project's goal of simplifying and improving its usability.\u003c/p\u003e\n"],["\u003cp\u003eGabbyprecious, the technical writer, brings experience in writing Django-related articles and a passion for open source, making her well-suited for this endeavor.\u003c/p\u003e\n"],["\u003cp\u003eThe project will be carried out over three months, utilizing tools like Sphinx and Read the Docs to enhance the documentation's clarity and organization.\u003c/p\u003e\n"]]],["The project aims to restructure Django's contribution guide to be more user-friendly and accessible. Key actions include segmenting content into beginner and advanced sections, adding \"dos and don'ts,\" and creating single pages for specific tasks. A glossary and internal index will be developed. The contributor will also develop a style guide for future technical writers and will reduce the documentation's overall length. A detailed timeline will guide the execution.\n"],null,["# Django project\n\nThis page contains the details of a technical writing project accepted for\nGoogle Season of Docs.\n\n### Project summary\n\nOpen source organization:\n: Django\n\nTechnical writer:\n: Gabbyprecious\n\nProject name:\n: Rewrite Contribution guide to be more user-friendly and easily navigated\n\nProject length:\n: Standard length (3 months)\n\n### Project description\n\n#### ABSTRACT\n\nThe goal of Django's contribution guide like every other documentation is to guide user, open-source contributors in this case on how and where they can contribute to making Django better and sustainable.\n\nThere's always a need to make documentations especially one that greatly affects the community and Django itself.\n\nThe goal of Django for this year's Google Summer of Docs is to make the Contribution guide less overwhelming, accessible, and welcoming to contributors. This is a goal which is essential as it encourages contributors, which I myself belong to in getting started to contribute to this great framework.\n\n#### Current State\n\nThe current stage of the documentation which can be found here, is not really much of a guide as it is too overwhelming and not well structured and leads to less understanding of contribution in Django and not welcoming to new contributors.\n\n#### Project Goals\n\nI discussed my suggestions for the documentation with my mentor, Carlton Gibson in the forum and he approves that it will help with the overwhelming issue with the current documentation. Here are the goals I plan on achieving restructuring the document:\nRestructure the document\nAdd sectional Dos and Don'ts\nCreate single pages for trivial sections like Requesting and making features\nReduced and straight to point documentation\nGlossary for words\nInternal Index built to follow the new guide\nWrite a more relatable friendly documentation\nSegmenting the contents into two main parts (Beginners and Advanced Contributors section)\nConstruct a guide and style for new technical writers/contributors, to keep the docs up to date and follow standards.\n\nThe current documentation is already targeted at advanced contributors, and doesn't give chance to new and beginners contributors both to open source and Django, here are some additional contents for beginners:\nSection that guides different set of contributors(technical writers, designers and developers)\nA page that documents first timer issues and easy issues that can be solved.\nTake a few sections in current documentation, rewrite and add to the beginners section.\nSections that explain key points or words used in the advanced section.\n\n#### Timeline\n\nHere will be a breakdown on how I want to work on the project goal as listed above with the calendar provided by Google.\n\nCommunity bonding week( August 17 - September 13)\nGet to engage more with the community\nContinue contributing to the documentation\nGetting more suggestions from Contributors\nMore study of current Documentation and intended tools\nWeek 1 - week 4\nStart out on sectioning documentation based on Levels\nCreate the beginners section of documentation\nWeek 4 - 6\nCurating Dos and Don'ts\nWriting out sectional Dos and Don'ts\nAdditional pages for sections\nWeek 7 - 9\nRewrite and move current documentation to Advanced Contributor guide\nReduced Documentation\nWeek 10 - 12\nPrepare Glossary\nUpdate Internal Index to new documentation\nCreate a guide and style for incoming technical writers/contributors\n\n#### Tools\n\nSphinx - current tool for current documentation.\nRead the Docs.\n\n#### Why this Project?\n\nI'm a core believer in well written documentations and articles to encompass everyone in part of the world. Aside from that, I'm also a lover of Django and Open source as a whole. I have been meaning to contribute to Django as a beginner and I think this is a perfect way to contribute to my favourite tool, while also getting acquainted with the codebase to offer more contribution as a developer(and a technical writer). It will be pleasant and beautiful to work with an organisation that aligns with my views and has been a great tool to my whole career.\n\n#### Why am I the right person for this project?\n\nI believe I'm the right person based on the following accounts:\nI have been contributing to Django by writing articles to help beginners understand the concept of Django more.\nBeing a developer and one looking forward to contributing to Django, I understand the need of fellow developers and how to document it well for them.\nI'm a team player and will work well under less or more supervision of my mentor Carlton Gibson."]]