docs(npm): add consistent README to published packages#2246
docs(npm): add consistent README to published packages#2246spike-rabbit wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
Code Review
This pull request standardizes the README files across all sub-projects to a minimal layout that directs users to the central documentation site (element.siemens.io). In addition, the build scripts in package.json have been updated to copy only the LICENSE.md file to the distribution directories, omitting the README.md files. There are no review comments, and I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
d77249d to
e0793ee
Compare
timowolf
left a comment
There was a problem hiding this comment.
I would stick to markdown syntax as much as possible and also I would not delete the documentation. This is what developers expect when getting into the readme.
73f730e to
fdc81a5
Compare
|
We should have our docs in one place: I will clean up the docs first, as I was not aware how many things are currently hidden in README files. |
fdc81a5 to
2596fb0
Compare
|
I removed modifications of existing |
Summary
Adds a consistent, minimal
README.mdto every package the lacked one.. Each one shows the Element icon, the package name as title, and a call to action linking to https://element.siemens.io.Affected published packages:
@siemens/element-ng@siemens/element-theme@siemens/element-translate-cliBuild script cleanup
Since all packages have a
README.mdwithin the project root, no need to copy it manually.It is automatically picked up by ngPackgr.
Documentation.
Examples.
Dashboards Demo.
Playwright report.
Coverage Reports:
Documentation.
Examples.
Dashboards Demo.
Playwright report.
Coverage Reports: