Project doesn't build with node v16.
(Actually even specified node-gyp version does not recompile itself)

For long timelines (hundreds of items?) responsive images (and lazy loading) are a must.

Responsive images are hard, but the first step is to provide the image ID inside the markup to give a change to filter to hook and adapt the <img> tag markup accordingly.

Lazy loading is already WP default so it makes sense to make Timeline child image lazy too.

It's great to have hosted the source-code of this plugin at GitHub but I wonder what evolution can be assumed regarding this plugin in the long run.

• Is work on new feature / bugfix to be expected?
• Does maintenance-work going to happen?
• Are code-review and external pull-request merging expected to happen?
  ... along the next 12 months?

Thank you

So far, we have:

• cp-timeline/content-timeline inside includes/cool-timeline-block
• cp-timeline/content-timeline-child inside includes/cool-timeline-block
• cooltimeline/timeline-block inside includes/gutenberg-block

Do you mind defining/documenting/formalizing this, why was is setup that way and what would be a possibly better organization without breaking existing namespacing?
It's also a bit confusing that that gutenberg-block directory contains the blocks namespaced cooltimeline, while the cool-timeline-block directory contains two blocks with the cp-timeline namespace.

Probably an useful feature

The "both-sided" timeline offers the option to select whether a story appears on the right or the left.

For huge timeline (eg: 20 items per year) this presents a limitation: Inserting a story forces the editor to reposition all subsequent stories.

A solution would be automatic side alternate. (Only the first item would be manually placed by the user then all others would be placed on the left/right automatically alternatively).

In the WP build, at https://plugins.trac.wordpress.org/browser/timeline-block/trunk/includes/cool-timeline-block/dist/blocks.build.js
The block is named cp-timeline/content-timeline-block

This is also the case of the build provided in this repository at https://github.com/narinder9/story-timeline-block/blob/e41892fbee15612c29998480e11582d9bea9de23/includes/cool-timeline-block/dist/blocks.build.js

But in the source code :
https://github.com/narinder9/story-timeline-block/blob/e41892fbee15612c29998480e11582d9bea9de23/includes/cool-timeline-block/src/story-timeline/block.js#L66
The block is named cp-timeline/content-timeline (no -block suffix)

Compiling and using this break existing blocks.

Any explanation about the intent / issue?

In 8d203c9, in includes/cool-timeline-block/src/story-timeline-child/edit.js

-                             tagName="h3"
+                                 className="timeline-block_title"
+                             tagName={headingTag}

+                               <div className='timeline-block_desc'>

Before:

<div class="wp-block-cp-timeline-content-timeline-block-child swiper-slide"><div class="timeline-content icon-false ">
<div class=" timeline-block-timeline ctl-row  position-left"><div class="ctl-6 timeline-block-time"><div class="story-time"><p>SEPTEMBER</p>
</div></div><div class="timeline-block-icon">

</div>
<div class="ctl-6 timeline-block-detail"><div class="story-details"><div class="story-image"><img src="https://my/file.jpg" alt="" class="wp-image-6619"/></div><div class="story-content"><h3>
</h3>
<p>MYCONTENT</p></div></div></div></div></div></div>

After:

<div class="wp-block-cp-timeline-content-timeline-block-child swiper-slide"><div class="timeline-content icon-false ">
<div class="timeline-block-timeline ctl-row  position-left"><div class="ctl-6 timeline-block-time"><div class="story-time"><p>SEPTEMBER</p>
</div></div><div class="timeline-block-icon">

<svg stroke="currentColor" fill="currentColor" stroke-width="0" viewBox="0 0 512 512" height="1em" width="1em" xmlns="http://www.w3.org/2000/svg"><path d="M256 8C119 8 8 119 8 256s111 248 248 248 248-111 248-248S393 8 256 8z"></path></svg>
^^^^^^^^^^^^^^^^^^^^^^^ Compatibility not ensured
</div>
<div class="ctl-6 timeline-block-detail"><div class="story-details"><div class="story-image"><img src="https://my/file.jpg" alt="" class="wp-image-6619"/></div><div class="story-content">
<h3 class="timeline-block_title">
           ^^^^^^^^^^^^^^^^^^^ Compatibility not ensured
</h3>
<div class="timeline-block_desc">
            ^^^^^^^^^^^^^^^^^^^ Compatibility not ensured

<p>MYCONTENT</p></div></div></div></div></div></div></div>

The currently generated markup looks like:

<div class="wp-block-cp-timeline-content-timeline-block Cool-Content-Timeline">
<div class="cool-timeline-block-b238fb3a-989b-4379-8fae-61af5ad138f2">
<style scoped="true">
.cool-timeline-block-b238fb3a-989b-4379-8fae-61af5ad138f2 .cool-vertical-timeline-body .story-time p{color: #333;}
 ... [lot of CSS] ...
</style>
<div class="cool-vertical-timeline-body both-sided left">
<div class="cool-timeline-block-list">...

But any change to the style.scss (like one that recently introduced linear-gradient(to bottom, rgba(230, 230, 230, 0) 0%, #D91B3E 10%) break the generated markup identity.

While such a thing is something difficult to avoid, inlining the CSS is calling for problems and should rather not be done.

A supported alternative (provided by WP or another upstream) must be found.