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

Feat/init vitepress docs #319

Merged
merged 5 commits into from
Dec 9, 2024
Merged

Feat/init vitepress docs #319

merged 5 commits into from
Dec 9, 2024

Conversation

simonhir
Copy link
Member

@simonhir simonhir commented Dec 9, 2024

Description

Initialize Vitepress from refarch-templates

Summary by CodeRabbit

Release Notes

  • New Features

    • Introduced a new GitHub Actions workflow for deploying the VitePress site to GitHub Pages.
    • Added a comprehensive .gitignore file to enhance project organization.
    • Created a new configuration file for VitePress, establishing site structure and navigation.
    • Launched new documentation sections: "Runtime API Examples" and "Markdown Extension Examples".
    • Updated home layout for the documentation site, featuring a hero section and a features list.
  • Configuration Changes

    • Added a new .npmrc configuration option for improved lockfile management.
    • Established a package.json file with scripts for development, building, and previewing the project.

@simonhir simonhir self-assigned this Dec 9, 2024
@simonhir simonhir requested a review from a team as a code owner December 9, 2024 10:49
@simonhir simonhir changed the title Feat/init vitepress Feat/init vitepress docs Dec 9, 2024
Copy link

coderabbitai bot commented Dec 9, 2024

Warning

Rate limit exceeded

@simonhir has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 22 minutes and 56 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between a900d72 and bd3d534.

⛔ Files ignored due to path filters (1)
  • docs/package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • docs/package.json (1 hunks)

Walkthrough

This pull request introduces several changes to enhance the VitePress documentation site for the "RefArch" project. A new GitHub Actions workflow for deploying the site to GitHub Pages is added. Additionally, comprehensive .gitignore, .npmrc, and package.json files are created to manage dependencies and ignore unnecessary files. Configuration for VitePress is established, along with new documentation pages covering API examples and markdown extensions, improving the site's structure and content.

Changes

File Path Change Summary
.github/workflows/deploy_docs.yaml New workflow added for deploying VitePress site to GitHub Pages, triggered on main branch pushes.
docs/.gitignore New .gitignore file created to exclude various build artifacts and IDE-specific files.
docs/.npmrc Added configuration option omit-lockfile-registry-resolved=true to control lockfile contents.
docs/.vitepress/config.mts New configuration file for VitePress, setting up site title, theme, navigation, and Mermaid plugin.
docs/api-examples.md New section added for "Runtime API Examples," demonstrating usage of useData() API with code snippets.
docs/index.md New home layout introduced with project name, description, tagline, and features section.
docs/markdown-examples.md New documentation page created for "Markdown Extension Examples," showcasing built-in markdown features.
docs/package.json New package.json file created with scripts for development, build, and preview, along with dependencies.

Poem

🐰 In the garden of code, we hop with glee,
New workflows and docs, as bright as can be!
With VitePress we build, our knowledge to share,
Ignoring the clutter, with love and with care.
So let’s celebrate, with a leap and a bound,
For every new change, a treasure we've found! 🌼


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot added Type: Documentation The issue contains work for the documentation Type: Feature The issue is a feature labels Dec 9, 2024
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 12

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE

📥 Commits

Reviewing files that changed from the base of the PR and between a2e2b7d and a900d72.

⛔ Files ignored due to path filters (1)
  • docs/package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (8)
  • .github/workflows/deploy_docs.yaml (1 hunks)
  • docs/.gitignore (1 hunks)
  • docs/.npmrc (1 hunks)
  • docs/.vitepress/config.mts (1 hunks)
  • docs/api-examples.md (1 hunks)
  • docs/index.md (1 hunks)
  • docs/markdown-examples.md (1 hunks)
  • docs/package.json (1 hunks)
🧰 Additional context used
🪛 Markdownlint (0.35.0)
docs/markdown-examples.md

87-87: Expected: 1; Actual: 2
Multiple consecutive blank lines

(MD012, no-multiple-blanks)


9-9: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)


23-23: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)


37-37: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)


61-61: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)


93-93: null
Files should end with a single newline character

(MD047, single-trailing-newline)

docs/api-examples.md

38-38: Expected: 1; Actual: 0; Below
Headings should be surrounded by blank lines

(MD022, blanks-around-headings)


41-41: Expected: 1; Actual: 0; Below
Headings should be surrounded by blank lines

(MD022, blanks-around-headings)


44-44: Expected: 1; Actual: 0; Below
Headings should be surrounded by blank lines

(MD022, blanks-around-headings)


30-30: Element: script
Inline HTML

(MD033, no-inline-html)


39-39: Element: pre
Inline HTML

(MD033, no-inline-html)


42-42: Element: pre
Inline HTML

(MD033, no-inline-html)


45-45: Element: pre
Inline HTML

(MD033, no-inline-html)

🔇 Additional comments (3)
docs/.npmrc (1)

1-2: LGTM! Good practice for lockfile management.

The configuration to omit resolved registry URLs from the lockfile enhances security and portability. The comment clearly explains the purpose.

docs/markdown-examples.md (2)

35-82: LGTM! Custom containers section is comprehensive.

The section effectively demonstrates all standard container types with clear input/output examples.

🧰 Tools
🪛 Markdownlint (0.35.0)

37-37: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)


61-61: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)


83-86: LGTM! Good reference to full documentation.

docs/package.json Show resolved Hide resolved
docs/package.json Show resolved Hide resolved
.github/workflows/deploy_docs.yaml Outdated Show resolved Hide resolved
.github/workflows/deploy_docs.yaml Outdated Show resolved Hide resolved
docs/.vitepress/config.mts Show resolved Hide resolved
docs/api-examples.md Show resolved Hide resolved
docs/api-examples.md Show resolved Hide resolved
docs/markdown-examples.md Show resolved Hide resolved
docs/markdown-examples.md Show resolved Hide resolved
docs/.gitignore Show resolved Hide resolved
devtobi
devtobi previously approved these changes Dec 9, 2024
Copy link
Member

@devtobi devtobi left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Member

@devtobi devtobi left a comment

Choose a reason for hiding this comment

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

LGTM

@simonhir simonhir merged commit 159ba4a into main Dec 9, 2024
11 checks passed
@simonhir simonhir deleted the feat/init-vitepress branch December 9, 2024 12:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Documentation The issue contains work for the documentation Type: Feature The issue is a feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants