You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 19, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: .github/CONTRIBUTING.md
+10-2Lines changed: 10 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,6 +24,8 @@ If you write and contribute a full topic, we will add your name (or your company
24
24
1.[Fork](https://help.github.com/articles/fork-a-repo/) the [DevDocs repository](https://github.com/magento/devdocs). Remember to [sync your fork](https://help.github.com/articles/syncing-a-fork/) and update branches as needed.
25
25
1. Review the [DevDocs guidelines](#contribution-guidelines).
26
26
27
+
**Note:** If you use a fork instead of a branch, please set permissions to allow maintainers to edit and update the PR. See [Allowing changes to a pull request branch created from a fork](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork) in the _GitHub documentation_.
28
+
27
29
## Contribute documentation
28
30
29
31
The following diagram shows the contribution workflow:
@@ -72,6 +74,8 @@ The following guidelines may answer most of your questions and help you get star
72
74
- Review your work for basic typos, formatting errors, or ambiguous sentences before opening a pull request.
73
75
- Revise pull requests according to review feedback. We will close pull requests that require an inordinate amount of time to review and process (especially for minor changes) if you fail to make revisions according to review feedback.
74
76
- Do not directly contact DevDocs team members or maintainers on Slack to review your pull request unless it has been open for more than five days. We have a process and queue for pull requests that everyone must follow.
77
+
- Get recognized on the DevDocs web site for writing new topics! Add your name and a link to your company website or GitHub profile to the file metadata so that we can display it on the page. See [Edit metadata](#edit-metadata).
78
+
- We no longer recognize individual community members who contribute features to the Magento 2 codebase in the corresponding feature topic(s) on the DevDocs website. Magento recognizes these contributions in more appropriate channels (for example, the [Magento DevBlog](https://community.magento.com/t5/Magento-DevBlog/bg-p/devblog)).
75
79
76
80
## Tips for writing content
77
81
@@ -108,8 +112,10 @@ The Markdown (.md) file's metadata is a set of YAML key-value pairs. The metadat
108
112
```yaml
109
113
110
114
---
111
-
group: install2
112
-
title: Continue with your installation
115
+
group:
116
+
title:
117
+
contributor_name:
118
+
contributor_link:
113
119
---
114
120
```
115
121
@@ -119,6 +125,8 @@ title: Continue with your installation
119
125
| ------------- | ---------- |
120
126
|`group`| Defines the topic's guide or section. Use the table of contents `.yml` file name. This loads your left-side navigation. We will help during the PR process to add new files to the `.yml` file. |
121
127
|`title`| Sets the title of the page in the HTML metadata and the main title on the page. |
128
+
|`contributor_name`| Sets the name of the contributor who wrote the topic and displays it on the page. |
129
+
|`contributor_link`| Creates a link to the contributor's GitHub profile or company website. |
Copy file name to clipboardExpand all lines: _plugins/page-params/page-baseurl-generator.rb
+4-14Lines changed: 4 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -6,29 +6,19 @@
6
6
# This custom plugin dynamically sets and injects the page.baseurl variable
7
7
# based on the page's destination.
8
8
#
9
-
# The hook introduces the page.baseurl and
10
-
# page.guide_version data parameters for each page.
9
+
# The hook introduces the page.baseurl parameter for each page.
11
10
# For pages at guides/v2.x the page.baseurl parameter is set
12
11
# as "{site.baseurl}/guides/v#{version}".
13
12
# The {version} is taken from the 'guide_version' front matter parameter on the page;
14
-
# if it is not set, then the 'guide_version' is set to version from the page path (for example, "2.2" in the "guides/v2.2/**/*.md");
15
-
# if the path doesn't contain "guides/v2.x", then the version is unset and returns the nil object (same as null)
13
+
# if it is not set, then the 'guide_version' is set to version from the _config.yml depending on a scope by path (for example, "2.4" at the "guides/v2.4/");
14
+
# otherwise, the version is unset and returns the nil object (same as null).
16
15
Jekyll::Hooks.register:pages,:post_initdo |page|
17
16
# Glossary. Create and assign variables to be used in the script.
0 commit comments