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

Update Docs: Pastanaga UI and Quanta #5903

Merged
merged 1 commit into from Mar 24, 2024
Merged

Conversation

jensens
Copy link
Sponsor Member

@jensens jensens commented Mar 21, 2024

After a chat with @sneridagh about Quanta, I took the information and updated the outdated page .

Copy link

netlify bot commented Mar 21, 2024

Deploy Preview for plone-components canceled.

Name Link
🔨 Latest commit 627810d
🔍 Latest deploy log https://app.netlify.com/sites/plone-components/deploys/65fc400939f824000842ab90

Copy link

netlify bot commented Mar 21, 2024

Deploy Preview for volto ready!

Name Link
🔨 Latest commit 627810d
🔍 Latest deploy log https://app.netlify.com/sites/volto/deploys/65fc400a5807da0008ad6c1d
😎 Deploy Preview https://deploy-preview-5903--volto.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@jensens jensens force-pushed the docs-styleguide-quanta-update branch 2 times, most recently from c8fdc23 to 2b20e10 Compare March 21, 2024 11:43
@jensens
Copy link
Sponsor Member Author

jensens commented Mar 21, 2024

It seems we have no news folder for documentation changes. I added a check. The prerelease script should find it anyway.

@stevepiercy
Copy link
Collaborator

The news folder for Volto moved since it became a monorepo to https://github.com/plone/volto/tree/main/packages/volto/news. Docs are for all the packages in the repo, which is why docs/ remains at the repo root.

@jensens
Copy link
Sponsor Member Author

jensens commented Mar 21, 2024

The news folder for Volto moved since it became a monorepo to https://github.com/plone/volto/tree/main/packages/volto/news. Docs are for all the packages in the repo, which is why docs/ remains at the repo root.

This is why I added an allow-check for docs and looked how prereleaser.js works, which globs'**/news/*.*(breaking|feature|bugfix|documentation|internal)', finding the docs/news then as well. This should be fine this way and then all news folders are in it's place.

Copy link
Collaborator

@stevepiercy stevepiercy left a comment

Choose a reason for hiding this comment

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

See comments about reverting check and where to put news items.

Otherwise, a few minor grammar and syntax suggestions.

Thank you for taking this on. It really needed some polishing from someone who knew the history.

.github/workflows/changelog.yml Outdated Show resolved Hide resolved
git fetch --no-tags origin main
towncrier check --compare-with origin/main --dir docs
env:
BASE_BRANCH: ${{ github.base_ref }}
Copy link
Collaborator

Choose a reason for hiding this comment

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

Please revert.

Copy link
Sponsor Member Author

Choose a reason for hiding this comment

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

so, where to put then the changelog for docs if not under /docs/news?

Copy link
Collaborator

Choose a reason for hiding this comment

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

packages/volto/news

Copy link
Collaborator

Choose a reason for hiding this comment

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

...or if you update docs for a specific package, then in its packages/package_name/news.

Copy link
Sponsor Member Author

Choose a reason for hiding this comment

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

Done, moved and cleaned the mess up into one commit.

docs/source/contributing/style-guide.md Outdated Show resolved Hide resolved
docs/source/contributing/style-guide.md Outdated Show resolved Hide resolved
docs/source/contributing/style-guide.md Outdated Show resolved Hide resolved
docs/source/contributing/style-guide.md Outdated Show resolved Hide resolved
docs/source/contributing/style-guide.md Outdated Show resolved Hide resolved
docs/source/contributing/style-guide.md Outdated Show resolved Hide resolved
docs/source/contributing/style-guide.md Outdated Show resolved Hide resolved
@stevepiercy
Copy link
Collaborator

This is why I added an allow-check for docs and looked how prereleaser.js works, which globs'**/news/*.*(breaking|feature|bugfix|documentation|internal)', finding the docs/news then as well. This should be fine this way and then all news folders are in it's place.

We already put documentation change log entries in the news items directory in packages/volto/news. We don't need another check that will not be used. It's also out of scope for this pull request, and should be discussed amongst the Volto team before making changes of this nature.

@jensens jensens force-pushed the docs-styleguide-quanta-update branch 2 times, most recently from b07f9e9 to bc58c2d Compare March 21, 2024 14:10
Co-authored-by: Steve Piercy <web@stevepiercy.com>
@jensens jensens force-pushed the docs-styleguide-quanta-update branch from bc58c2d to 627810d Compare March 21, 2024 14:11
@jensens
Copy link
Sponsor Member Author

jensens commented Mar 21, 2024

We already put documentation change log entries in the news items directory in packages/volto/news

Since the placement of the news files are very different from other parts of Plone, I would like to see an explanation at https://6.docs.plone.org/volto/contributing/index.html#change-log-entry - its not obvious.

@stevepiercy
Copy link
Collaborator

We already put documentation change log entries in the news items directory in packages/volto/news

Since the placement of the news files are very different from other parts of Plone, I would like to see an explanation at https://6.docs.plone.org/volto/contributing/index.html#change-log-entry - its not obvious.

Screenshot 2024-03-21 at 2 44 15 PM

The "see also" link goes to https://6.docs.plone.org/contributing/index.html#change-log-entry which provides sufficient detail.

For Volto, its repository is in a monorepo structure, consisting of several packages in the packages folder. Thus for Volto and its packages, change log entries should be created in packages/PACKAGE_NAME/news/, which is the root of the package.

I can add your suggestion, if you still think it would be beneficial. I would turn it into a snippet and include it, so that we don't use copy-paste. Please let me know. Thank you!

Copy link
Collaborator

@stevepiercy stevepiercy left a comment

Choose a reason for hiding this comment

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

This is professionally and well-written. Thank you!

@stevepiercy
Copy link
Collaborator

@sneridagh I'd like your review for accuracy, and let you take the merge honors.

@jensens
Copy link
Sponsor Member Author

jensens commented Mar 22, 2024

We already put documentation change log entries in the news items directory in packages/volto/news

Since the placement of the news files are very different from other parts of Plone, I would like to see an explanation at https://6.docs.plone.org/volto/contributing/index.html#change-log-entry - its not obvious.

Screenshot 2024-03-21 at 2 44 15 PM

The "see also" link goes to https://6.docs.plone.org/contributing/index.html#change-log-entry which provides sufficient detail.

For Volto, its repository is in a monorepo structure, consisting of several packages in the packages folder. Thus for Volto and its packages, change log entries should be created in packages/PACKAGE_NAME/news/, which is the root of the package.

I can add your suggestion, if you still think it would be beneficial. I would turn it into a snippet and include it, so that we don't use copy-paste. Please let me know. Thank you!

Something like "in case of setup/CI/CD or documentation changes not bound to a specific package, use the PACKAGE_NAME=volto"?

@sneridagh
Copy link
Member

Something like "in case of setup/CI/CD or documentation changes not bound to a specific package, use the PACKAGE_NAME=volto"?

I'd be +1 on clarifying this.

@jensens very well written, it's just awesome. Thanks a lot!

@sneridagh sneridagh merged commit 40526aa into main Mar 24, 2024
74 checks passed
@sneridagh sneridagh deleted the docs-styleguide-quanta-update branch March 24, 2024 09:41
sneridagh added a commit that referenced this pull request Apr 16, 2024
* main: (21 commits)
  Use fieldset `id` instead of the fieldset `title` in Form when rendering the Field component (#5921)
  Fix registry wrong default primitive type (#5925)
  Release @plone/types 1.0.0-alpha.8
  Improve types for APIExpanders, export all (#5918)
  Missing step in storybook migration (#5913)
  Push missing .d.ts files
  Release 18.0.0-alpha.25
  Release generate-volto 9.0.0-alpha.14
  Update Docs: Pastanaga UI and Quanta (#5903)
  Upgrade to StoryBook 8 (#5912)
  Fix Storybook in app gen for Volto 18 (#5911)
  Release 18.0.0-alpha.24
  Upgrade `@typescript-eslint` (#5910)
  Add new cypress helper for slate `getSlateEditorAndType` (#5909)
  Add id attributes to discussions container and individual comments (#5905)
  Move testing-library cypress commands import to inner commands so it can be imported (#5906)
  Release 18.0.0-alpha.23
  Release @plone/registry 1.5.4
  Improve the usage of RAZZLE_JEST_CONFIG (#5901)
  fix reordering of slots function (#5840)
  ...
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.

None yet

3 participants