Skip to content

docs: updates to make commands#9529

Merged
mendonk merged 7 commits into
mainfrom
docs-lfoss-1905
Sep 3, 2025
Merged

docs: updates to make commands#9529
mendonk merged 7 commits into
mainfrom
docs-lfoss-1905

Conversation

@mendonk
Copy link
Copy Markdown
Collaborator

@mendonk mendonk commented Aug 25, 2025

Summary by CodeRabbit

  • Documentation
    • Overhauled development setup guide: clarified environment initialization, added a one-step quick-start command, and separated build/run workflows.
    • Added notes on optional pre-commit hooks.
    • Expanded documentation build instructions with Dev Container caveats and explicit host-based steps.
    • Updated contributor guide to explain differences between common commands and hot-reload workflow.
    • Removed outdated startup output and refined headings/wording, including clearer navigation to local docs.

@mendonk mendonk self-assigned this Aug 25, 2025
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Aug 25, 2025

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

Documentation updates restructure development workflow guidance: decouple init from build/run, add a quick-start make target, clarify command differences, and add dev container notes for docs. Edits are limited to DEVELOPMENT.md and a contributing guide MDX file.

Changes

Cohort / File(s) Summary
Development workflow guide
DEVELOPMENT.md
Rewrites setup and run instructions: init installs dependencies and pre-commit hooks; introduces make run_cli as one-step build/start; reorganizes post-init options; removes startup example output; adds optional pre-commit section; expands docs build steps with host/dev-container notes.
Contributing docs updates
docs/docs/Contributing/contributing-how-to-contribute.mdx
Adds admonitions: clarifies differences between make init, make run_cli, and hot-reload flow; advises building docs from host when using dev containers.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested labels

documentation, size:L, lgtm

Suggested reviewers

  • edwinjosechittilappilly
  • aimurphy
  • mfortman11
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch docs-lfoss-1905

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore or @coderabbit 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.

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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 the documentation Improvements or additions to documentation label Aug 25, 2025
@github-actions

This comment has been minimized.

@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Aug 25, 2025
Copy link
Copy Markdown
Contributor

@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: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
docs/docs/Contributing/contributing-how-to-contribute.mdx (1)

1-4: Add required frontmatter description field

Per docs guidelines, every page needs at least title and description in frontmatter. This file is missing description. Add a concise sentence that reflects the page’s purpose for SEO and previews.

Apply this diff:

 ---
 title: Contribute to Langflow
+description: Learn how to contribute to Langflow, set up the development environment, run from source, and build the documentation.
 slug: /contributing-how-to-contribute
 ---
🧹 Nitpick comments (2)
DEVELOPMENT.md (2)

60-66: Grammar: “set up” (verb), not “setup”

Minor wording fix for clarity and correctness.

Apply this diff:

-To setup and validate the initial environment, run:
+To set up and validate the initial environment, run:

170-171: Fix markdownlint MD034: wrap bare URL

Wrap the URL to satisfy markdownlint and render consistently.

Apply this diff:

-Navigate to http://localhost:3001/ in a browser and view the documentation. Documentation updates will be visible as they are saved, though sometimes the browser page will also need to be refreshed.
+Navigate to <http://localhost:3001/> in a browser and view the documentation. Documentation updates will be visible as they are saved, though sometimes the browser page will also need to be refreshed.
📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 9ae41d6 and 67f9b09.

📒 Files selected for processing (2)
  • DEVELOPMENT.md (4 hunks)
  • docs/docs/Contributing/contributing-how-to-contribute.mdx (2 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
docs/docs/**/*.{md,mdx}

📄 CodeRabbit inference engine (.cursor/rules/docs_development.mdc)

docs/docs/**/*.{md,mdx}: All documentation content must be written in Markdown or MDX files located under docs/docs/, following the prescribed directory structure for guides, reference, how-to, concepts, and API documentation.
All documentation Markdown and MDX files must begin with a frontmatter block including at least title and description fields.
Use admonitions (:::tip, :::warning, :::danger) in Markdown/MDX files to highlight important information, warnings, or critical issues.
All images referenced in documentation must include descriptive alt text for accessibility.
All code examples included in documentation must be tested and verified to work as shown.
Internal links in documentation must be functional and not broken.
Content must follow the style guide: professional but approachable tone, second person voice, present tense, short paragraphs, sentence case headers, inline code with backticks, bold for UI elements, italic for emphasis, and parallel structure in lists.
Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.

Files:

  • docs/docs/Contributing/contributing-how-to-contribute.mdx
🧠 Learnings (6)
📚 Learning: 2025-06-23T12:46:29.953Z
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: The documentation site is built and served locally using 'yarn build' and 'yarn serve', and is automatically deployed on commit to the main branch.

Applied to files:

  • DEVELOPMENT.md
  • docs/docs/Contributing/contributing-how-to-contribute.mdx
📚 Learning: 2025-07-18T18:26:42.027Z
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: All documentation changes must be built and served locally using yarn build and yarn serve before deployment.

Applied to files:

  • DEVELOPMENT.md
  • docs/docs/Contributing/contributing-how-to-contribute.mdx
📚 Learning: 2025-06-23T12:46:29.953Z
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.

Applied to files:

  • DEVELOPMENT.md
📚 Learning: 2025-07-18T18:26:42.027Z
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Documentation is automatically deployed on commit to the main branch; build artifacts are output to the build/ directory and served via CDN.

Applied to files:

  • DEVELOPMENT.md
  • docs/docs/Contributing/contributing-how-to-contribute.mdx
📚 Learning: 2025-07-18T18:26:42.027Z
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Content must follow the style guide: professional but approachable tone, second person voice, present tense, short paragraphs, sentence case headers, inline code with backticks, bold for UI elements, italic for emphasis, and parallel structure in lists.

Applied to files:

  • docs/docs/Contributing/contributing-how-to-contribute.mdx
📚 Learning: 2025-07-18T18:26:42.027Z
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be written in Markdown or MDX files located under docs/docs/, following the prescribed directory structure for guides, reference, how-to, concepts, and API documentation.

Applied to files:

  • docs/docs/Contributing/contributing-how-to-contribute.mdx
🪛 markdownlint-cli2 (0.17.2)
DEVELOPMENT.md

170-170: Bare URL used

(MD034, no-bare-urls)

🪛 LanguageTool
docs/docs/Contributing/contributing-how-to-contribute.mdx

[grammar] ~122-~122: There might be a mistake here.
Context: ...nment but doesn't start the application. make run_cli installs dependencies, bu...

(QB_NEW_EN)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: build-and-deploy
🔇 Additional comments (3)
docs/docs/Contributing/contributing-how-to-contribute.mdx (2)

121-126: Change admonition to tip and tighten wording

We’ve confirmed that the Makefile (including Makefile.frontend) defines the init, run_cli, backend, and frontend targets. Please update lines 121–126 in docs/docs/Contributing/contributing-how-to-contribute.mdx as follows:

-:::important Difference between commands
-`make init` sets up the development environment but doesn't start the application.
-`make run_cli` installs dependencies, builds the frontend, and starts the application in one step.
-For development with hot-reload, use `make init`, followed by `make backend` and `make frontend` commands in separate terminals.
-:::
+:::tip Difference between commands
+`make init` sets up the development environment; it does not start the application.
+`make run_cli` installs dependencies, builds the frontend, and starts the application in one step.
+For development with hot reload, run `make init`, then `make backend` and `make frontend` in separate terminals.
+:::

210-214: Change admonition to warning and verify docs build locally

Please update the note in docs/docs/Contributing/contributing-how-to-contribute.mdx (lines 210–214) to use a warning admonition and streamline the text:

- File: docs/docs/Contributing/contributing-how-to-contribute.mdx
- Lines: 210–214
-:::important
-If you're using a dev container, run the documentation build from outside the container on your host terminal, not from within the dev container workspace.
-The documentation build may not work properly when run inside the dev container.
-:::
+:::warning
+If you’re using a dev container, build the docs from your host terminal (outside the container). Builds may not work properly inside the container.
+:::

I attempted to run the original verification script in the sandbox environment, but encountered Node/Yarn post-install errors that prevented a successful build. Please verify on your local setup (with a proper Node.js runtime):

cd docs
# (Optional) clean previous node_modules & cache
rm -rf node_modules .cache
yarn install
yarn build
yarn serve --port 3001 --host 127.0.0.1

Ensure the site builds without errors and that all links resolve correctly.

DEVELOPMENT.md (1)

68-75: Nice addition: quick-start via make run_cli

Clear callout that run_cli installs, builds, and starts in one step. This improves onboarding. LGTM.

@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Aug 25, 2025
@github-actions

This comment has been minimized.

Copy link
Copy Markdown
Collaborator

@aimurphy aimurphy left a comment

Choose a reason for hiding this comment

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

Some things are confusing

Comment thread DEVELOPMENT.md Outdated
Comment thread DEVELOPMENT.md Outdated
Comment thread DEVELOPMENT.md Outdated
Comment thread docs/docs/Contributing/contributing-how-to-contribute.mdx Outdated
Comment thread docs/docs/Contributing/contributing-how-to-contribute.mdx Outdated
@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Sep 2, 2025
Co-authored-by: April I. Murphy <36110273+aimurphy@users.noreply.github.com>
@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Sep 2, 2025
@github-actions

This comment has been minimized.

1 similar comment
@github-actions

This comment has been minimized.

@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Sep 2, 2025
@github-actions

This comment has been minimized.

@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Sep 2, 2025
@github-actions

This comment has been minimized.

@mendonk mendonk requested a review from aimurphy September 2, 2025 20:39
@github-actions github-actions Bot added the lgtm This PR has been approved by a maintainer label Sep 3, 2025
@mendonk mendonk enabled auto-merge September 3, 2025 20:59
@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Sep 3, 2025
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Sep 3, 2025

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Sep 3, 2025

Build successful! ✅
Deploying docs draft.
Deploy successful! View draft

@mendonk mendonk added this pull request to the merge queue Sep 3, 2025
Merged via the queue into main with commit 63ab2ca Sep 3, 2025
16 checks passed
@mendonk mendonk deleted the docs-lfoss-1905 branch September 3, 2025 21:13
@coderabbitai coderabbitai Bot mentioned this pull request Oct 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation lgtm This PR has been approved by a maintainer

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants