modman

This entry is about our IPS Community Suite 4.2 release.
Improving your SEO can be a complex undertaking with many different approaches but there are things that everyone knows are good practice and also more modern approaches to SEO that have changed since we first started developing IPS Community Suite. So it was time for a review and update.
Unfortunately no pretty screenshots on this one as this is all behind the scenes stuff but still quite useful to know . Also, some of this may sound a bit technical and dry but feel free to search some of these technologies if you are curious.
Move from HTML structured data to JSON-LD and enhance our existing markup with sensible additions. Calendar, blog, forum and pages (articles) data marked up for rich snippets. General review of our schema.org markup and enhance where appropriate. Use sitelinks search and other sensible markup such as the website and logo markup. Allow administrators to specify social profile links in the AdminCP which we then show links to in the footer and also make available in schema.org markup. Fix many duplicate page title issues. Review and ensure nofollow/noindex tags are used in appropriate areas. Add item tags as HTML meta tags Adding <link rel="next" value="next page url"> helps search engines know next/previous page.  
Nothing like a bulleted list of items to get you excited! But really these should be welcome improvements to all.
 

HTML Logic is our name for the additional tags available in IPS4's templates that allow runtime logic to be executed. It comprises if/then/else statements as well as loops and more.
Since HTML Logic has access to all of the underlying PHP framework in IPS4, it's very powerful and a lot can be achieved with it. One common use is to limit certain content within a template to particular member groups. Let's see how that might be done.
 
Showing or hiding content only to guests
We'll first look at a simpler idea: showing or hiding content specifically to guests (i.e. anyone who isn't logged in). Within IPS4, the \IPS\Member::loggedIn() object contains information about the current user. Guests always have a member_id of NULL (i.e. no value), so we can simply check that value in our logic tag:
{{if \IPS\Member::loggedIn()->member_id === NULL}} This content *only* shows to guests, since they have a NULL member_id. {{endif}} {{if \IPS\Member::loggedIn()->member_id}} This content *only* shows to logged-in users since their member_id is a number, which will equal true. {{endif}}  
Showing content only to specific groups
Let's go a bit further and this time show content to specific (primary) member groups. First, you need to get the IDs for the group(s) you want to deal with. You can find this by editing the group in the AdminCP, and making a note of the id parameter in the URL. On my installation, the Administrator group is ID 4 so we'll use that in our example.
Once again, we're using the \IPS\Member::loggedIn() object, but this time we're using the member_group_id property.
{{if \IPS\Member::loggedIn()->member_group_id === 4}} This content only shows to members in the "Administrators" group (ID 4 in our example) {{endif}}  
Working with multiple groups at once
Following the code above, you could simply repeat the check against \IPS\Member::loggedIn()->member_group_id several times, for each ID you want to allow. However, since our templates allow arbitrary PHP expressions to be used, there's a neater way: use an array of member group IDs you want to allow, and check against that using PHP's in_array function. Here's an example where we only show content to group IDs 2, 4 and 6:
{{if in_array( \IPS\Member::loggedIn()->member_group_id, array( 2, 4, 6 ) )}} This content only shows to members in groups with the ID 2, 4 or 6. {{endif}}  
Have a request for a theme tip? Let us know in the comments and we'll try and help out in a future tip!