Is your feature request related to a problem? Please describe.
Should be similar with https://github.com/WPChill/strong-testimonials/issues/119 , think we will create a submodule for this one so that we can use it in our main plugins and modify only once.
Describe the solution you'd like
Create a submodule framework, wpchill-welcome-banner, that will redirect the user to the welcome banner when the plugin activates. It should be a class and it's methods should generate HTML markup for the banner elements, for example:
a button method that accepts text, link and bool ( true for primary and false secondary ), that will output the button HTML element
an extension method that accepts title, text and icon for the extensions HTML element ( only title required, rest optional )
a heading method that accepts text and positioning for the headers HTML elements ( default positioning = center )
a subheading method that accepts text and positioning ( default positioning = center )
a testimonial method that accepts text, icon, name and function/company ( only text required, rest optional )
a list method that accepts an array of choices
optional :
methods for the beginning and ending of 2 and 3 columns layout
a video iframe method, which accepts YouTube video URL
The layout will be similar to the one present on the ST issue. The page will be build separately using the above class methods in order to be more customizable/subjective to each main plugin.
Is your feature request related to a problem? Please describe. Should be similar with https://github.com/WPChill/strong-testimonials/issues/119 , think we will create a submodule for this one so that we can use it in our main plugins and modify only once.
Describe the solution you'd like Create a submodule framework, wpchill-welcome-banner, that will redirect the user to the welcome banner when the plugin activates. It should be a class and it's methods should generate HTML markup for the banner elements, for example:
The layout will be similar to the one present on the ST issue. The page will be build separately using the above class methods in order to be more customizable/subjective to each main plugin.