Opened on 12/13/2016 at 04:44:56 PM

Last modified on 10/09/2019 at 06:32:01 PM

#4730 new change

Document the variable naming pattern for website project

Reported by: saroyanm Assignee:
Priority: Unknown Milestone:
Module: Websites Keywords:
Cc: juliandoucette, lisabielik, Shikitita Blocked By:
Blocking: Platform: Unknown / Cross platform
Ready: no Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

Description (last modified by saroyanm)

Background

We do deal with a huge load of translation variables and letting developers/content developers make sense for each single string take huge amount of time.

What to change

Document the variable naming convention pattern.

[heading]-[tag]-[unordered increasing numeration]

Example HTML:

<h2>
  {{ios-support[Title of section] iOS support}}
</h2>
<ul>
  <li>{{ios-support-list[iOS support list item] Installing Adblock Browser for iOS}}</li>
  <li>{{ios-support-list1[iOS support list item] Adding a filter list}}</li>
  <li>{{ios-support-list4[iOS support list item] Removing a filter list}}</li>
  <li>{{ios-support-list3[iOS support list item] Configuring Acceptable Ads}}</li>
  <li>{{ios-support-list5[iOS support list item] Changing the default search engine}}</li>
</ul>

Temporary Note

  • this is being currently used without documentation

Attachments (0)

Change History (2)

comment:1 Changed on 12/13/2016 at 05:04:23 PM by saroyanm

  • Cc juliandoucette lisabielik Shikitita added
  • Description modified (diff)

We also need to find place where this needs to be documented, current suggestions:

comment:2 Changed on 10/09/2019 at 06:32:01 PM by greiner

  • Component changed from Unknown to Websites

Add Comment

Modify Ticket

Change Properties
Action
as new .
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from (none).
Next status will be 'reviewing'.
 
Note: See TracTickets for help on using tickets.