Notice Block

  • Resolved omegatcu

    (@omegatcu)


    7 years, 4 months ago

    Hello,

    why was Notice depreciated?
    Is there a replacement that I don’t see? – I have this Plugin only for that Block.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Hardeep Asrani

    (@hardeepasrani)

    7 years, 4 months ago

    Hey there,

    Notice block was depreciated to make way for Section block, which allows you to create complex designs, including a Notice block. Notice block was an experiment we did, and we realized it wasn’t the best block for our plugin, so we depreciated it before more people start using it.

    If you’re willing, we would love to help you in migrating your Notice block to Section block.

    Let us know your feedback, and we understand your frustration so would love to have your views on this so we could improve the decision process.

    • This reply was modified 7 years, 4 months ago by Hardeep Asrani. Reason: fix autocorrect
    Thread Starter omegatcu

    (@omegatcu)

    7 years, 4 months ago

    Hey Hardeep,

    I assume the best way would then be to use the section to recreate the Block and then replace the others for that.

    As for the Decision Process:
    I do understand that some things have to be changed and so to depreciate the Block was the best way to do. But I would like to see the alternative to it – like if you remove something then build a template for it or show us how to replace it in an easy way.

    As for Blocks in general – the biggest problem, also long term, I see with replacing them. In my instance, I don’t have a lot of them but if you would replace sections one day it could become potentially hard to migrate.

    to be honest, that’s why I used otter blocks – because TI is usually supporting its plugins and that’s Important with the Gutenberg Blocks for the future…
    Don’t want to migrate 200+ Articles one day because certain blocks were changed.

    Plugin Author Hardeep Asrani

    (@hardeepasrani)

    7 years, 4 months ago

    We’re planning on migrating the Notice block to Section, i.e. if you’re using a Notice block then it would be automatically be converted into a Section.

    That’s why we didn’t remove the block straight, that will cause an error, so we kept it inside the plugin so people who are already using it shouldn’t face any issues.

    Gutenberg is new and still very fresh, so a lot of things happen real quick, and we have, admittedly, not been able to communicate the changes with the users, that’s why in the next major version you will see a “Welcome page” which will keep the users updated with ongoing changes and new features.

    We hurried the first version and hence ended up with 12 different blocks which made no sense for the vision and then laid down a good roadmap for the future of our plugin.

    I can say with confidence that you won’t see any more deprecations anytime soon as all the blocks are final but one.

    Plugin Card will soon be removed (not deprecated) into its own separate plugin because it is a great block, but for a different audience than Otter, so it deserves its own proper maintenance instead of relying on Otter’s vision.

    Thank you for your honest feedback, and we hope we won’t disappoint you in the future.

    PS: Here’s a little video showcasing how you can convert Notice using Section: https://www.useloom.com/share/a47d78237ce643c58c3e4688cbcda6a8

    This is a quick video so you can do way better and more advanced than this. 🙂

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Notice Block’ is closed to new replies.