When blogging recipes, how can I support both readers who want the narrative/journey and ones who want the printer-friendly recipe?

You can put your content into a <div id="recipeXYZ"> nested normally within your blog post. Then you can load the content to a print page dynamically. Now you can print from your original page, with its images and story, or from your print page, which is more printer friendly. You can also modify your recipe from one central location and have it update both pages as they both always receive their content from the same source.

To generate the print page just add the button:

<span id="printPreview">printer friendly version (requires javascript)</span>

$("#printPreview").click(function(){
    var w = window.open(); // you can change the dimenstions of the window here.
    w.document.open().write("#recipeXYZ");
    // you probably want to create the actual print button here.
});

posted over 5 years ago

CC BY-SA 3.0

AGirlHasNoName‭

135 reputation 27 11 20 0

WordPress Answer

If you're using WordPress, I've got really good news for you. The example that you provided is using a WordPress plugin: https://wordpress.org/plugins/easyrecipe/

Adding a recipe and getting the Recipe View microdata correct is not only time consuming but it’s also pretty geeky and most cooks prefer to cook and share, not code webpages.

Enter EasyRecipe.

Non-Wordpress Answer

If you are not using Wordpress I would give you 3 suggestions

1. If I was blogging recipes, what I would do is that I would create a separate pdf of the easy view and just link to it. While that doesn't synchronize, that's what I would do.

2. If you really want an html page instead of a pdf, You can create a separate blog. And the "Image and wordy" blog can reference the "easy" recipe blog.

3. Finally, if neither of those work because you REALLY want the data synced, I would use the other answers already given to use the @media print styling.

posted over 5 years ago

CC BY-SA 3.0

Dustin‭

15 reputation 0 3 3 0

You use @media rules in your CSS style sheets to define which html tags you want to print and which are only visible on screen. E.g.

@media print {
    .stuff-you-don't-want-to-print {
        display: none;
    }
}

To print the current browser window, you print it with JavaScript, e.g.

<a href="javascript:window.print()">Print</a>

The page you link to actually provides a separate web page to print. You can see that the URL of the page you print is different than the URL of the blog post. And if you look at the source code the pages are different. So in fact your "example" is an example of what you don't want, when you say that "[you] don't want to have to create the content twice". That page has created the content twice.

If you don't want to create the content twice, use media queries.

posted over 5 years ago

CC BY-SA 3.0

System‭

3226 reputation 147 215 553 0

disclaimer: I'm not, in anyway, associated with the printfriendly company.

I found the printfriendly plugin pretty useful and easy to implement. It is a small script you can add to your website and it displays a print (and an optional pdf/mail) button.

https://www.printfriendly.com/about

quote form their website:
PrintFriendly cleans and formats web pages for perfect print experience. PrintFriendly removes ads, navigation and web page junk, so you save paper and ink when you print. It's free and easy to use. Perfect to use at home, the office, or whenever you need to print a web page.

I created a (quick and dirty, sorry for that) test page where I included this script:

Here we see the test page with the included printfriendly button:




Here is the page setup dialog which appears after one clicked the print button. You are able to delete various parts of the page you want to print:




This is the output pdf generated by the script:




Of course, everybody should check if this works on his website and if all data protection stuff is okay for his needs.

For me, the advantage of this solution is that you don't need to manage two versions of the content or mess around with more or less difficult CSS.

A potential downside could be GDPR related issues in the free version. There is also a payed version which claims to be GDPR compliant.

posted over 5 years ago

CC BY-SA 3.0

undefined‭

5 reputation 0 1 1 0

CSS supports media queries since Level 2, Revision 1. That's from way back in 2011, so any modern web browser should support it.

If you're able to specify custom CSS, and apply custom CSS classes to your content, then you can define a CSS class such that the pictures and other ancilliary content is shown on screen, but only the actual recipe is printed on paper.

This way, you don't need to have a separate "printer friendly" page, because you're using CSS to define what "printer friendly" means for your particular content. Of course, it assumes that you have control over the CSS in the first place! The person visiting your web site just prints via their browser's normal "print" function.

Specifically, as discussed on MDN, you can either target print media, or a specific characteristic of a media (a feature). For the former, you'd add something like

@media print {
    img.food-photo { display: none; }
    body { color: black; }
}

to hide food-photo class imgs and set the text color to black when the rendering media is identified as print.

For the latter, you can target non-color-capable media (whether screen, print, or otherwise) by writing something like

@media not color /* untested, but looks like it should work */ {
    body { color: black; }
}

to set the text color to black where color is not supported.

These can be combined to form even more complex rules, and of course the normal CSS inheritance rules apply as well, so you can override only those attributes that need to be different between, say, print and non-print.

You might also be interested in CSS feature queries, which look to be similar but geared toward even more specific feature support; for example, one example shows how to apply specific CSS depending on whether display: flex is supported. This looks more useful for when you want to know that the user agent (browser) supports a feature, than for targetting specific media types or capabilities.

I came across a Stack Overflow question at What does @media screen and (max-width: 1024px) mean in CSS? which has some more complex examples that you may find enlightening.

I think that the biggest downside to using CSS for this is that it leaves the visitor with no easy way to print the whole page including the "narrative/journey" if that's what they want to do. There are tricks that one can use, but those by their very nature are rather technical.

posted over 5 years ago

CC BY-SA 4.0

Canina‭

485 reputation 10 40 74 49

In a lot of ways, quests on online games like RuneScape are very much like recipes. I think you could take a page out of their book. Compare the following two pages:

https://oldschool.runescape.wiki/w/Dragon_Slayer https://oldschool.runescape.wiki/w/Dragon_Slayer/Quick_guide

At the top of each is a snippet that explains that there is a quick guide, or if you're on the quick guide and want the fuller description, that that exists as well. I think this paradigm would work very well for the recipes.

One potential issue here is that you have to essentially maintain two separate articles. But one of them, by definition, is pretty slimmed down, so it shouldn't be too much of an issue. I know this is something you specifically said you didn't want, but I wanted to throw it out there as a form of "When this problem came up, here's a solution for it in the wild that seems to actually work well."

posted over 5 years ago

CC BY-SA 3.0

corsiKa‭

15 reputation 0 3 3 0