Merge pull request #178 from magento-devdocs/develop

[owls] Beta documentation release

Author: davemacaulay

README.md

@@ -1,98 +1,28 @@
-# magento2-page-builder
-
-<!-- {% raw %} -->
-
 ## PageBuilder Early Access Program
 
-The PageBuilder Early Access Program (EAP) gives partners the following perks:
-
-* Explore PageBuilder extension points to build custom modules and integrations for 3rd party services, such as Facebook, Instagram, etc.
-* Try out PageBuilder customization options and extend its functionality beyond its default features.
-* Preview PageBuilder to prepare a migration plan from BlueFoot 1.0 to PageBuilder.
-
-**Note:**
-*This program should not be used to design and launch a production website using early code.*
-
-## Installation
-
-We offer one method for installing PageBuilder:
-
-* As a [Composer package] - use this option if you do not plan to contribute to the PageBuilder code repository.
-* Using the [GitHub repository] - use this option to install PageBuilder from the GitHub repository and contribute to the code.
-
-[Composer package]: docs/install-pagebuilder.md#composer-installation
-[GitHub repository]: docs/install-pagebuilder.md#github-installation
-
-<!-- {% comment %} -->
+The Page Builder Early Access Program (EAP) gives partners the following perks:
+ 
+* Explore extension points to build custom modules and integrations for 3rd party services, such as Facebook and Instagram.
+* Try out customization options and extend its functionality beyond its default features.
+* Preview to prepare a migration plan from BlueFoot 1.0 to PageBuilder.
 
 ## Developer documentation
 
-### Getting Started
-
-1. [Introduction](docs/getting-started/introduction.md)
-2. [Install Page Builder](docs/getting-started/install-pagebuilder.md)
-3. [Activate Page Builder](docs/getting-started/activate-pagebuilder.md)
-
-### Customizations
-
-* [Block chooser](docs/customizations/block-chooser.md)
-* [Full-width page layouts](docs/customizations/full-width-page-layouts.md)
-* [Responsive layouts](docs/customizations/responsive-layouts.md)
-* [Storefront customization](docs/customizations/storefront-customization.md)
-* [Visual selects](docs/customizations/visual-selects.md)
-* [Additional data configuration](docs/customizations/additional-data-configuration.md)
-* [Product conditions](docs/customizations/product-conditions.md)
-* [Server-side rendered previews](docs/customizations/server-side-rendered-previews.md)
-
-### How Tos
-
-* [How to develop a new content type](docs/how-to/how-to-develop-new-content-type.md)
-* [How to develop a container content type](docs/how-to/how-to-develop-container-content-type.md)
-* [How to use the Image Uploader](docs/how-to/how-to-use-image-uploader.md)
-* [How to add inline text editing](docs/how-to/how-to-add-inline-text-editing.md)
-* [How to add a custom toolbar](docs/how-to/how-to-add-custom-toolbar.md)
-* [How to convert product attribute fields to use Page Builder](docs/how-to/how-to-convert-product-attributes-to-use-pagebuilder.md)
-* [How to store a component master format as a widget-directive](docs/how-to/how-to-store-master-format-as-widget-directive.md)
-
-### Reference
-
-* [Architecture](docs/reference/architecture.md)
-* [Events](docs/reference/events.md)
-* [Knockout bindings](docs/reference/knockout-bindings.md)
-* [Configuration](docs/reference/configuration.md)
-* [Master format](docs/reference/master-format.md)
-
-### Migration
-
-* [Migrate from BlueFoot](docs/migration/migrate-from-bluefoot.md)
-* [Migrate custom content types from BlueFoot](docs/migration/migrate-custom-content-types-from-bluefoot.md)
-  
-<!-- {% endcomment %} -->
+We will update the developer documentation frequently during beta. Please use this link to access the latest updates: 
+[Page Builder developer documentation](https://devdocs.magedevteam.com/ds_pagebuilder/page-builder/getting-started/introduction.html)
 
 ## Contribute to PageBuilder
 
 We appreciate any and all contributions to PageBuilder. If you are interested in contributing to this repository, please see our [Contribution Guide].
 
-[Contribution Guide]: CONTRIBUTING.md
-
 ## PageBuilder updates from the Magento core team
 
-The PageBuilder team updates the code every 2 weeks.
-**These changes may introduce breaking changes.**
-
-## Provide feedback
+We will push new beta releases once a week, including work from the backlog. We don't expect any large breaking changes, but we  will communicate them to you if the need arises.
 
-We want to hear what you think of PageBuilder!
-We are particularly interested on your thoughts on the following:
+## Contact us
 
-* [How would you customize PageBuilder and what do you need to accomplish this task?](https://github.com/magento/magento2-page-builder/issues/57)
-* [What web content API do you use or would like to see in PageBuilder?](https://github.com/magento/magento2-page-builder/issues/58)
+To participate in technical discussions and ask questions, join us in [Slack], where a number of Page Builder team members are present.
 
-To participate in technical discussions and ask questions, join us in [Slack].
 
-For all other questions or requests, contact [Olena Tkacheva].
-
-[Slack]: https://magentocommeng.slack.com/
-[Olena Tkacheva]: https://magentocommeng.slack.com/messages/@UAFV915FB
-
-<!-- {% endraw %} -->
+[Contribution Guide]: CONTRIBUTING.md
+[Slack]: https://magentocommeng.slack.com/messages/GANS1R4C9

docs/CONTRIBUTING.md

@@ -0,0 +1,37 @@
+# Contributing to Magento 2 code
+
+## Overview
+
+Contributions to the Magento 2 codebase are done using the fork & pull model.
+This contribution model has contributors maintaining their own copy of the forked codebase (which can easily be synced with the main copy). The forked repository is then used to submit a request to the base repository to “pull” a set of changes (hence the phrase “pull request”).
+
+Contributions can take the form of new components/features, changes to existing features, tests, documentation (such as developer guides, user guides, examples, or specifications), bug fixes, optimizations or just good suggestions.
+
+The Magento 2 development team will review all issues and contributions submitted by the community of developers in the first in, first out order. During the review we might require clarifications from the contributor. If there is no response from the contributor for two weeks, the issue is closed.
+
+## Contribution requirements
+
+1. Contributions must adhere to [Magento coding standards](http://devdocs.magento.com/guides/v2.0/coding-standards/bk-coding-standards.html).
+2. Pull requests (PRs) must be accompanied by a meaningful description of their purpose. Comprehensive descriptions increase the chances of a pull request to be merged quickly and without additional clarification requests.
+3. Commits must be accompanied by meaningful commit messages.
+4. PRs which include bug fixing, must be accompanied with step-by-step description of how to reproduce the bug.
+5. PRs which include new logic or new features must be submitted along with:
+    * Unit/integration test coverage where applicable.
+    * Updated documentation in the `docs` directory at the root level.
+6. For large features or changes, please [open an issue](https://github.com/magento/magento2/issues) and discuss first. This may prevent duplicate or unnecessary effort, and it may gain you some additional contributors.
+7. All automated tests are passed successfully locally. After PR submitted Magento team will run builds on continuous integration environment.
+
+## Contribution process
+
+If you are a new GitHub user, we recommend that you create your own [free github account](https://github.com/signup/free). By doing that, you will be able to collaborate with the Magento 2 development team, “fork” the Magento 2 project and be able to easily send “pull requests”.
+
+1. Search current [listed issues](https://github.com/magento/magento2-page-builder/issues) on GitHub (open or closed) before starting work on a new contribution.
+2. Review the [Contributor License Agreement](https://magento.com/legaldocuments/mca) if this is your first time contributing.
+3. Create and test your work.
+4. Fork the Magento 2 repository according to [Fork a repository instructions](http://devdocs.magento.com/guides/v2.0/contributor-guide/contributing.html#fork) and when you are ready to send us a pull request – follow [Create a pull request instructions](http://devdocs.magento.com/guides/v2.0/contributor-guide/contributing.html#pull_request). Instructions written for `https://github.com/magento/magento2` repository, but they also apply to `https://github.com/magento/magento2-page-builder`.
+5. Once your contribution is received, Magento 2 development team will review the contribution and collaborate with you as needed to improve the quality of the contribution.
+
+## Code of Conduct
+
+Please note that this project is released with a Contributor Code of Conduct. We expect you to agree to its terms when participating in this project.
+The full text is available in the repository [Wiki](https://github.com/magento/magento2/wiki/Magento-Code-of-Conduct).