dedanirungu

I am working on a Laravel ERP which I have managed to port to WordPress as illustrated in the attachment image shown below,

I noticed a new Laravel installation is 39MB before adding my modules.

I will therefore self-host the plugin at?https://github.com/mybizna/mybizna-wp-core.

It has worked.

Thank you.

We usually develop custom type that uses description section to get detailed information on particular post. We have been using wordpress because it made every thing easier as shown on the image link below. (NOTE I am using WooCommerce for example)

View post on imgur.com

The page looks very different after installing Gutenberg as shown below.

View post on imgur.com

This is very confusing because we do not intend to submit a post but we are only adding product description. The Classic Editor had advantage of Keeping It Simple and Smart(KISS).

Gutenberg should only be used on adding blog post and should not replace every area custom types are used. There should be an option to choose whether to use Gutenberg or not when developing custom types.

Example: We have customs type for Job, Faqs and Testimonials. Why would I need Gutenberg when posting? The post description is usually one paragraph or two and does not require column,blocks etc.

Suggestion: Let use use Gutenberg on submitting post, but on custom types let us allow the use of classic editor where it is needed.

We usually develop custom type that uses description section to get detailed information on particular post. We have been using wordpress because it made every thing easier as shown on the image link below. (NOTE I am using WooCommerce for example)

View post on imgur.com

The page looks very different after installing Gutenberg as shown below.

View post on imgur.com

This is very confusing because we do not intend to submit a post but we are only adding product description. The Classic Editor had advantage of Keeping It Simple and Smart(KISS).

Gutenberg should only be used on adding blog post and should not replace every area custom types are used. There should be an option to choose whether to use Gutenberg or not when developing custom types.

Example: We have customs type for Job, Faqs and Testimonials. Why would I need Gutenberg when posting? The post description is usually one paragraph or two and does not require column,blocks etc.

Suggestion: Let use use Gutenberg on submitting post, but on custom types let us allow the use of classic editor where it is needed.

I developed a plugins that creates custom types for frequently used data type eg faqs, testimonials, our services etc.

This custom types are then displayed with additional fields where by I can decide to have the title and description or remove them all together.

On Gutenberg editor all the customization is not rendered and in some instances the layout is not what I would expect for a CMS. This is confusing my employees when using the CMS.

This is very frustrating.