Metadata-Version: 2.1
Name: widgetwizard
Version: 0.9.2
Summary: Widget Wizard is a Python automation module that allows you to create widget and extension code base structures for your Oracle Commerce Cloud projects.
Home-page: https://github.com/valdal14/widgetwizard
Author: Valerio D'Alessio - @valdal14
Author-email: valerio.dalessio@oracle.com
License: MIT
Description: # OCCS Widget Wizard
        
        ![Start](https://github.com/valdal14/widgetwizard/blob/master/images/bannerGitNew.jpg?raw=true "OCCS Widget Wizard")
        
        # Installation and usage
        
        <code> >>> pip3 install widgetwizard</code><br>
        <code> >>> python3</code><br>
        <code> >>> <strong>import widgetwizard.widgetwizard as ww</strong></code><br>
        <code> >>> ww.run_script()</code>
        
        # Description
        
        OCCS Widget Wizard is a Python’s automation module that allows you to create widget and extension code base structures for your Oracle Commerce Cloud projects. 
        
        Instead of repeating tedious steps to create your Oracle Commerce Cloud’s widget and extension file and folder structures you simply provide with the necessary information needed by your Oracle Commerce Cloud’s backend instance and the module will generate the structure and the basic code you need to start working on your next widget or extension. On top of that, you can also upload it directly to your Oracle Commerce Cloud’s backend instance from the wizard process itself. 
        
        # Video Tutorial
        
        [![Watch the video](https://github.com/valdal14/widgetwizard/blob/master/images/playVideo.png?raw=true)](https://youtu.be/PO--gHMWQac)
        
        # Contributing
        
        When contributing to this repository, please first discuss the change you wish to make via issue,
        email, or any other method with the owners of this repository before making a change. 
        
        Please note we have a code of conduct, please follow it in all your interactions with the project.
        
        ## Pull Request Process
        
        1. Ensure any install or build dependencies are removed before the end of the layer when doing a 
           build.
        2. Update the README.md with details of changes to the interface, this includes new environment 
           variables, exposed ports, useful file locations and container parameters.
        3. Increase the version numbers in any examples files and the README.md to the new version that this
           Pull Request would represent.
        4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you 
           do not have permission to do that, you may request the second reviewer to merge it for you.
        
        ## Code of Conduct
        
        ### Our Pledge
        
        In the interest of fostering an open and welcoming environment, we as
        contributors and maintainers pledge to making participation in our project and
        our community a harassment-free experience for everyone, regardless of age, body
        size, disability, ethnicity, gender identity and expression, level of experience,
        nationality, personal appearance, race, religion, or sexual identity and
        orientation.
        
        ### Our Standards
        
        Examples of behavior that contributes to creating a positive environment
        include:
        
        * Using welcoming and inclusive language
        * Being respectful of differing viewpoints and experiences
        * Gracefully accepting constructive criticism
        * Focusing on what is best for the community
        * Showing empathy towards other community members
        
        Examples of unacceptable behavior by participants include:
        
        * The use of sexualized language or imagery and unwelcome sexual attention or
        advances
        * Trolling, insulting/derogatory comments, and personal or political attacks
        * Public or private harassment
        * Publishing others' private information, such as a physical or electronic
          address, without explicit permission
        * Other conduct which could reasonably be considered inappropriate in a
          professional setting
        
        ### Our Responsibilities
        
        Project maintainers are responsible for clarifying the standards of acceptable
        behavior and are expected to take appropriate and fair corrective action in
        response to any instances of unacceptable behavior.
        
        Project maintainers have the right and responsibility to remove, edit, or
        reject comments, commits, code, wiki edits, issues, and other contributions
        that are not aligned to this Code of Conduct, or to ban temporarily or
        permanently any contributor for other behaviors that they deem inappropriate,
        threatening, offensive, or harmful.
        
        ### Scope
        
        This Code of Conduct applies both within project spaces and in public spaces
        when an individual is representing the project or its community. Examples of
        representing a project or community include using an official project e-mail
        address, posting via an official social media account, or acting as an appointed
        representative at an online or offline event. Representation of a project may be
        further defined and clarified by project maintainers.
        
        ### Enforcement
        
        Instances of abusive, harassing, or otherwise unacceptable behavior may be
        reported by contacting the project team. All
        complaints will be reviewed and investigated and will result in a response that
        is deemed necessary and appropriate to the circumstances. The project team is
        obligated to maintain confidentiality with regard to the reporter of an incident.
        Further details of specific enforcement policies may be posted separately.
        
        Project maintainers who do not follow or enforce the Code of Conduct in good
        faith may face temporary or permanent repercussions as determined by other
        members of the project's leadership.
Platform: UNKNOWN
Classifier: Programming Language :: Python :: 3
Classifier: License :: OSI Approved :: MIT License
Classifier: Operating System :: OS Independent
Requires-Python: >=3.7.1
Description-Content-Type: text/markdown
