Skip to content

feat: implement new semantic-release documentation site#2

Merged
babblebey merged 45 commits into
mainfrom
feat/new
Mar 14, 2026
Merged

feat: implement new semantic-release documentation site#2
babblebey merged 45 commits into
mainfrom
feat/new

Conversation

@babblebey

@babblebey babblebey commented Mar 9, 2026

Copy link
Copy Markdown
Member

This pull request introduces a major reorganization and modernization of the documentation site, shifting from gitbook to a more non-service tied and custom framework by implementing @withastro and integrating @astrojs/starlight.

Other Changes

  • Introduced a lint github workflow for code quality

Screencast/Screenshot

screen-capture.28.webm

babblebey added 30 commits March 7, 2026 16:12
- Added package.json for project dependencies and scripts
- Included tsconfig.json for TypeScript configuration
…ssues

- Documented permission errors when publishing packages.
- Explained the impact of squashed commits on semantic-release.
- Provided guidance on resolving `reference already exists` errors when pushing tags.
- Added instructions for recovering from lost releases after `git push --force`.

feat: create CI configuration guide for semantic-release

- Outlined the importance of running semantic-release after all tests pass.
- Listed CI services that support this configuration.
- Explained authentication requirements for pushing to remote repositories.

feat: introduce comprehensive configuration documentation

- Detailed the configuration options available for semantic-release.
- Explained how to set up configuration files and CLI arguments.
- Provided examples for configuring branches, repository URLs, and plugins.

feat: establish getting started guide for semantic-release

- Created a step-by-step guide for installing and configuring semantic-release.

feat: outline installation methods for semantic-release

- Recommended global installation via npx for CI environments.
- Discussed the implications of local installation and dependency management.

feat: document plugins and their configuration in semantic-release

- Explained the role of plugins in the release process.
- Listed default plugins and how to install additional ones.
- Provided examples of plugin declaration and execution order.

feat: introduce shareable configurations for semantic-release

- Explained the concept of shareable configurations and how to use them.

feat: detail release workflow configuration for semantic-release

- Described the management of complex release workflows with multiple branches.
- Explained branch types and their properties for effective release management.
- Refactor the highlights section in intro.md for better readability.
- Update CI configurations index.md to improve formatting.
- Enhance git authentication SSH keys documentation for clarity.
- Standardize formatting in git-hosted services index.md.
- Improve distribution channels recipe formatting for consistency.
- Refine release workflow recipes for better structure.
- Update FAQ.md for improved clarity and consistency.
- Enhance resources.md with better formatting for video and article lists.
- Improve CI configuration documentation for better readability.
- Standardize configuration documentation for semantic-release options.
- Update installation.md for clearer instructions on global installation.
- Refactor plugins.md for better readability and structure.
- Enhance workflow-configuration.md for improved clarity and consistency.
@vercel

vercel Bot commented Mar 9, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
semantic-release-docs Ready Ready Preview, Comment Mar 14, 2026 6:19pm

Request Review

@babblebey babblebey changed the title feat: implement new semantic-release documentation feat: implement new semantic-release documentation site Mar 9, 2026
@babblebey babblebey requested a review from travi March 9, 2026 05:49
@travi

travi commented Mar 13, 2026

Copy link
Copy Markdown
Member
  • Introduced a new astro.config.mjs file
  • Added a .prettierrc.mjs file

initial suggestion before diving deeper: lets avoid .mjs extensions. since the project is ESM, the "m" can be dropped

@travi travi left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

this all looks good to me.

i havent tried to start it locally to see it rendered. is that the simplest way to see how things look? looking forward to getting hosting setup so we could have a PR preview deploy to take a look at

the one question i have is whether the embedded styles and js could be extracted to separate files or not. i'm not up to speed on astro or tailwind, so you might tell me that it is common convention in those cases, but i still prefer separate files if that does conflict with things

Comment thread src/assets/hero.png

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

interesting update to the logo :D

@babblebey babblebey Mar 13, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

We already are deployed actually... currently sharing the @hearts vercel account pending the while we get a pro account from Vercel.... and the preview for this particular PR is https://semantic-release-docs-git-feat-new-hearts.vercel.app/

Preview, Comment

Link's in the Preview text on the vercel's PR comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Link's in the Preview text on the vercel's PR comment

🤦🏼 totally overlooked that comment, haha. thanks for the clarity

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

i like it 👍🏼

@babblebey babblebey marked this pull request as ready for review March 14, 2026 18:15
@babblebey

Copy link
Copy Markdown
Member Author

i have is whether the embedded styles and js could be extracted to separate files or not. i'm not up to speed on astro or tailwind

The embedded style/js-script is kinda convention for astro, think it like a way of containing a needed interactivity within a component if needed for hydration.

More like how interactivity is contained in a .jsx file that's the how to add interactivity to .astro..

YES of-course you can externalise and import but while you can import .../style.css in the frontmatter for css to an astro component.... it will have be within the <script>import ../script.js</script> or <script src="../scripts.js"></script> tag at the bottom of the astro file still if you're import external js interaction to an astro component if you want it hydrated.

@babblebey babblebey merged commit 7e86246 into main Mar 14, 2026
4 checks passed
@babblebey babblebey deleted the feat/new branch March 14, 2026 19:21
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