Skip to content

Commit 5466f2f

Browse files
author
Igor Melnikov
authored
Merge pull request #56 from magento-obsessive-owls/MAGETWO-91200-update-documentation-eap
[CMS Team 2 - Sprint 8] Update documentation for EAP, fix data migration
2 parents 3a35732 + 6e72e35 commit 5466f2f

31 files changed

+3309
-154
lines changed

README.md

Lines changed: 85 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,85 @@
1+
# magento2-page-builder
2+
3+
## PageBuilder Early Access Program
4+
5+
The PageBuilder Early Access Program (EAP) gives partners the following perks:
6+
7+
* Explore PageBuilder extension points to build custom modules and integrations for 3rd party services, such as Facebook, Instagram, etc.
8+
* Try out PageBuilder customization options and extend its functionality beyond its default features.
9+
* Preview PageBuilder to prepare a migration plan from BlueFoot 1.0 to PageBuilder.
10+
11+
**Note:**
12+
*This program should not be used to design and launch a production website using early code.*
13+
14+
## Installation
15+
16+
We offer two methods for installing PageBuilder:
17+
18+
* As a [Composer package] - use this option if you do not plan to contribute to the PageBuilder code repository
19+
* Using the [GitHub repository] - use this option to install PageBuilder from the GitHub repository and contribute to the code
20+
21+
[Composer package]: app/code/Magento/PageBuilder/docs/install.md#composer-installation
22+
[GitHub repository]: app/code/Magento/PageBuilder/docs/install.md#github-installation
23+
24+
## Developer documentation
25+
26+
This project repository contains PageBuilder developer documentation on the following topics:
27+
28+
1. [Architecture overview]
29+
1. [BlueFoot to PageBuilder data migration]
30+
1. [Third-party content type migration]
31+
1. [Iconography]
32+
1. [Module integration]
33+
1. [Additional data configuration]
34+
1. [Content type configuration]
35+
1. [How to add a new content type]
36+
1. [Events]
37+
1. [Master format]
38+
1. [Visual select]
39+
40+
[Architecture overview]: app/code/Magento/PageBuilder/docs/architecture-overview.md
41+
[BlueFoot to PageBuilder data migration]: app/code/Magento/PageBuilder/docs/bluefoot-data-migration.md
42+
[Third-party content type migration]: app/code/Magento/PageBuilder/docs/new-content-type-example.md
43+
[Iconography]: app/code/Magento/PageBuilder/docs/iconography.md
44+
[Module integration]: app/code/Magento/PageBuilder/docs/module-integration.md
45+
[Additional data configuration]: app/code/Magento/PageBuilder/docs/custom-configuration.md
46+
[Content type configuration]: app/code/Magento/PageBuilder/docs/content-type-configuration.md
47+
[How to add a new content type]: app/code/Magento/PageBuilder/docs/how-to-add-new-content-type.md
48+
[Events]: app/code/Magento/PageBuilder/docs/events.md
49+
[Master format]: app/code/Magento/PageBuilder/docs/master-format.md
50+
[Visual select]: app/code/Magento/PageBuilder/docs/visual-select.md
51+
52+
## Contribute to PageBuilder
53+
54+
We appreciate any and all contributions to PageBuilder.
55+
A good place to start is by looking at our [features roadmap] and list of [known issues].
56+
57+
If you are interested in contributing to this repository, please see our [Contribution Guide].
58+
59+
[Contribution Guide]: app/code/Magento/PageBuilder/docs/CONTRIBUTING.md
60+
[features roadmap]: app/code/Magento/PageBuilder/docs/roadmap.md#planned-features-and-functionality
61+
[known issues]: app/code/Magento/PageBuilder/docs/roadmap.md#known-issues
62+
63+
## PageBuilder updates from the Magento core team
64+
65+
The PageBuilder team updates the code every 2 weeks.
66+
**These changes may introduce breaking changes.**
67+
68+
To help you prepare for these changes, we are publishing a [roadmap] of features and issues that we are going to work on in the following months.
69+
70+
[roadmap]: app/code/Magento/PageBuilder/docs/roadmap.md
71+
72+
## Provide feedback
73+
74+
We want to hear what you think of PageBuilder!
75+
We are particularly interested on your thoughts on the following:
76+
77+
* [How would you customize PageBuilder and what do you need to accomplish this task?](https://github.com/magento/magento2-page-builder/issues/57)
78+
* [What web content API do you use or would like to see in PageBuilder?](https://github.com/magento/magento2-page-builder/issues/58)
79+
80+
To participate in technical discussions and ask questions, join us in [Slack].
81+
82+
For all other questions or requests, contact [Olena Tkacheva].
83+
84+
[Slack]: https://magentocommeng.slack.com/
85+
[Olena Tkacheva]: https://magentocommeng.slack.com/messages/@UAFV915FB

app/code/Magento/PageBuilder/Setup/DataConverter/Renderer/AdvancedSliderItem.php

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,13 +75,15 @@ public function render(array $itemData, array $additionalData = [])
7575
$overlayDivElementAttributes['class'] = 'pagebuilder-overlay pagebuilder-poster-overlay';
7676
$style = $this->styleExtractor->extractStyle($formData, ['padding']);
7777

78+
$overlayColor = 'transparent';
7879
if (isset($eavData['has_overlay']) && $eavData['has_overlay'] == 1) {
79-
$overlayDivElementAttributes['data-overlay-color'] = 'rgba(0,0,0,0.5)'; // default overlay style
80+
$overlayColor = 'rgba(0,0,0,0.5)';
8081
if ($style) {
8182
$style .= ' ';
8283
}
8384
$style .= 'background-color: rgba(0,0,0,0.5);';
8485
}
86+
$overlayDivElementAttributes['data-overlay-color'] = $overlayColor;
8587
if ($style) {
8688
$overlayDivElementAttributes['style'] = $style;
8789
}

app/code/Magento/PageBuilder/Setup/DataConverter/Renderer/SliderItem.php

Lines changed: 0 additions & 124 deletions
This file was deleted.

app/code/Magento/PageBuilder/Setup/Patch/Data/MigrateToPageBuilder.php

Lines changed: 16 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,21 +29,29 @@ class MigrateToPageBuilder implements DataPatchInterface
2929
*/
3030
private $moveImages;
3131

32+
/**
33+
* @var \Magento\Framework\App\State
34+
*/
35+
private $appState;
36+
3237
/**
3338
* Constructor
3439
*
3540
* @param \Magento\PageBuilder\Setup\ConvertBlueFootToPageBuilderFactory $convertBlueFootToPageBuilderFactory
3641
* @param ModuleDataSetupInterface $moduleDataSetup
3742
* @param MoveImages $moveImages
43+
* @param \Magento\Framework\App\State $appState
3844
*/
3945
public function __construct(
4046
\Magento\PageBuilder\Setup\ConvertBlueFootToPageBuilderFactory $convertBlueFootToPageBuilderFactory,
4147
ModuleDataSetupInterface $moduleDataSetup,
42-
MoveImages $moveImages
48+
MoveImages $moveImages,
49+
\Magento\Framework\App\State $appState
4350
) {
4451
$this->convertBlueFootToPageBuilderFactory = $convertBlueFootToPageBuilderFactory;
4552
$this->moduleDataSetup = $moduleDataSetup;
4653
$this->moveImages = $moveImages;
54+
$this->appState = $appState;
4755
}
4856

4957
/**
@@ -55,7 +63,13 @@ public function apply()
5563
{
5664
if ($this->moduleDataSetup->tableExists('gene_bluefoot_entity')) {
5765
$this->updateEavConfiguration();
58-
$this->convertBlueFootToPageBuilderFactory->create(['setup' => $this->moduleDataSetup])->convert();
66+
$convertBlueFootToPageBuilder = $this->convertBlueFootToPageBuilderFactory->create(
67+
['setup' => $this->moduleDataSetup]
68+
);
69+
$this->appState->emulateAreaCode(
70+
\Magento\Framework\App\Area::AREA_ADMINHTML,
71+
[$convertBlueFootToPageBuilder, 'convert']
72+
);
5973
$this->moveImages->move();
6074
}
6175
}
Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
# Contributing to Magento 2 code
2+
3+
## Navigation
4+
5+
1. [Introduction]
6+
2. [Installation guide]
7+
3. **Contribution guide**
8+
1. [Overview](#overview)
9+
1. [Contribution requirements](#contribution-requirements)
10+
1. [Contribution process](#contribution-process)
11+
1. [Code of Conduct](#code-of-conduct)
12+
4. [Developer documentation]
13+
5. [Roadmap and known issues]
14+
15+
[Introduction]: README.md
16+
[Installation Guide]: install.md
17+
[Contribution guide]: CONTRIBUTING.md
18+
[Developer documentation]: developer-documentation.md
19+
[Architecture overview]: architecture-overview.md
20+
[BlueFoot to PageBuilder data migration]: bluefoot-data-migration.md
21+
[Third-party content type migration]: new-content-type-example.md
22+
[Iconography]: iconography.md
23+
[Module integration]: module-integration.md
24+
[Additional data configuration]: custom-configuration.md
25+
[Content type configuration]: content-type-configuration.md
26+
[How to add a new content type]: how-to-add-new-content-type.md
27+
[Events]: events.md
28+
[Master format]: master-format.md
29+
[Visual select]: visual-select.md
30+
[Roadmap and Known Issues]: roadmap.m
31+
32+
## Overview
33+
34+
Contributions to the Magento 2 codebase are done using the fork & pull model.
35+
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”).
36+
37+
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.
38+
39+
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.
40+
41+
42+
## Contribution requirements
43+
44+
1. Contributions must adhere to [Magento coding standards](http://devdocs.magento.com/guides/v2.0/coding-standards/bk-coding-standards.html).
45+
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.
46+
3. Commits must be accompanied by meaningful commit messages.
47+
4. PRs which include bug fixing, must be accompanied with step-by-step description of how to reproduce the bug.
48+
3. PRs which include new logic or new features must be submitted along with:
49+
* Unit/integration test coverage where applicable.
50+
* Updated documentation in the module directory `app/code/PageBuilder/docs`.
51+
4. 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.
52+
5. All automated tests are passed successfully locally. After PR submitted Magento team will run builds on continuous integration environment.
53+
54+
## Contribution process
55+
56+
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”.
57+
58+
1. Search current [listed issues](https://github.com/magento/magento2-page-builder/issues) on GitHub (open or closed) and [list of known issues](roadmap.md#Known Issues) on our roadmap for similar proposals of intended contribution before starting work on a new contribution.
59+
2. Please contact us in Slack chanel if you want to work on issue from [list of known issues](roadmap.md#Known Issues).
60+
2. Review the [Contributor License Agreement](https://magento.com/legaldocuments/mca) if this is your first time contributing.
61+
3. Create and test your work.
62+
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`.
63+
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.
64+
65+
## Code of Conduct
66+
67+
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.
68+
The full text is available in the repository [Wiki](https://github.com/magento/magento2/wiki/Magento-Code-of-Conduct).
Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
# PageBuilder Module Documentation
2+
3+
PageBuilder is a Content Management System(CMS) module for Magento 2.3 and above.
4+
It replaces the default WYSIWYG Editor in the Admin area with a highly configurable drag-and-drop editing system.
5+
6+
## Navigation
7+
8+
1. **Introduction**
9+
2. [Installation guide]
10+
3. [Contribution guide]
11+
4. [Developer documentation]
12+
1. [Architecture overview]
13+
1. [BlueFoot to PageBuilder data migration]
14+
1. [Third-party content type migration]
15+
1. [Iconography]
16+
1. [Module integration]
17+
1. [Additional data configuration]
18+
1. [Content type configuration]
19+
1. [How to add a new content type]
20+
1. [Events]
21+
1. [Master format]
22+
1. [Visual select]
23+
5. [Roadmap and known issues]
24+
25+
[Introduction]: README.md
26+
[Installation Guide]: install.md
27+
[Contribution guide]: CONTRIBUTING.md
28+
[Developer documentation]: developer-documentation.md
29+
[Architecture overview]: architecture-overview.md
30+
[BlueFoot to PageBuilder data migration]: bluefoot-data-migration.md
31+
[Third-party content type migration]: new-content-type-example.md
32+
[Iconography]: iconography.md
33+
[Module integration]: module-integration.md
34+
[Additional data configuration]: custom-configuration.md
35+
[Content type configuration]: content-type-configuration.md
36+
[How to add a new content type]: how-to-add-new-content-type.md
37+
[Events]: events.md
38+
[Master format]: master-format.md
39+
[Visual select]: visual-select.md
40+
[Roadmap and Known Issues]: roadmap.md

0 commit comments

Comments
 (0)