Consider deprecating Queulat

[brylie]

Problem

Remove the project dependency on Queulat.

Description

The project depends on a WordPress development framework called Queulat. The Queulat framework has some possible shortcomings

• very limited documentation
• limited community contribution
• defining its own conventions
• has broken/abandoned dependencies
  • https://packagist.org/packages/anahkiasen/underscore-php

Additional context

Before making the decision whether to deprecate Queulat, it is good to

• determine how Queulat is being used in the project
• identify alternatives in the WordPress development ecosystem
  • these should be ideally part of WordPress core and not some third-party, proprietary plugin

How is Queulat used?

Queulat is used to

• define the theme settings page
• create custom WordPress metaboxes

What would be used instead of Queulat?

Use standard WordPress functions to define the theme options forms

• https://blog.templatetoaster.com/wordpress-settings-api-creating-theme-options/

Use conventional WordPress code to define metaboxes.

• https://developer.wordpress.org/plugins/metadata/custom-meta-boxes/

Related code

Queulat is used in the following files:

creativecommons-base/inc/settings.php

Lines 2 to 11 in 39e7252

	use Queulat\Forms\Element\Div;
	use Queulat\Forms\Element\Form;
	use Queulat\Forms\Node_Factory;
	use Queulat\Forms\Element\WP_Nonce;
	use Queulat\Forms\Element\WP_Editor;
	use Queulat\Forms\Element\WP_Image;
	use Queulat\Forms\Element\Input;
	use Queulat\Forms\Element\Input_Number;
	use Queulat\Forms\Element\Input_Checkbox;
	use Queulat\Forms\Element\Select;

creativecommons-base/inc/metaboxes.php

Lines 2 to 5 in 39e7252

	use Queulat\Metabox;
	use Queulat\Forms\Node_Factory;
	use Queulat\Forms\Element\WP_Gallery;
	use Queulat\Forms\Element\Input;

creativecommons-base/composer.json

Lines 12 to 17 in 39e7252

	"repositories": [
	{
	"no-api": true,
	"type": "vcs",
	"url": "https://github.com/creativecommons/queulat"
	},

What to avoid?

Avoid adding new plugins to this theme, particular those with premium extensions or features.

[brylie]

@hugosolar could you share some of your thoughts on the Queulat framework?

[hugosolar]

Hello @brylie
I agree about what you're saying. Queulat lacks of documentation, although in my opinion is a good tool for managing forms and metaboxes it saves a lot of time when you're building admin screens.
I think using WordPress itself will increase the development times but it's up to you.

I'd recommend this plugin instead

• Fieldmanager

it has much more documentation, last release is from 2020 and it's approved by WP VIP platform.

[brylie]

It's just strange to me that basic form building isn't part of WordPress core. Forms seem like a major component. The lack of simple form building has led to a fragmented ecosystem of projects trying to provide that functionality.

[hugosolar]

I'd tend to agree with your opinion, I feel like WordPress lacks so many things. Although, some of the functionality made by Queulat in this theme can be moved to something more related to the WordPress core for instance Gutenberg blocks (which made the editor work so much easy) or maybe something like shortcodes (thinking in the classic editor which will be supported for another year I think)