seo | SEO/OM plugin for Croogo | Search Engine Optimization library

Your items are overlapping because you're not allowing any lerping diffing when the items should switch positions.

The current value should never equal the target value. If the values match, than the current value needs to catch up the target — giving that erratic movement and wrong calculations, additionally aggravated for the two sibling elements which should be perfectly in sync to give that immediate snap-back, perceived as a fluid continuous motion.

• Instead of animating two (or more) children independently,
  animate only the parent .loop-container.
• The container should be as wide as one child element exactly.
• "Push" one child element to the far left using position: absolute; left: -100%
• To allow the target value to be always greater than the current value:
  when the target value is greater than 100 — set current to the negative difference of the two values, and target to 0

_{Demo time:}

It appears you are using react-router-dom@6 so there are no longer any route props. In other words, props.match is undefined. Reading into props.match.params then throws the error.

Use the useParams hook to access the date route param.

1. You should already be linking to the files without the .php extension on your internal URLs (ie. href="/page1", not href="/page1.php"). I'm also assuming that your URLs don't otherwise contain dots (which normally delimits the file extension).

2. Implement a rewrite to append the .php extension if required. This needs to go near the top of the root .htaccess file:

You can not do this with JavaScript.

But you can use PHP as follows

You need passHref only with some tags, here is an example. is not about SEO, and your quote is about "If your does not have passHref attribute and has child, your SEO might be broken".

Just create 2 pages with passHref and without, and check the pages, for example, with LIghthouse of chrome or any other tool. Also, check the DOM, you will see, no changes in SEO directly. (ofc if child components are html or even react components with no "required" href property.)

Before we start, I do agree with you that these 2 different websites have completely different behaviors, hence demand different handling approaches.

To the point - let's break your question into the followings factors:

• Availability
• Incoming Traffic
• Pricing

Availability Most chances that your landing page should be served via a CDN in order to get world-wide coverage, while the app itslef may use a cdn. Some technical point to consider:

• If that page is also build with a modern stack it also can be hosted via a cloud-based storage
• You can select a CDN from your hosting cloud provider (such as aws, azure, gcp, etc.) or use a completely external service (such as max cdn). It mainly depends on the technological stack that your website

Incoming Traffic As landing pages are opened to the general public and using anonymous access (e.g. - no login is required) they are at a high risk level for ddos and other malicious attacks. This is why these websites are mostly hosted behind a waf, gateway or any other tier that help these websites to protect themselves from being hijacked. Also, in most use-cases, these websites should handle very high loads (way more than the app itself, which is login protected). Some key points:

• Landing page websites loads may change drastically and without any warning.. so they should be deployed in an elastic high availability manner which means - when high loads occur - please use more resources to handle these loads (and please automatically decrease them when loads return to normal levels)
• In terms of logs - incoming traffic is different when dealing with identify users and when handling anonymous access - both in terms of cyber security as well of data analysis
• Apps that require login, will mostly need to use a solid gateway and some sort of identity management solution. These parts have no benefit to the landing page in terms of functionality and also - resource usage

Pricing Yes, we want to gain as much flexibility as possible, but we also want to pay the lower price possible as well. Coupling these 2 different apps may cause using expensive resources just to handle landing page loads. On the other hand - decoupling them will allow us to track every resource group and pay only for what we are using. So yes - it's even makes sense in terms of pricing

In short (sort of) - 2 different apps should have 2 different ways of deployments - each with its own technical stack and configurations. That will give us

• Flexibility - change in one environment will not damage the other
• Deployment - 2 different pipelines - each dedicated only to the a single solution
• Pricing - there is no need to waste resources (for example: by over using libraries that consume resources that most time is unused) hence - paying less
• DevOps - in some use-cases - 2 different devOps personnel may handle each pipeline, which may be an advantage

Hope this information helps

Here's what I did, worked like a charm...

1. create a Component called HubspotContactForm

I don't think there's necessarily a good reason for this - I think this is basically a historical artifact. Let me explain with some git archeology.

In current Linux, this limit is governed by MAX_RW_COUNT: