[ 
https://issues.apache.org/jira/browse/CB-10353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15158163#comment-15158163
 ] 

ASF GitHub Bot commented on CB-10353:
-------------------------------------

Github user dblotsky commented on a diff in the pull request:

    https://github.com/apache/cordova-docs/pull/489#discussion_r53728075
  
    --- Diff: www/static/css-src/_docs.scss ---
    @@ -204,6 +204,23 @@
             }
         }
     
    +    .hooks {
    +        td[data-col="description"] {
    +            text-align: left;
    +            vertical-align: middle;
    +        }
    +
    +        td[rowspan="2"], th[colspan="3"], td[data-col="code"] {
    +            text-align: center;
    +            vertical-align: middle;
    +        }
    +
    +        td[data-col="description"] {
    --- End diff --
    
    These should be classes instead of content-specific selectors. Sorry I 
missed this before this got merged.


> Make Hooks guide a reference
> ----------------------------
>
>                 Key: CB-10353
>                 URL: https://issues.apache.org/jira/browse/CB-10353
>             Project: Apache Cordova
>          Issue Type: Task
>          Components: Docs
>            Reporter: Raghav
>            Assignee: Sarangan Rajamanickam
>              Labels: Docs-6.x
>
> Hooks guide 
> (https://cordova.apache.org/docs/en/latest/guide/appdev/hooks/index.html) 
> needs to be modified as per the reference structure. 
> General guidelines:
> - While giving examples, keep them short. Do not repeat for all 
> plugins/platforms.
> - Remove all references to cordova plugin registry.
> - Remove Tizen references. The platform is deprecated 
> (http://markmail.org/message/hryg6sjswecpgndu)
> - Keep information up to date for the platforms, CLI and plugins



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to