Changes

Jump to navigation Jump to search
726 bytes removed ,  11:35, 24 August 2012
no edit summary
Line 5: Line 5:  
[[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). -->
 
[[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). -->
 
</noinclude>
 
</noinclude>
  −
'''Comments and Explanations:'''
  −
  −
There are comments (in italic) providing guidance to fill out each section, see also the [[Features/Policy|Feature Policy Page]] for a more detailed explanation of the new-feature process. '''Copy the source to a ''new page'' named Features/''Your Feature Name'' before making changes!  DO NOT EDIT THIS TEMPLATE.'''
      
<!-- All fields on this form are required to be accepted.
 
<!-- All fields on this form are required to be accepted.
Line 87: Line 83:  
{{:{{PAGENAME}}/Testing}}
 
{{:{{PAGENAME}}/Testing}}
 
== User Experience ==
 
== User Experience ==
''If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice.''
+
''This feature will bring noticeable change in their Sugar environment. This activity will allow users to create,learn and explore HTML,JavaScript and Web Development.
   −
== Dependencies ==
  −
''What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time?  Other upstream projects like Python?''
      
== Contingency Plan ==
 
== Contingency Plan ==

Navigation menu