How I stopped worrying and learned to leave social media: Why focusing on self-care is what we need to move forward after 2024.

It derives its name from Alexandria where it resided for a number of years before it brought by the Eastern Orthodox Patriarch Cyril Lucaris from Alexandria to Constantinople. Then it was given to Charles I of England in the 17th century. Until the later purchase of the Codex Sinaiticus, it was the best manuscript of the Greek Bible deposited in Britain. Today, it rests along with Codex Sinaiticus in one of the showcases in the Ritblat Gallery of the British Library. As the text came from several different traditions, different parts of the codex are not of equal textual value. The text has been edited several times since the 18th century.

This week we read Revelation 10, by which we are taught both how God has revealed Himself clearly in Jesus, and also how there remain mysteries that we cannot fathom. We read this chapter in the light of Ezekiel 3:1-3 and Daniel 9-12, learning that the new covenant brings us a new intimacy with God, but also calls for patience as we await God’s completion of His work.

Dean The Very Rev. Dr. John Behr, author of academic, popular, and spiritual works, presented the keynote address at this year's Education Day at St. Vladimir's Seminary. Fr. John highlighted the symbiotic relationship between Christianity and books, and described how the development of the internet has changed the way people read.

This tutorial shows how to change website scroll speed in Wordpress.

The post WordPress. How to change website scroll speed appeared first on Template Monster Help.

By Craig McPherson, freelance writer.

Think of this. You've got a serious deadline to cover and are working on it. After one hour of work, you turn back to social media for a "state of relaxation". But guess what? You keep on scrolling your favourite social media platform for hours and end up missing the deadline. Sounds familiar, right?

Creating an infinite horizontal logo scroll effect with pure CSS is a simple yet powerful way to add dynamic movement to a website. This tutorial will walk you through building an infinite scroll effect with added hover effects that allow the user to pause scrolling and scale each logo slightly when hovered.

A design pattern that is currently growing more popular is the fixed position bar at the top of the page. Sometimes the bar stays the same throughout, sometimes the header morphs into a slimmer bar as you scroll down, sometimes a completely new bar appears.

For example, as you scroll down on the New York Times website, the top navigation bar shifts from displaying typical site-wide navigation to article specific controls, showing the title of the article, the share link, the comments link, as well as compressed site-wide links:

At the Forbes website, as the user scrolls down the page a fixed position bar appears at the top promoting links to other articles the reader may find interesting, as well as a drop-down site navigation menu, search and user controls:

While these bars may be useful, they take up vertical space, reducing the reading space the user has chosen for themselves by picking the size of their browser window. Additionally, information displayed on these bars does not do anything to aid the reading of the actual content, making the bar more of a nuisance than help.

An interesting way to solve the issue is to hide the bar when scrolling down, and show it when scrolling up. On mobile interfaces, where space is precious, this technique is used to hide chrome, such as Web browser controls, but it’s also a good pattern to use on the Web. For example, Medium has just updated their new navigation bar. As you scroll down, the bar goes away, but it can be revealed at any time by scrolling up. Here’s what it looks like:

Less annoying than bars that just sit there as you scroll down, and makes the menu easy to access without having to scroll up to the top of the page. Scrolling up won’t necessarily mean the user wants the navigation – they may just be scanning the content – but 100% of the people wanting the navigation will be scrolling up, making it a pretty good compromise.

Update 2014-06-16

For anyone interested in using this design pattern on their own sites, Eduardo Martins Barbosa has created a jQuery plugin that performs much the same way as the bar on Medium, including the subtle effect of revealing the bar at the scrolling speed of the user rather than simply sliding it down upon scrolling up.

Want to enable scroll tracking on your WordPress website? You can easily find out how far a user scrolls down on each post. This lets you know the exact section in which they lose interest and abandon your site. With this data, you can modify that specific section and make it interesting enough to engage […]

The post How to Enable Scroll Tracking in WordPress With Google Analytics first appeared on IsItWP - Free WordPress Theme Detector.

Do you have "screen apnea"? Our special series Body Electric continues with former Microsoft executive Linda Stone who coined the term. Around 2007, Linda noticed she had an unhealthy habit while answering emails: she held her breath. On this episode, she tells host Manoush Zomorodi how she tested her friends and colleagues for "screen apnea" and what she's done since.

Then, Manoush talks to the bestselling author of Breath, science writer James Nestor, who explains how shallow breathing impacts our physical and mental health. He takes us through a simple exercise to 'reset' our breath and relieve screen time stress.

Binge the whole Body Electric series here.

Sign up for the Body Electric Challenge and our newsletter here.

Talk to us on Instagram @ManoushZ, or record a voice memo and email it to us at BodyElectric@npr.org.

Learn more about sponsor message choices: podcastchoices.com/adchoices

NPR Privacy Policy

One of the most challenging aspects of reading from a teleprompter has always been speed control. Unless you get the speed just right, you either have to rush or slow down your narration, and either adjustment adds stress to your delivery that can force a glitch and another retake. Fortunately, Elgato has two hardware options you can use to control scrolling speed; the Stream Deck+ ($199.99) and Stream Deck Pedal ($89.99). Elgato was kind enough to send both options for me to try, and I'll briefly recount my experience here.

Mute Steve Kornacki, unclench your jaw, and scroll through these sweet scenes from Sea-Meow. by Megan Seling

Photos by Madison Kirkman

Sea-Meow, which bills itself as Washington’s largest cat convention, invaded Seattle Center’s Exhibition Hall over the weekend and brought with it appearances from the Two Crazy Cat Ladies, Moshow the Cat Rapper, and Christopher Watson aka the Catluminati, as well as a cat costume contest, a cat-calling contest, cat bingo, and dozens of vendors slinging everything from cat beds to catnip to cat coffee. (That is, cat-themed coffee that benefits cat rescues and not, like, coffee for cats.)

But most importantly, there were cats. So many cats. Old cats, young cats, kitten cats. Cats available for adoption, cats available for snuggles, and cats being pushed, carried, and cradled in backpacks and strollers and those bags with little clear bubble cutouts that make them look like grumpy-faced astronauts. 

Election results won’t be in for several hours, and even then, it may take days to know who won. So close Twitter (what are you still doing on that hell site anyway???), mute Steve Kornacki, unclench your jaw, and scroll through these sweet scenes from Sea-Meow.

Madison Kirkman Madison Kirkman Madison Kirkman Madison Kirkman Madison Kirkman Madison Kirkman Madison Kirkman Madison Kirkman Madison Kirkman Madison Kirkman Madison Kirkman Madison Kirkman Madison Kirkman Madison Kirkman Madison Kirkman Madison Kirkman

When Mount Vesuvius erupted in 79 C.E., it covered the ancient cities of Pompeii and Herculaneum under tons of ash. Millennia later, in the mid-18th century, archeologists began to unearth the city, including its famed libraries, but the scrolls they found were too fragile to be unrolled and read; their contents were thought to be lost forever. Only now, thanks to the advent of artificial intelligence and machine learning, scholars of the ancient world have partnered with computer programmers to unlock the contents of these priceless documents. In this episode of “There’s More to That,” science journalist and Smithsonian contributor Jo Marchant tells us about the yearslong campaign to read these scrolls. And Youssef Nader—one of the three winners of last year’s “Vesuvius Challenge” to make these clumps of vulcanized ash readable—tells us how he and his teammates achieved their historic breakthrough. Read Smithsonian’s coverage of the Vesuvius Challenge and the Herculaneum scrolls here (https://www.smithsonianmag.com/smart-news/three-students-decipher-first-passages-2000-year-old-scroll-burned-vesuvius-eruption-180983738/) , here (https://www.smithsonianmag.com/history/buried-ash-vesuvius-scrolls-are-being-read-new-xray-technique-180969358/) , and here (https://www.smithsonianmag.com/history/archaeologoists-only-just-beginning-reveal-secrets-hidden-ancient-manuscripts-180967455/) . Find prior episodes of our show here (https://www.smithsonianmag.com/podcast/) . There’s More to That is a production of Smithsonian magazine and PRX Productions. From the magazine, our team is Chris Klimek, Debra Rosenberg and Brian Wolly. From PRX, our team is Jessica Miller, Adriana Rosas Rivera, Genevieve Sponsler, Rye Dorsey, and Edwin Ochoa. The Executive Producer of PRX Productions is Jocelyn Gonzales. Fact-checking by Stephanie Abramson. Episode artwork by Emily Lankiewicz. Music by APM Music.

A Greek philosopher’s musings on pleasure, contained in ancient papyrus scrolls buried by Mount Vesuvius’s eruption 2000 years ago, have been rediscovered with the help of AI

3D mapping and artificial intelligence has helped decipher an ancient Herculaneum papyrus scroll which had been digitally scanned

The Elder Scrolls: Legends, the free-to-play card game set in Bethesda's fantasy world, has been removed from sale on Steam. Its servers will shut down for good on January 30th, 2025, after which it will no longer be playable. The closure comes five years after the game was last updated.

Read more

Canadians are watching the U.S. election results with trepidation, knowing they have no control over the outcome that will still affect them. Polling shows Vice-President Kamala Harris and former president Donald Trump are neck-and-neck. 

Need a break from your electronic devices? An increasing number of millenials and the Gen Z are now taking to fun, crafty hobbies which include knitting, crochet, and tufting

Paul Lewis did an interesting article a while back about avoiding unnecessary paints through disabling hover effects as the user scrolls, which is a great approach. The down side being managing all your hover states through a parent class. UPDATE: I’ve done a follow up article which demonstrates a more robust technique. .hover .element:hover { … Continue reading "60fps scrolling using pointer-events: none"

60fps scrolling article got quite a few people excited but also a few smart people to point out some flaws in the approach. I was planning to just update the original article but I’ve compiled so much info about this topic that I thought it would be better to do a follow up article and … Continue reading "A follow up to obtaining 60fps scrolling performance"

The most significant user interface change from iOS 17 to iOS 18 are the navigation differences in Apple's Photos app. The ubiquitous tab bar that's became the default navigation model in mobile apps is gone and in its place is one long scrolling page. So how does it work and why?

Most mobile applications have adopted a bottom bar for primary navigation controls. On Android it's called bottom navigation and on iOS, a tab bar, but the purpose is the same: make the top-level sections of an application visible and let people move between them.

And it works. Across multiple studies and experiments, companies found when critical parts of an application are made more visible, usage of them increases. For example, Facebook saw that not only did engagement go up when they moved from a “hamburger” menu to a bottom tab bar in their iOS app, but several other important metrics went up as well. Results like this made use of tab bars grow.

But in iOS 18, Apple removed the tab bar in their Photos app. Whereas the prior version had visible tabs for the top-level sections (Library, For You, Albums, Search), the redesign is just a single scroll view. The features previously found in each tab are now accessed by scrolling up and down vs. switching between tabs. One notable exception is Search which stays anchored at the top of the screen.

In addition to the persistent Search button, there's also a Select action and user profile image that opens a sheet with account settings. As you scroll up into your Photo library a persistent set of View controls appears at the bottom of the screen as well. The Close action scrolls you to the end of your Photo library and reveals a bit of the actions below making the location of features previously found in tabs more clear.

It's certainly a big change and given the effectiveness of tab bars, its also a change that has people questioning why? I have no inside information on Apple's decision-making process here but based on what I've learned about how people use Google Photos, Yahoo! Photos, and Flickr, I can speculate.

1. By far the dominant use of a Photo gallery is scrolling to find an image whether to share, view, or just browse.
2. Very few people organize their photo libraries and those that do, do it rarely.
3. People continue to have poor experiences with searching images, despite lots of improvements, so they default to browsing when trying to find photos.
4. Most automatic curation features like those found in For You just get ignored.

All that together can easily get you to the design answer of "the app should just be a scrolling list of all your Photos". Of course there's trade-offs. The top-level sections, and their features are much less visible, and thereby less obvious. The people who do make use of features like Albums and Memories now need to scroll to them vs. tapping once. But as iOS18 rolls out to everyone in the Fall, we'll see if these trade-offs were worth it.

The exhibition, organised by the Kolkata Centre for Creativity along with the Kerala Lalithakala Akademi and Gallery Rasa, pays tribute to artist Benode Behari Mukherjee, one of the pioneers of Indian modern art

There’s bunches of plugins, extensions and techniques to smoothly scroll page elements, but most of them are convoluted messes and probably do more than you need. I like “small and works well”, and it’s a good exercise for those JavaScript and DOM muscles to write a small plugin from time to time. My goal was […]

Michelle Barker appears as one of a heavenly host, coming forth with scroll in hand to pronounce an end to janky scrolljacking! Unto us a new specification is born, in the city of TimBL, and its name shall be called Scroll Snap.

---

Sponsor: Order any Standard paperback(s) and get a surprise gift card in the box for YOU. While supplies last, from your pals at A Book Apart!

---

One area where the web has traditionally lagged behind native platforms is the perceived “slickness” of the app experience. In part, this perception comes from the way the UI responds to user interactions – including the act of scrolling through content.

Faced with the limitations of the web platform, developers frequently reach for JavaScript libraries and frameworks to alter the experience of scrolling a web page – sometimes called “scroll-jacking” – not always a good thing if implemented without due consideration of the user experience. More libraries can also lead to page bloat, and drag down a site’s performance. But with the relatively new CSS Scroll Snap specification, we have the ability to control the scrolling behaviour of a web page (to a degree) using web standards – without resorting to heavy libraries. Let’s take a look at how.

Scroll Snap

A user can control the scroll position of a web page in a number of ways, such as using a mouse, touch gesture or arrow keys. In contrast to a linear scrolling experience, where the rate of scroll reflects the rate of the controller, the Scroll Snap specification enables a web page to snap to specific points as the user scrolls. For this, we need a fixed-height element to act as the scroll container, and the direct children of that element will determine the snap points. To demonstrate this, here is some example HTML, which consists of a <div> containing four <section> elements:

<div class="scroll-container">
  <section>
    <h2>Section 1</h2>
  </section>
  <section>
    <h2>Section 2</h2>
  </section>
  <section>
    <h2>Section 3</h2>
  </section>
  <section>
    <h2>Section 4</h2>
  </section>
</div>

Scroll snapping requires the presence of two main CSS properties: scroll-snap-type and scroll-snap-align. scroll-snap-type applies to the scroll container element, and takes two keyword values. It tells the browser:

• The direction to snap
• Whether snapping is mandatory

scroll-snap-align is applied to the child elements – in this case our <section>s.

We also need to set a fixed height on the scroll container, and set the relevant overflow property to scroll.

.scroll-container {
  height: 100vh;
  overflow-y: scroll;
  scroll-snap-type: y mandatory;
}

section {
  height: 100vh;
  scroll-snap-align: center;
}

In the above example, I’m setting the direction in the scroll-snap-type property to y to specify vertical snapping. The second value specifies that snapping is mandatory. This means that when the user stops scrolling their scroll position will always snap to the nearest snap point. The alternative value is proximity, which determines that the user’s scroll position will be snapped only if they stop scrolling in the proximity of a snap point. (It’s down to the browser to determine what it considers to be the proximity threshold.)

If you have content of indeterminate length, which might feasibly be larger than the height of the scroll container (in this case 100vh), then using a value of mandatory can cause some content to be hidden above or below the visible area, so is not recommended. But if you know that your content will always fit within the viewport, then mandatory can produce a more consistent user experience.

See the Pen Simple scroll-snap example by Michelle Barker (@michellebarker) on CodePen.

In this example I’m setting both the scroll container and each of the sections to a height of 100vh, which affects the scroll experience of the entire web page. But scroll snapping can also be implemented on smaller components too. Setting scroll snapping on the x-axis (or inline axis) can produce something like a carousel effect.

In this demo, you can scroll horizontally scroll through the sections:

See the Pen Carousel-style scroll-snap example by Michelle Barker (@michellebarker) on CodePen.

The Intersection Observer API

By implementing the CSS above, our web page already has a more native-like feel to it. To improve upon this further we could add some scroll-based transitions and animations. We’ll need to employ a bit of Javascript for this, using the Intersection Observer API. This allows us to create an observer that watches for elements intersecting with the viewport, triggering a callback function when this occurs. It is more efficient than libraries that rely on continuously listening for scroll events.

We can create an observer that watches for each of our scroll sections coming in and out of view:

const sections = [...document.querySelectorAll('section')]

const options = {
  rootMargin: '0px',
  threshold: 0.25
}

const callback = (entries) => {
  entries.forEach((entry) => {
    if (entry.intersectionRatio >= 0.25) {
      target.classList.add("is-visible");
    } else {
      target.classList.remove("is-visible");
    }
  })
}

const observer = new IntersectionObserver(callback, options)

sections.forEach((section, index) => {
  observer.observe(section)
})

In this example, a callback function is triggered whenever one of our sections intersects the container by 25% (using the threshold option). The callback adds a class of is-visible to the section if it is at least 25% in view when the intersection occurs (which will take effect when the element is coming into view), and removes it otherwise (when the element is moving out of view). Then we can add some CSS to transition in the content for each of those sections:

section .content {
  opacity: 0:
}

section.is-visible .content {
  opacity: 1;
  transition: opacity 1000ms:
}

This demo shows it in action:

See the Pen Scrolling with Intersection Observer by Michelle Barker (@michellebarker) on CodePen.

You could, of course, implement some much more fancy transition and animation effects in CSS or JS!

As an aside, it’s worth pointing out that, in practice, we shouldn’t be setting opacity: 0 as the default without considering the experience if JavaScript fails to load. In this case, the user would see no content at all! There are different ways to handle this: We could add a .no-js class to the body (which we remove on load with JS), and set default styles on it, or we could set the initial style (before transition) with JS instead of CSS.

Position: sticky

There’s one more CSS property that I think has the potential to aid the scroll experience, and that’s the position property. Unlike position: fixed, which locks the position of an element relative to the nearest relative ancestor and doesn’t change, position: sticky is more like a temporary lock. An element with a position value of sticky will become fixed only until it reaches the threshold of its parent, at which point it resumes relative positioning.

By “sticking” some elements within scroll sections we can give the impression of them being tied to the action of scrolling between sections. It’s pretty cool that we can instruct an element to respond to it’s position within a container with CSS alone!

Browser support and fallbacks

The scroll-snap-type and scroll-snap-align properties are fairly well-supported. The former requires a prefix for Edge and IE, and older versions of Safari do not support axis values. In newer versions of Safari it works quite well. Intersection Observer similarly has a good level of support, with the exception of IE.

By wrapping our scroll-related code in a feature query we can provide a regular scrolling experience as a fallback for users of older browsers, where accessing the content is most important. Browsers that do not support scroll-snap-type with an axis value would simply scroll as normal.

@supports (scroll-snap-type: y mandatory) {
  .scroll-container {
    height: 100vh;
    overflow-y: scroll;
    scroll-snap-type: y mandatory;
  }

  section {
    height: 100vh;
    scroll-snap-align: center;
  }
}

The above code would exclude MS Edge and IE, as they don’t support axis values. If you wanted to support them you could do so using a vendor prefix, and using @supports (scroll-snap-type: mandatory) instead.

Putting it all together

This demo combines all three of the effects discussed in this article.

Summary

Spending time on scroll-based styling might seem silly or frivolous to some. But I believe it’s an important part of positioning the web as a viable alternative to native applications, keeping it open and accessible. While these new CSS features don’t offer all of the control we might expect with a fully featured JS library, they have a major advantage: simplicity and reliability. By utilising web standards where possible, we can have the best of both worlds: Slick and eye-catching sites that satisfy clients’ expectations, with the added benefit of better performance for users.

---

About the author

Michelle is a Lead Front End Developer at Bristol web agency Atomic Smash, author of front-end blog CSS { In Real Life }, and a Mozilla Tech Speaker. She has written articles for CSS Tricks, Smashing Magazine, and Web Designer Magazine, to name a few. She enjoys experimenting with new CSS features and helping others learn about them.

More articles by Michelle

I’m utterly behind in learning about scroll-driven animations apart from the “reading progress bar” experiments all over CodePen. Well, I’m not exactly “green” on the topic; we’ve published a handful of articles on it including this neat-o one by Lee …

---

Unleash the Power of Scroll-Driven Animations originally published on CSS-Tricks, which is part of the DigitalOcean family. You should get the newsletter.

Full Article