Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IBX-8917: Content fixes in Developer Documentation #2506

Merged
merged 80 commits into from
Nov 28, 2024
Merged

Conversation

julitafalcondusza
Copy link
Contributor

@julitafalcondusza julitafalcondusza commented Oct 3, 2024

Question Answer
JIRA Ticket (https://issues.ibexa.co/browse/IBX-8917)
Versions 4.6+

Content fixes in Developer Documentation

Checklist

  • Text renders correctly
  • Text has been checked with vale
  • Description metadata is up to date

@julitafalcondusza julitafalcondusza marked this pull request as ready for review October 17, 2024 13:14
@adamwojs
Copy link
Member

@julitafalcondusza rebase is needed here

@mnocon mnocon mentioned this pull request Oct 29, 2024
4 tasks
Copy link
Contributor

@mnocon mnocon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lots of work here, good job on preparing this - but there are some things to fix before we merge this:

  1. Almost the whole Search reference is marked as Commerce only, this needs to be reverted
  2. You're also changing the licence of a font we're using - let's revert it
  3. Some includes have broken after the headers have been changed to use variables
  4. There is one repeating error - a sentence starting with they're (lowercase). Please review this as well, as I'm not sure if I found all the occurances of this
  5. In some places you're removing the dangling comma from card includes - but keeping it is a good practice, let's bring them back.
  6. Changes to PHP API Reference will be lost when it's regenerated - and the code is not adjusted. Let's revert them as well (or create PRs fixing them in the code as a follow-up).
  7. Have you regenerated the REST API reference, are the HTML changes to it consistent with the changes to the RAML files?

docs/administration/admin_panel/segments_admin_panel.md Outdated Show resolved Hide resolved
docs/administration/back_office/content_tree.md Outdated Show resolved Hide resolved
docs/administration/back_office/notifications.md Outdated Show resolved Hide resolved
docs/administration/content_organization/object_states.md Outdated Show resolved Hide resolved
docs/permissions/permission_use_cases.md Outdated Show resolved Hide resolved
@julitafalcondusza
Copy link
Contributor Author

Lots of work here, good job on preparing this - but there are some things to fix before we merge this:

  1. Almost the whole Search reference is marked as Commerce only, this needs to be reverted
  2. You're also changing the licence of a font we're using - let's revert it
  3. Some includes have broken after the headers have been changed to use variables
  4. There is one repeating error - a sentence starting with they're (lowercase). Please review this as well, as I'm not sure if I found all the occurances of this
  5. In some places you're removing the dangling comma from card includes - but keeping it is a good practice, let's bring them back.
  6. Changes to PHP API Reference will be lost when it's regenerated - and the code is not adjusted. Let's revert them as well (or create PRs fixing them in the code as a follow-up).
  7. Have you regenerated the REST API reference, are the HTML changes to it consistent with the changes to the RAML files?
  1. Reverted ✅
  2. Reverted ✅
  3. Fixed ✅
  4. Reviewed, fixed missed occurrences. ✅
  5. Fixed ✅
  6. PHP API Reference files are now excluded from PR (changes are reverted). ✅
  7. REST API Reference files are now excluded from PR (changes are reverted). ✅

6&7 - we can think about separate PR with the fixes in .raml and .html files.

Copy link
Contributor

@mnocon mnocon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

Copy link
Contributor

@dabrt dabrt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor issues reported offline

@julitafalcondusza julitafalcondusza merged commit cceaa73 into master Nov 28, 2024
4 of 5 checks passed
@julitafalcondusza julitafalcondusza deleted the IBX-8917 branch November 28, 2024 13:36
Copy link
Contributor

@adriendupuis adriendupuis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I end my review at docs/personalization/api_reference/tracking_api.md as the PR seems already merged. No big changes asked.

@@ -7,7 +7,8 @@ edition: experience

## What is page

[Page](pages.md) is a block-based type of content. You can create and modify it with a visual drag-and-drop editor - Page Builder.
[Page](pages.md) is a block-based type of content.
You can create and modify it with a visual drag-and-drop editor - Page Builder.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
You can create and modify it with a visual drag-and-drop editor - Page Builder.
You can create and modify it with a visual drag-and-drop editor - the Page Builder.

@@ -8,8 +8,7 @@ React App block allows an editor to embed a preconfigured React application into
It's configured in YAML files, under the `ibexa_fieldtype_page` key.
Page block configuration isn't SiteAccess-aware.

Another element of React App Block is `\Ibexa\FieldTypePage\FieldType\Page\Block\Event\Listener\ReactBlock` Listener
which adds component and props variables.
Another element of React App Block is `\Ibexa\FieldTypePage\FieldType\Page\Block\Event\Listener\ReactBlock` Listener which adds component and props variables.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Another element of React App Block is `\Ibexa\FieldTypePage\FieldType\Page\Block\Event\Listener\ReactBlock` Listener which adds component and props variables.
Another element of React App Block is `\Ibexa\FieldTypePage\FieldType\Page\Block\Event\Listener\ReactBlock` Listener which adds component and props variables.

@@ -34,7 +35,7 @@ With a help of documentation and trainings, any developer familiar with Symfony

Version control systems and environment variables allow you to deploy your extensions and settings on several environments, such as [Ibexa Cloud](ibexa_cloud_guide.md).

[[= product_name_com =]] is built on [[[= product_name_exp =]]](ibexa_experience.md) and includes all bundles, APIs, and features that come with both [Headless](ibexa_headless.md#core-features) and [Experience](ibexa_experience.md#core-features) editions.
[[= product_name_com =]] is built on [Ibexa Experience](ibexa_experience.md) and includes all bundles, APIs, and features that come with both [Headless](ibexa_headless.md#core-features) and [Experience](ibexa_experience.md#core-features) editions.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one was properly working and might not be necessary.

Suggested change
[[= product_name_com =]] is built on [Ibexa Experience](ibexa_experience.md) and includes all bundles, APIs, and features that come with both [Headless](ibexa_headless.md#core-features) and [Experience](ibexa_experience.md#core-features) editions.
[[= product_name_com =]] is built on [[[= product_name_exp =]]](ibexa_experience.md) and includes all bundles, APIs, and features that come with both [Headless](ibexa_headless.md#core-features) and [Experience](ibexa_experience.md#core-features) editions.

Are we authorized to nickname "Ibexa Experience" as "Experience" and "Ibexa Headless" as "Headless"? (I would say that we are if not overused.)

julitafalcondusza added a commit that referenced this pull request Nov 28, 2024
* Content updates, capitalization fixes

* New fixes

* New fixes

* New fixes

* New fixes

* Fixes

* Typo fix

* Field -> field

* Capitalization fixes

* Fixes

* Fixes

* Fixes

* Fixes

* Fixes

* Fixes

* Variables fix

* More fixes

* More fixes

* More fixes

* Batch of fixes

* Tabs fixes

* 'Will' fixes

* 'Won't' fixes

* 'e.g.' fixes

* Fixes in 'back office' section

* Fixes in 'configuration' section

* Fixes in 'content organization' section

* Fixes

* Fixes in'api' section

* Fixes in 'cdp' section

* Fixes in 'commerce'

* Fixes in 'content management' section

* Fixes in 'customer management'

* Fixes in 'getting started' section

* Fixes in 'ibexa cloud'

* Fixes in 'ibexa engage' section

* Fixes in 'ibexa products' section

* Fixes in 'cache' section

* Fixes in 'clustering'

* Fixes in 'security'

* Fixes in 'infrastructure' section

* Fixes in 'languages'

* Fixes in 'site factory and siteaccess' sections

* Fixes in 'multisite'

* Fixes in 'permissions' section

* Fixes in 'personalization'

* Fixes in 'pim'

* Fixes in 'resources'

* Fixes in 'search references' and aggregations

* Fixes in 'search'

* Fixes in 'snippets'

* Fixes in 'templates'

* Fixes in 'tutorials'

* Fixes in 'users'

* Fixes - 'field'

* Fixes - 'section'

* Fixes - 'location'

* Fixes - 'subtree'

* Fixes - 'value object'

* Fixes - 'search criteria'

* Fixes - 'product'

* Fixes - 'sort clauses'

* Fixes - 'elasticsearch'

* Fix 'storefront'

* Fixes - 'etc.'

* Fixes - 'policies'

* Fixes

* Fixes

* Fixes

* Fixes

* Fixes

* Links fixed (variables removed)

* Fixes after review

* Fixes after review

* Revert changes in api .raml and .html files

* fix

* fixes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants