-
Notifications
You must be signed in to change notification settings - Fork 0
Refactor all texts #21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
…elease notes - Revised the "Начало работы" section to clarify development conventions and installation steps. - Enhanced the "Почему Servactory" section with a detailed overview of the framework's benefits and usage examples. - Updated release notes for versions 2.2 to 2.14, highlighting key changes, improvements, and support for Ruby and Rails versions.
- Revised the "Начало работы" section to provide a clearer introduction to Datory, including installation and setup instructions. - Added sections on nested data handling and examples for DTO creation, serialization, and deserialization. - Enhanced descriptions across various guides to improve clarity and usability for users.
- Updated the "Начало работы с Featury" section to provide a clearer introduction, including installation and setup instructions. - Added detailed development conventions and examples for creating and using features. - Revised the "Информация об объекте Featury" section to clarify methods for retrieving feature information and their structure.
- Updated the "Getting Started with Featury" section to enhance the introduction and installation instructions. - Improved the structure and content of the "Development Conventions" and "Version Support" sections. - Enhanced the "Featury Actions" and "Callbacks" documentation for better understanding. - Revised various sections for consistency in terminology and formatting across the documentation.
✅ Deploy Preview for servactory ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
…nto docs/refactoring
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR refactors and standardizes documentation across the Datory and Featury guides by updating frontmatter descriptions, normalizing heading styles, and expanding examples for clarity.
- Updated frontmatter
descriptionfields for more precise context - Standardized heading capitalization and naming conventions
- Added new introductory sections and code examples in both English and Russian docs
Reviewed Changes
Copilot reviewed 38 out of 38 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| docs/ru/datory/guide/usage/deserialization.md | Expanded page description with specific focus |
| docs/ru/datory/guide/info.md | Added overview of info and describe methods |
| docs/ru/datory/guide/data/nesting.md | Clarified nesting methods and added full examples |
| docs/ru/datory/guide/data/attributes.md | Detailed attribute helper descriptions |
| docs/ru/datory/getting-started.md | Introduced “What is Datory?” and first DTO guide |
| docs/guide/options/usage.md | Capitalized headings and refined option text |
| docs/guide/options/dynamic.md | Normalized dynamic options headings |
| docs/guide/options/advanced.md | Standardized advanced mode headings and notes |
| docs/guide/i18n.md | Minor phrasing adjustments for clarity |
| docs/guide/extensions.md | Refined description and heading for extension guide |
| docs/guide/exceptions/success.md | Revised titles and phrasing for success flow |
| docs/guide/exceptions/failure.md | Standardized method descriptions and error terms |
| docs/guide/configuration.md | Consistent capitalization and phrasing |
| docs/guide/actions/usage.md | Refined action usage wording and headings |
| docs/guide/actions/grouping.md | Updated grouping option headings |
| docs/featury/guide/info.md | Added context sentence about purpose of info |
| docs/featury/guide/features.md | Removed stray blank line |
| docs/featury/guide/callbacks.md | Updated frontmatter titles and descriptions |
| docs/featury/guide/actions.md | Refined overview and example wording |
| docs/featury/getting-started.md | Added “What is Featury?”, conventions, and examples |
Comments suppressed due to low confidence (2)
docs/guide/extensions.md:17
- [nitpick] Consider renaming this heading to “### Connecting” or “### Extension Connection” to clearly indicate the action rather than the noun ‘Connection’.
### Connection
docs/guide/options/usage.md:14
- [nitpick] This fragment is a sentence fragment; consider rephrasing to “It uses the
is_a?method.” for consistency and readability.
Uses the `is_a?` method.
No description provided.