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

Contributors: move to sites, change context of use #2459

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Garneauma
Copy link
Contributor

  • Moved Cotnributors component to Sites section
  • Updated Page details component to include Contributors component
  • Updated Topic template with new Contributors location

Related to WET-505

@Garneauma
Copy link
Contributor Author

Pre-approved upon successful review.

Copy link
Member

@duboisp duboisp left a comment

Choose a reason for hiding this comment

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

Todo:

  • Centralize sample inside the contributor component.
  • (Optional) remove the "gc-" prefix in the file/folder name for the contributor component
  • Update the contributor component documentation to add more emphasis on the breaking change + migration instruction.
  • Page details - move demoted pattern in demoted folder
  • For "contributor" component, make it a minor version for now (v1.1) because both are still ok, but identify the version 1.0 as demoted. We will increase the major version when we will switch the v1.0 from "demoted" into "deprecated" state.

This change is:

  • Minor change for contributor component - Add new pattern where located in the page details section
  • Minor change for page details component - Add new pattern that include the contributor component
  • Minor change for Topic template - Add new pattern that include the new page details with the contributor component
  • Minor change for the "Topic" template - Add new pattern that implement page-details v 3.3 where the contributor component are in the page-details section
  • We will perform a major change to those component, when we will switch them from "demoted" into "deprecated" at our next major release

Copy link
Member

Choose a reason for hiding this comment

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

Please move it in sites/gc-contributors/samples/gc-contributors.html

It is specific to gc-contributor and we need to keep all component specific item in the same base folder

And please remove it here: _includes/components/gc-contributors/gc-contributors.html

Comment on lines +67 to +68
"_:implement_contributors",
"_:implement_contributors_gcweb"
Copy link
Member

Choose a reason for hiding this comment

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

We need an additional "implementation" for the migration instruction from v1 to v2.

Where it mention:

  • Date of when this is applicable, use December 2024 like in the history.
  • Describe the breaking change and mention there is an impact on page details component and link to it. Like require minimal version 3.3 of page details component.

@@ -81,7 +86,7 @@
"implementation": [
{
"@id": "_:implement_contributors",
"iteration": "_:iteration_contributors_2",
"iteration": "_:iteration_contributors_3",
Copy link
Member

Choose a reason for hiding this comment

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

For this implementation, please be clear in the instruction this need to be added in the page details section and do require the implementation of page details v3.3 + a link if possible to page details docs.

{
"@id": "_:iteration_contributors_3",
"name": "Contributors - Iteration 3",
"date": "2024-05",
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
"date": "2024-05",
"date": "2024-12",

"date": "2024-05",
"detectableBy": ".pagedetails .gc-contributors",
"breaking": [
"Changed context of use in the page. The component should be located in the page details section above the date modified component."
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
"Changed context of use in the page. The component should be located in the page details section above the date modified component."
"Changed context of use in the page. The component must be located in the page details section above the date modified component."

Note: It is not an optional location.

Copy link
Member

Choose a reason for hiding this comment

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

Move to "demoted" and identify in the docs as "demoted"

Copy link
Member

Choose a reason for hiding this comment

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

Move to "demoted" and identify in the docs as "demoted"

@@ -17,7 +17,7 @@
"modified": "2024-08-27",
"componentName": "topic",
"status": "stable",
"version": "2.1",
"version": "3.0",
Copy link
Member

Choose a reason for hiding this comment

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

Set a minor version for now (v2.2) as we do allow both pattern for now, but demote the version 2.1

Copy link
Member

Choose a reason for hiding this comment

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

Need implementation with migration instruction from version 2.0 (demoted) to v2.1 (stable)

@@ -194,7 +202,7 @@
},
{
"@id": "_:implement_topic_aem",
"iteration": "_:iteration_topic_3",
"iteration": "_:iteration_topic_4",
Copy link
Member

Choose a reason for hiding this comment

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

For this one, add an instruction note that mention about the "Contributor" component that are located in the "page details" configuration

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.

2 participants