This PR addresses the feature request in #11 .

The transform keeps the list block's type (ordered, unordered):

It also attempts to pass other attributes from the list block to each resulting paragraph, which allows for some things like Typography settings to come over. Unfortunately, the font family setting is currently still experimental and exists on the list block but not the paragraph block (???), but once it is supported it should come over.

I'm happy to try to attempt a similar transform from the columns block, maybe in a separate PR?

The Situation

I had never considered that someone else might want to contribute to the plugin, although I know it's a possibility and I have contributed to other plugins on occasion myself! To that end, if build files are committed then there will always be a conflict (if just of the date and time in the asset files), which will make merging more problematic.

To Ponder

So, should build files be excluded the way they are in Gutenberg? 🤔

Currently using a multiple entry custom webpack config setup. But I've tested in another project that the new wp-scripts feature for supporting multiple block is FLAWless. So should update tooling here to simplify things.

I was initially calling it Superlist and not Super List, and most people refer to it as Superlist as well. So should just change it, keep things streamlined. :)

A lot of the time lists that include other blocks in them will want to hide the list icon because the block is being used for semantic purposes. The ability to hide the list icons would be great.

Closes #8

This is a pretty awesome PR, even if I do say so myself. There are a few different things happening here:

• I've added link color support to both blocks
• the list-item width setting no longer sets explicit inline size, and rather modifies a CSS Custom Property inline instead
• there is theme.json support for not only the list-item width setting, but for all the settings the block supports, so any theme can set their own defaults for the Super List block.
  • this includes smart support for the orientation setting! if theme.json sets a default for the list orientation, it will be respected. So if a theme primarily wants to use Super List in horizontal mode, they can set that as their default so they don't keep having to switch it in every new block.
• we've also got a handy dandy theme.json example in the block itself to make life easier for theme authors

Currently block.json is not loaded dynamically when people install a block from the block library search. This means if there are items missing in index.js, it causes all sorts of issues. This has been reported and documented in the following issues in the Gutenberg repo:

• https://github.com/WordPress/gutenberg/issues/38588
• https://github.com/WordPress/gutenberg/issues/38494
• https://github.com/WordPress/gutenberg/issues/38245

In light of this information, this PR pulls all the metadata from block.json files and pops it into index.js

Closes #5

• This PR adds anchor support to both Super List and Super List Item block.
• There is also a slight visual adjustment to the Super List block inserter, to make it a little smaller but still obvious and easy to click on.
• This PR also adds the Vertical Alignment capability to the overall super list. It does not as of yet, allow you to control vertical alignment on individual Super List Items – that would be part of a larger conversation connected to this comment about layout capabilities.

As far as the Vertical Alignment feature goes:

This is ready and I've done some preliminary testing. But it needs to be tested a bit more to ensure there won't be that Block Recovery error on existing super lists. I've set it up so that the justification settings only add classes IF a justification is set, so theoretically that means there should be no errors on past blocks that don't have anything set. But I'd like to test it a bit more before merging.

• [x] Test on online installations where I have the v0.1.0 installed to check if justification addition causes an error.

Closes #15

The following CSS adjustment has been made to the main super list block:

/* allow indentation via padding to occur when a super list is nested
inside a super list item, otherwise, remove the unnecessary padding-left. */
:not(li) > ul.wp-block-createwithrani-superlist-block {
	padding-inline-start: 0;
	margin-inline-start: 0;
	li {
		flex: 1;
	}
}

Basically, if a super list is the child of anything but an <li> element, the indentation through padding and margin is removed from the start of the block (in english, that would be on the left). So if the super list is the child of an <li> element, any indentation provided by wordpress, theme, or user is respected.

Currently the panel is mistakenly named Repeater Settings, when in fact it should be List Settings. And Sub-item max-width, should be List-item max-width. In general the max-width setting needs improvement, but until then the label should still be corrected.

Right now, the block doesn't inherently support typography. Being able to set typography options for the entire list, or the entire list-item would be super helpful and avoid manual fixing on a per nested-block basis whenever you need to change any typography settings.

Hi,

I downloaded your plugin from the plugin directory this morning (I used wp-cli but that shouldn't affect it; it still fetches the plugin from https://downloads.wordpress.org/plugin/superlist-block.0.1.0.zip ) and activated it but I received the following notice in my terminal after installation signifying that the block wasn't properly registered.

I'm not 100% sure, but I think the cause is that register_block_type is expecting a block.json file in the build/superlist directory and such a directory does not exist.

I'm using Gutenberg 13.4.0; no other plugins installed. WP 6.0.0.

PHP Notice: Function WP_Block_Type_Registry::register was called incorrectly. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type Please see Debugging in WordPress for more information. (This message was added in version 5.0.0.) in /path/to/my/wordpress_install/public_html/wp-includes/functions.php on line 5831 PHP Stack trace: PHP 1. {main}() /usr/local/bin/wp:0 PHP 2. include() /usr/local/bin/wp:4 PHP 3. include() phar:///usr/local/bin/wp/php/boot-phar.php:11 PHP 4. WP_CLI\bootstrap() phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php:27 PHP 5. WP_CLI\Bootstrap\LaunchRunner->process($state = class WP_CLI\Bootstrap\BootstrapState { private $state = ['context_manager' => class WP_CLI\ContextManager { private $contexts = ['cli' => class WP_CLI\Context\Cli { }, 'admin' => class WP_CLI\Context\Admin { }, 'frontend' => class WP_CLI\Context\Frontend { }, 'auto' => class WP_CLI\Context\Auto { private $context_manager = ... }]; private $current_context = 'cli' }] }) phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/bootstrap.php:78 PHP 6. WP_CLI\Runner->start() phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php:28 PHP 7. WP_CLI\Runner->load_wordpress() phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1235 PHP 8. require() phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1317 PHP 9. do_action($hook_name = 'init') /path/to/my/wordpress_install/public_html/wp-settings.php:598 PHP 10. WP_Hook->do_action($args = [0 => '']) /path/to/my/wordpress_install/public_html/wp-includes/plugin.php:476 PHP 11. WP_Hook->apply_filters($value = '', $args = [0 => '']) /path/to/my/wordpress_install/public_html/wp-includes/class-wp-hook.php:331 PHP 12. create_block_superlist_block_block_init('') /path/to/my/wordpress_install/public_html/wp-includes/class-wp-hook.php:307 PHP 13. register_block_type($block_type = '/path/to/my/wordpress_install/public_html/wp-content/plugins/superlist-block/build/superlist', $args = uninitialized) /path/to/my/wordpress_install/public_html/wp-content/plugins/superlist-block/superlist-block.php:29 PHP 14. WP_Block_Type_Registry->register($name = '/path/to/my/wordpress_install/public_html/wp-content/plugins/superlist-block/build/superlist', $args = []) /path/to/my/wordpress_install/public_html/wp-includes/blocks.php:393 PHP 15. _doing_it_wrong($function = 'WP_Block_Type_Registry::register', $message = 'Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type', $version = '5.0.0') /path/to/my/wordpress_install/public_html/wp-includes/class-wp-block-type-registry.php:77 PHP 16. trigger_error($message = 'Function WP_Block_Type_Registry::register was called incorrectly. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type Please see Debugging in WordPress for more information. (This message was added in version 5.0.0.)', $error_type = 1024) /path/to/my/wordpress_install/public_html/wp-includes/functions.php:5831 PHP Notice: Function WP_Block_Type_Registry::register was called incorrectly. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type Please see Debugging in WordPress for more information. (This message was added in version 5.0.0.) in /path/to/my/wordpress_install/public_html/wp-includes/functions.php on line 5831 PHP Stack trace: PHP 1. {main}() /usr/local/bin/wp:0 PHP 2. include() /usr/local/bin/wp:4 PHP 3. include() phar:///usr/local/bin/wp/php/boot-phar.php:11 PHP 4. WP_CLI\bootstrap() phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php:27 PHP 5. WP_CLI\Bootstrap\LaunchRunner->process($state = class WP_CLI\Bootstrap\BootstrapState { private $state = ['context_manager' => class WP_CLI\ContextManager { private $contexts = ['cli' => class WP_CLI\Context\Cli { }, 'admin' => class WP_CLI\Context\Admin { }, 'frontend' => class WP_CLI\Context\Frontend { }, 'auto' => class WP_CLI\Context\Auto { private $context_manager = ... }]; private $current_context = 'cli' }] }) phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/bootstrap.php:78 PHP 6. WP_CLI\Runner->start() phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php:28 PHP 7. WP_CLI\Runner->load_wordpress() phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1235 PHP 8. require() phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1317 PHP 9. do_action($hook_name = 'init') /path/to/my/wordpress_install/public_html/wp-settings.php:598 PHP 10. WP_Hook->do_action($args = [0 => '']) /path/to/my/wordpress_install/public_html/wp-includes/plugin.php:476 PHP 11. WP_Hook->apply_filters($value = '', $args = [0 => '']) /path/to/my/wordpress_install/public_html/wp-includes/class-wp-hook.php:331 PHP 12. create_block_superlist_block_block_init('') /path/to/my/wordpress_install/public_html/wp-includes/class-wp-hook.php:307 PHP 13. register_block_type($block_type = '/path/to/my/wordpress_install/public_html/wp-content/plugins/superlist-block/build/superlist-item', $args = uninitialized) /path/to/my/wordpress_install/public_html/wp-content/plugins/superlist-block/superlist-block.php:30 PHP 14. WP_Block_Type_Registry->register($name = '/path/to/my/wordpress_install/public_html/wp-content/plugins/superlist-block/build/superlist-item', $args = []) /path/to/my/wordpress_install/public_html/wp-includes/blocks.php:393 PHP 15. _doing_it_wrong($function = 'WP_Block_Type_Registry::register', $message = 'Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type', $version = '5.0.0') /path/to/my/wordpress_install/public_html/wp-includes/class-wp-block-type-registry.php:77 PHP 16. trigger_error($message = 'Function WP_Block_Type_Registry::register was called incorrectly. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type Please see Debugging in WordPress for more information. (This message was added in version 5.0.0.)', $error_type = 1024) /path/to/my/wordpress_install/public_html/wp-includes/functions.php:5831

Thanks for great plugin! When I try set list as "No marker", container is changed from ul to div, but items are still li, which is not semantically correct, I think.

Test that setting link, colour, font, etc through the block area works. Remove CSS Properties around it from the custom area because although it allows theme defaults, it messes with user customization, because turns out CSS Custom Properties don't fall back to the last declaration, they always fall back to the computed value of the parent which is..deeply nonsensical, but there you go.

The term List Orientation, while sufficient for its current capabilities, doesn't do a good job of leaving room for more list styles. In addition, the use of the arrow icons is vague at best.

I'm proposing two things here:

1. List Orientation be renamed to List Style, and changing the current List Style to List Type or something else
2. Either replacing the arrow icons with text or adding the text alongside the icons for clearer and better representation.

This will likely involve deprecating some attributes, which means confirming and checking that deprecation actually works.

Often times, content grids have background images. It'd be nice if the plugin supported background images as well. Unsure at this time if this is a feature better put in pro. But for now, proposing it for the free plugin.

Closes #28

Adds helpful inline documentation throughout the plugin to help future folks (future me, or future contributors) understand what's going on.