Search Results for 'block'

Perfect! Thanks. The homepage links work now.

BUT…. what if we want to make it a little more customized? Like this…

1. The share links on the homepage (Twitter & FB) should add UTM params – https://share.america.gov/?utm_source=shareamerica&utm_medium=homepage&utm_campaign=list — replace “https://share.america.gov/” with the full URL of the article and put today’s date in there too

2. The share links on the individual post for the similar articles (Twitter & FB) should add UTM params – https://share.america.gov/?utm_source=shareamerica&utm_medium=postpage&utm_campaign=similararticles-YYYY-MM-DD : replace “https://share.america.gov/” with the full URL of the article

3. The share links on the individual post for top share buttons (Twitter & FB) should add UTM params – https://share.america.gov/?utm_source=shareamerica&utm_medium=postpage&utm_campaign=sharetop-YYYY-MM-DD : replace “https://share.america.gov/” with the full URL of the article

4. The share links on the individual post for botom share buttons (Twitter & FB) should add UTM params – https://share.america.gov/?utm_source=shareamerica&utm_medium=postpage&utm_campaign=sharebottom — replace “https://share.america.gov/” with the full URL of the article

Can this be done?

Thanks,
David

Hi Lucian,

Thanks for getting back to me.

Yep I want to do it through CSS so it effects the

element. I’m having trouble though. Surely…

blockquote { text-align: left; }

…should work (when inserted in the child theme’s stye.css), but it doesn’t. Any thoughts?

Cheers.

Hi Lucian,

I recognized that category links are empty. Links go to /#.

Can you please send a new code for module 8?

Any word on this, mehedi?

P.S. Looking at your live site again, minor CSS tweak suggestion:

.auhtor-twitter a {
  display: block;
}

This may not be necessary but it just drives me crazy when there’s a small spot you can’t click between the icon and the text 😀

So, one aspect of “responsive” design (good and bad), is that it’s better to load a 25kb image once than load the 25kb image once and the 12kb image together and switch those out on viewport. Better to load the 25kb image ONCE, then resize to fit the aspect you’re looking at when you look at it.

I agree it’s best to load the image only once. All I’m saying (and is what I believe Google Pagespeed is saying) is that we should request the version of the image that is best fit to the screen at it’s current orientation, and then if the device changes the viewport, the image will be resized locally, which is essentially what newspaper does now at a certain level.

For example, if I load my homepage and resize the browser window down to 767 pixels, I see this image which is only 326px wide being displayed at over 700 px wide WITHOUT reloading the image, as seen in the screenshot below, second image down:

Does that make sense? If someone really was bothered by the pixelated images, they’d probably realize that they could simply re-orient their device to how they loaded the page or simply reload the page. It seems terribly inefficient to me to have every single person download a high-resolution image on the off-chance that they will flip from portrait to landscape while viewing the page…

The other benefit of using the larger image is for retina/HD displays on a mobile device which have higher pixel count than desktop; so again, if you do the pixel math, a 700×500 image on a screen with double the pixel count, loaded half size, would still provide the same number of pixels when shown half size — without having to load alternate retina/HD version of image or use “image stacks.”

I agree, it does look nice on “Retina” phone screens, which is why I disabled my retina plugin on mobile devices. I think it would simply be a better solution to have Newspaper serve a 300 px wide image, and then allow the retina plugin to substitute the @2x version, rather than serving everyone the hi-res image.

Doesn’t that seem more efficient?

This is actually one of the cool things about mod_pagespeed … if you have an image loading over and over at 80% size, it will cache the image at THAT SIZE and serve up the smaller image to people who keep requesting it vs loading the larger image and scaling it.

So let’s say an iPhone is requesting that 745 pixel wide image, with mod_pagespeed, it will know that the iPhone can only display a 640 px wide image and then serve it a new thumbnail?

That’s pretty cool if true. Thanks!

Lucian,

One thing you might want to take a look at is Block 10. The output on my site is the shortcode instead of the block (and someone mentioned a similar problem above).

No big deal for me though, just changed to a different block!

Thanks!

Hi Lucian,

We finally lifted the password off the site and made it public today… https://share.america.gov/

As we discussed before… The facebook “Share This” link is still not working on the homepage. But, it works great on all internal pages. We are still using the td_module_6.php file.

Please help!

Thanks
David

I fixed it… thank you very much 🙂

Ok, in the first case using css can you tell me how to add different background for two block 4 (like the first one is green and second is blue), i try to do that but it always change colour to every block 4 on my homepage :/

Now I changed block on the website, but is only a temporary solution.

I’m still waiting for your answer.

Thanks