WordPress.org
Get WordPress

Plugin Directory

Changeset 1770972


Ignore:
Timestamp:
11/19/2017 08:46:38 PM (8 years ago)
Author:
giannisg
Message:

Small changes in the readme.txt

File:
1 edited

Legend:

Unmodified
Added
Removed

  • css-page-ancestors/trunk/readme.txt

    r1770956 r1770972  
    1212
    1313== Description ==
    14 Please, keep in mind that THIS IS IN BETA.
     14*Please, keep in mind that THIS IS IN BETA. I'm relying to your feedback, positive or with suggestions, to release it out of beta*
    1515
    1616This plugin will give you the extra class you need in your <body>  tag of ALL (and not just one) of the anchestors of a page in Wordpress.
    … …  
    3232* Contact
    3333
    34 Let's see this scenario: You want all the pages under 'Clients' to have a red background. Now, it's easy to do that - but only for the 'Web', and 'Print' pages because Wordpress gives you only the fathers in the body classes - in this case, the id of 'Clients'. 'Eshops' and 'Portfolio' can also have a red background, but you will have to add a new class in your css with the id of 'Web' at your css. And, if you add pages under 'Eshops', same thing, you will have to add a new class in your css file with the id of 'Eshops' page. And, all this is easy if you do it yurself - but if you handle the site to an editor, that knows only to create content - you will have to add the class in the CSS every time someone adds a level to all this.
     34Let's see this scenario: You want all the pages under 'Clients' to have a red background. Now, it's easy to do that - but only for the 'Web', and 'Print' pages because Wordpress gives you only the fathers in the body classes - in this case, the id of 'Clients'. 'Eshops' and 'Portfolio' can also have a red background, but you will have to add a new class in your css with the id of 'Web' at your css. And, if you add pages under 'Eshops', same thing, you will have to add a new class in your css file with the id of 'Eshops' page. So, all this is easy if you do it yourself - but if you handle the site to an editor, that knows only to create content - you will have to add the class in the CSS every time someone adds a level to all this.
    3535
    36 Whith this plugin all the ancestors will be in your body as class names - as a slug, and as an id. And you want all the pages under 'Clients' to have a red background you just add to your css .achestor-clients {background:red;} in your css,  and you are done - no matter the level the final page is under. 
     36Whith this plugin **all the ancestors of a page, no matter the depth** will be *in your body as class names* - as a slug, and as an id. And you want all the pages under 'Clients' to have a red background you just add to your css .achestor-clients {background:red;} in your css,  and you are done - no matter the level the final page is under. 
    3737
    38 Also, the  order is with top ancestor first (in our example, Portfolio page will have "ancestor-clients ancestor-web") - this way, it's simpler in CSS to overwrite the -clients class with the -web attributes.
     38Finaly, the  order is with top ancestor first (in our example, Portfolio page will have "ancestor-clients ancestor-web") - this way, it's simpler in CSS to overwrite the -clients class with the -web attributes.
    3939
    4040There is no writing on the database, or other change on the site, so, even if something goes wrong, just de-activate the plugin, and you'll be fine.
Note: See TracChangeset for help on using the changeset viewer.