By dokumori on
In D7 strings, placeholders are used to add links to handbook pages. For example:
<a href="@handbook_url">
documentation-japanese group is planning on translating the handbook and I would like to know the links should be changed. Should we hard-code the link to the translated nodes, or is there another way?
Comments
hi
please follow these steps and you can get some solution from these steps:
Submit an issue in the D7 issue queue.
Resolve the issue.
Submit a patch that the testbot is happy with.
Commit change to core.
Reference the change in the chronological log (the top portion of http://drupal.org/update/modules/6/7) and document the change in the bottom portion of the same page.
Cross-reference the change in the categorical page (http://drupal.org/node/394070). (New this year)
Add an issue to the Coder queue under the "Upgrade Routines" component.
Create a "placeholder" project for the API changes related to core.
Once a change is committed to core, add an issue to the API changes module with the details. This is identical to the current work flow except the information is posted in a different place.
Tag the issue based on Unstable release number and the categories it applies to (in the same way done on the categorical page).
Change the Coder Review and Upgrade flags as rules and routines are written.
Questions and clarifications about the change could be posted as comments on the issue. (This could significantly improve the post as with comments on the api.drupal.org site.)
If the change is later modified, reset the Coder Review and Upgrade flags to reflect this.
Use views to create the current chronological and categorical documentation pages from the individual issues. The chronological page will be limited to the log at the top of the current page, with each item linking to the individual issue page containing the details. This eliminates two of the current cross-reference steps (adding a Coder module issue and the categorical page item).