<p>How to super imposing a image with text and using that image as twitter tweet with copyright text</p>


Super imposing a image with text and using that image as twitter tweet

<p>The highlighted features of <a href="https://nextjs.org/" target="_blank" rel="noopener">Next.js</a> mentioned on their <a href="https://nextjs.org/blog" target="_blank" rel="noopener">website</a> were the main reason to move to Next.js.</p>
<p>As a newbie to react I had started the journey with CRA(Create React App), which isn&#8217;t a bad option at all but for a bigger vision you cannot rely on CRA due to various reasons like it&#8217;s di<span style="background-color: var(--global--color-background); color: var(--global--color-primary); font-family: var(--global--font-secondary); font-size: var(--global--font-size-base);">fficult to add custom build configs. One way to add custom configs is to eject the app, but then it overrides the </span><strong style="background-color: var(--global--color-background); color: var(--global--color-primary); font-family: var(--global--font-secondary); font-size: var(--global--font-size-base);">Only one build dependency</strong><span style="background-color: var(--global--color-background); color: var(--global--color-primary); font-family: var(--global--font-secondary); font-size: var(--global--font-size-base);"> advantage. The other way is you can use packages like </span><a style="background-color: var(--global--color-background); font-family: var(--global--font-secondary); font-size: var(--global--font-size-base);" href="https://github.com/arackaf/customize-cra">customize-cra</a><span style="background-color: var(--global--color-background); color: var(--global--color-primary); font-family: var(--global--font-secondary); font-size: var(--global--font-size-base);"> or </span><a style="background-color: var(--global--color-background); font-family: var(--global--font-secondary); font-size: var(--global--font-size-base);" href="https://github.com/timarney/react-app-rewired">react-app-rewired</a><span style="background-color: var(--global--color-background); color: var(--global--color-primary); font-family: var(--global--font-secondary); font-size: var(--global--font-size-base);"> but then they have limited capabilities. </span><span style="background-color: var(--global--color-background); color: var(--global--color-primary); font-family: var(--global--font-secondary); font-size: var(--global--font-size-base);">Abstracts everything. It&#8217;s important to understand the things that need to run a React app. But due to it&#8217;s </span><strong style="background-color: var(--global--color-background); color: var(--global--color-primary); font-family: var(--global--font-secondary); font-size: var(--global--font-size-base);">Only one build dependency</strong><span style="background-color: var(--global--color-background); color: var(--global--color-primary); font-family: var(--global--font-secondary); font-size: var(--global--font-size-base);"> advantage, a beginner might think that </span><code style="font-size: var(--global--font-size-base);">react-scripts</code><span style="background-color: var(--global--color-background); color: var(--global--color-primary); font-family: var(--global--font-secondary); font-size: var(--global--font-size-base);"> is the only dependency needed to run react apps and might not know that transpiler(babel), bundler(webpack) are the key dependencies which are used under the hood by </span><code style="font-size: var(--global--font-size-base);">react-scripts</code><span style="background-color: var(--global--color-background); color: var(--global--color-primary); font-family: var(--global--font-secondary); font-size: var(--global--font-size-base);">. This happened to me until I read this awesome </span><a style="background-color: var(--global--color-background); font-family: var(--global--font-secondary); font-size: var(--global--font-size-base);" href="https://medium.com/the-node-js-collection/modern-javascript-explained-for-dinosaurs-f695e9747b70">article</a><span style="background-color: var(--global--color-background); color: var(--global--color-primary); font-family: var(--global--font-secondary); font-size: var(--global--font-size-base);">. </span><span style="background-color: var(--global--color-background); color: var(--global--color-primary); font-family: var(--global--font-secondary); font-size: var(--global--font-size-base);">CRA is bloated &#8211; IMO. For example, CRA comes with SASS support, if you are using </span><code style="font-size: var(--global--font-size-base);">plain CSS</code><span style="background-color: var(--global--color-background); color: var(--global--color-primary); font-family: var(--global--font-secondary); font-size: var(--global--font-size-base);"> or </span><code style="font-size: var(--global--font-size-base);">Less</code><span style="background-color: var(--global--color-background); color: var(--global--color-primary); font-family: var(--global--font-secondary); font-size: var(--global--font-size-base);"> it&#8217;s an extra dependency that you will never use.</span></p>


How I created, moved to next.js from react, Create React App

<p><span style="color: var(--global--color-primary); font-family: var(--global--font-secondary); font-size: var(--global--font-size-base); background-color: var(--global--color-background);">Technology</span><span style="color: var(--global--color-primary); font-family: var(--global--font-secondary); font-size: var(--global--font-size-base); background-color: var(--global--color-background);"> is advancing at an unprecedented pace, and it&#8217;s no surprise that it&#8217;s having a significant impact on our lives. From smartphones to self-driving cars, technology is making our lives more convenient, more productive, and more connected.</span></p>
<p>One of the most significant technological advancements of recent years has been the rise of artificial intelligence. AI is being used in a variety of industries, from healthcare to finance, to make important decisions and automate processes. In healthcare, for example, AI is being used to analyze large amounts of patient data to help doctors make more accurate diagnoses. In finance, AI is being used to detect and prevent fraud.</p>
<p>Another area where technology is having a major impact is in the field of robotics. Robotics is being used to automate repetitive tasks, and to make manufacturing more efficient. Robotics is also being used to perform tasks that are dangerous for humans, such as exploring deep space or defusing bombs.</p>
<p>The rise of technology has also led to an increase in automation, which has had both positive and negative effects. On the one hand, automation has led to increased productivity and efficiency. On the other hand, it has also led to job losses and a decrease in human interaction.</p>
<p>One of the most exciting areas of technology is the Internet of Things (IoT). IoT is the network of physical devices, vehicles, buildings, and other items embedded with electronics, software, sensors, and connectivity which enables these objects to connect and exchange data. This technology is making it possible for everyday objects to communicate with one another, creating a more connected world.</p>
<p>Finally, it&#8217;s worth mentioning the impact of technology on communication. Social media and messaging apps have made it easier than ever to stay in touch with people, no matter where they are in the world. But it also has a downside, it&#8217;s also led to a decrease in face-to-face communication and an increase in cyberbullying.</p>
<p>In conclusion, technology is advancing at a rapid pace, and it&#8217;s having a significant impact on our lives. While it has its drawbacks, technology is making our lives more convenient, more productive, and more connected. As technology continues to evolve, it will be interesting to see how it will shape our future.</p>
<p>&nbsp;</p>


Technology and AI

<h2>The Problem With Scroll Animations Today</h2>
<p>
Frontend developers love scroll-based effects.
</p>
<p>
Parallax sections. Progress indicators. Sticky reveals. Scroll-triggered fades.
</p>
<p>
But most implementations still rely on:
</p>
<ul>
<li><code>scroll</code> event listeners</li>
<li><code>requestAnimationFrame</code></li>
<li>IntersectionObservers</li>
<li>animation libraries</li>
<li>manual DOM synchronization</li>
</ul>
<p>
Which means:
</p>
<ul>
<li>main-thread work increases</li>
<li>animations become janky</li>
<li>performance suffers on low-end devices</li>
<li>mobile scrolling becomes inconsistent</li>
</ul>
<p>
And ironically:
</p>
<blockquote><p>
  The browser already knows the scroll position better than your JavaScript ever will.
</p></blockquote>
<p>
That’s exactly why <code>scroll-timeline</code> matters.
</p>
<hr />
<h2>What Is <code>scroll-timeline</code>?</h2>
<p>
<code>scroll-timeline</code> is part of the newer CSS Scroll-Driven Animations specification.
</p>
<p>
It allows animations to sync directly with scroll progress using native CSS.
</p>
<p>
Meaning:
</p>
<ul>
<li>no scroll listeners</li>
<li>no animation frame loops</li>
<li>no JS-driven interpolation</li>
</ul>
<p>
The browser handles animation timing internally.
</p>
<hr />
<h2>The Old Way (And Why It Becomes Painful)</h2>
<h3>Traditional JavaScript Scroll Animation</h3>
<pre><code class="language-js">
window.addEventListener('scroll', () =&gt; {
  const progress = window.scrollY / 1000;

  element.style.transform =
    `translateY(${progress * 100}px)`;
});
</code></pre>
<p>
This works.
</p>
<p>
But it introduces:
</p>
<ul>
<li>continuous event handling</li>
<li>layout synchronization overhead</li>
<li>main-thread dependency</li>
<li>potential frame drops</li>
</ul>
<p>
Especially problematic on:
</p>
<ul>
<li>mobile devices</li>
<li>large pages</li>
<li>complex React apps</li>
</ul>
<hr />
<h2>Enter <code>scroll-timeline</code></h2>
<h3>Native Scroll Animation</h3>
<pre><code class="language-css">
.progress-bar {
  animation: grow linear;
  animation-timeline: scroll();
}

@keyframes grow {
  from {
    transform: scaleX(0);
  }

  to {
    transform: scaleX(1);
  }
}
</code></pre>
<p>
That’s already scroll-driven.
</p>
<p>
Without JavaScript.
</p>
<hr />
<h2>What Actually Changes Under the Hood</h2>
<p>
Traditional scroll animation:
</p>
<ul>
<li>JavaScript watches scrolling</li>
<li>JS calculates progress</li>
<li>JS updates styles</li>
<li>browser re-renders</li>
</ul>
<p>
With <code>scroll-timeline</code>:
</p>
<ul>
<li>browser internally maps scroll progress to animation progress</li>
<li>animation pipeline becomes native</li>
<li>less synchronization overhead exists</li>
</ul>
<p>
This is a major architectural improvement.
</p>
<hr />
<h2>Real-World Use Cases</h2>
<h3>1. Reading Progress Bars</h3>
<pre><code class="language-css">
.progress {
  position: fixed;
  top: 0;
  left: 0;
  height: 4px;

  animation: progress linear;
  animation-timeline: scroll();
}

@keyframes progress {
  from {
    width: 0%;
  }

  to {
    width: 100%;
  }
}
</code></pre>
<hr />
<h3>2. Scroll-Reveal Sections</h3>
<pre><code class="language-css">
.card {
  animation: fade-up linear;
  animation-timeline: view();
}

@keyframes fade-up {
  from {
    opacity: 0;
    transform: translateY(40px);
  }

  to {
    opacity: 1;
    transform: translateY(0);
  }
}
</code></pre>
<hr />
<h3>3. Parallax Effects</h3>
<pre><code class="language-css">
.hero-image {
  animation: parallax linear;
  animation-timeline: scroll();
}

@keyframes parallax {
  from {
    transform: translateY(0);
  }

  to {
    transform: translateY(200px);
  }
}
</code></pre>
<hr />
<h2>React Developers Need to Rethink Scroll Logic</h2>
<p>
A lot of React applications currently do this:
</p>
<pre><code class="language-jsx">
useEffect(() =&gt; {
  const onScroll = () =&gt; {
    setProgress(window.scrollY);
  };

  window.addEventListener('scroll', onScroll);

  return () =&gt;
    window.removeEventListener('scroll', onScroll);
}, []);
</code></pre>
<p>
Which means:
</p>
<ul>
<li>state updates during scrolling</li>
<li>component re-renders</li>
<li>potential hydration complexity</li>
</ul>
<p>
Most of this disappears with native scroll-driven CSS animations.
</p>
<p>
That’s the important shift.
</p>
<hr />
<h2>⚡ Why Performance Gets Better</h2>
<p>
Native scroll animations:
</p>
<ul>
<li>avoid excessive JS execution</li>
<li>reduce layout thrashing</li>
<li>can integrate better with compositor pipelines</li>
<li>improve smoothness on constrained devices</li>
</ul>
<p>
The browser becomes the animation engine.
</p>
<p>
Not your event listeners.
</p>
<hr />
<h2>🚨 Important Browser Reality</h2>
<p>
This feature is still evolving.
</p>
<p>
Support is improving rapidly, but production readiness depends on:
</p>
<ul>
<li>your audience</li>
<li>browser targets</li>
<li>enterprise requirements</li>
</ul>
<p>
This is one of those features where:
</p>
<blockquote><p>
  progressive enhancement is the correct strategy.
</p></blockquote>
<hr />
<h2>Another Important Gotcha</h2>
<p>
Developers often assume:
</p>
<blockquote><p>
  “No JavaScript means no complexity.”
</p></blockquote>
<p>
That’s not entirely true.
</p>
<p>
Complex animation choreography can still become difficult.
</p>
<p>
Especially when combining:
</p>
<ul>
<li>multiple timelines</li>
<li>nested scrolling containers</li>
<li>sticky positioning</li>
<li>view timelines</li>
</ul>
<p>
Good architecture still matters.
</p>
<hr />
<h2>❌ When NOT to Use <code>scroll-timeline</code></h2>
<p>
Avoid if:
</p>
<ul>
<li>browser support is mission-critical</li>
<li>animations depend heavily on application state</li>
<li>complex sequencing logic exists</li>
<li>you need physics-based interactions</li>
</ul>
<p>
In those cases:
</p>
<ul>
<li>GSAP</li>
<li>Framer Motion</li>
<li>custom animation systems</li>
</ul>
<p>
may still be better tools.
</p>
<hr />
<h2>🧠 Opinion (This Is the Bigger Industry Shift)</h2>
<p>
Frontend developers spent years building animation systems around browser limitations.
</p>
<p>
Now modern CSS is increasingly absorbing those responsibilities natively.
</p>
<p>
The trend is becoming very clear:
</p>
<ul>
<li>less JavaScript orchestration</li>
<li>more browser-native capabilities</li>
<li>better rendering integration</li>
</ul>
<p>
Developers who continue assuming:
</p>
<blockquote><p>
  “Animations always need JavaScript”
</p></blockquote>
<p>
are operating with increasingly outdated assumptions.</p>


Super imposing a image with text and using that image as twitter tweet

How I created, moved to next.js from react, Create React App

Technology and AI

The CSS Animation Feature That Could Replace Half Your Scroll Event Code – scroll-timeline