Skip to content

docs: add a first blog post in the website#672

Merged
tbouffard merged 3 commits intomainfrom
docs/add_blog_post
Feb 12, 2025
Merged

docs: add a first blog post in the website#672
tbouffard merged 3 commits intomainfrom
docs/add_blog_post

Conversation

@tbouffard
Copy link
Member

@tbouffard tbouffard commented Feb 12, 2025

This first blog post is an overview about what's been accomplished in 2024 and what to expect next in 2025.

A simple Docusaurus blog configuration has been initialized:

  • global authors
  • blog edit link

Additional website changes

  • Fix regular docs page edit url: use an edit link, not a view link
  • Change the order of items in navbar and in the footer after the introduction of the Blog

Summary by CodeRabbit

  • New Features

    • Added a new blog post outlining future directions for maxGraph.
    • Introduced a new author profile for Thomas Bouffard to enrich community insights.
  • Documentation & Navigation Updates

    • Enhanced website navigation with clearer labels and dedicated sections for Docs, Blog, and API.
    • Updated documentation configuration to improve the editing and content management experience.

This first blog post is an overview about what's been accomplished in 2024 and what to expect next in 2025.

A simple Docusaurus blog configuration has been initialized:
  - global authors
  - blog edit link

Additional website changes
  - Fix regular docs page edit url: use an edit link, not a view link
  - Change the order of items in navbar and in the footer after the introduction of the Blog
@tbouffard tbouffard added the documentation Improvements or additions to documentation label Feb 12, 2025
@coderabbitai
Copy link

coderabbitai bot commented Feb 12, 2025

Walkthrough

This pull request introduces a new blog post titled "Looking Ahead: maxGraph in 2025," outlining the future direction and goals for the maxGraph library, including documentation improvements and tree-shaking optimizations. An author entry for Thomas Bouffard has been added to the blog configuration. The Docusaurus configuration has been updated to include a new constant for the edit URL and reorganized navigation and footer links for improved clarity and accessibility.

Changes

File(s) Change Summary
packages/website/blog/2025/02-12-looking-ahead-maxgraph-in-2025.md, packages/website/blog/authors.yml Added a new blog post detailing maxGraph’s future plans and introduced a new author entry for Thomas Bouffard.
packages/website/docusaurus.config.ts Introduced a new editUrl constant and updated navigation items and footer links (labels changed and reordering applied) to streamline configuration.

Possibly related PRs

  • chore(deps-dev): bump docusaurus from 3.5.2 to 3.6.0 #559: The changes in the main PR regarding the Docusaurus configuration are related to the modifications made in the retrieved PR, as both involve updates to the packages/website/docusaurus.config.ts file, specifically altering the configuration structure.

Suggested labels

enhancement


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f999345 and ff687d6.

📒 Files selected for processing (1)
  • packages/website/blog/2025/02-12-looking-ahead-maxgraph-in-2025.md (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • packages/website/blog/2025/02-12-looking-ahead-maxgraph-in-2025.md

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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

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

🧹 Nitpick comments (2)
packages/website/docusaurus.config.ts (1)

48-50: Consider additional blog configuration options.

While the current configuration is sufficient, you might want to consider these additional options for better blog functionality:

  • showReadingTime: true - Shows estimated reading time
  • postsPerPage: 5 - Controls pagination
  • blogSidebarCount: 'ALL' - Shows all posts in sidebar
packages/website/blog/2025/02-12-looking-ahead-maxgraph-in-2025.md (1)

43-43: Consider these grammar improvements.

  1. Add a comma before "and" in compound sentences:
-In the initial release, Internet Explorer support was removed and custom code was replaced with modern ECMAScript APIs.
+In the initial release, Internet Explorer support was removed, and custom code was replaced with modern ECMAScript APIs.
  1. Avoid repetitive sentence beginnings around line 49.

  2. Add a comma in:

-Issues will continue to be addressed and performance improvements will be made.
+Issues will continue to be addressed, and performance improvements will be made.

Also applies to: 49-49, 68-68

🧰 Tools
🪛 LanguageTool

[uncategorized] ~43-~43: Use a comma before “and” if it connects two independent clauses (unless they are closely connected and short).
Context: ...e, Internet Explorer support was removed and custom code was replaced with modern EC...

(COMMA_COMPOUND_SENTENCE_2)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 81d5e5a and 19c2640.

📒 Files selected for processing (3)
  • packages/website/blog/2025/02-12-looking-ahead-maxgraph-in-2025.md (1 hunks)
  • packages/website/blog/authors.yml (1 hunks)
  • packages/website/docusaurus.config.ts (4 hunks)
🧰 Additional context used
🪛 LanguageTool
packages/website/blog/2025/02-12-looking-ahead-maxgraph-in-2025.md

[uncategorized] ~43-~43: Use a comma before “and” if it connects two independent clauses (unless they are closely connected and short).
Context: ...e, Internet Explorer support was removed and custom code was replaced with modern EC...

(COMMA_COMPOUND_SENTENCE_2)


[style] ~49-~49: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ctly, avoiding transitive inclusion. - [v0.12.0](https://github.com/maxGraph/maxGr...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[uncategorized] ~68-~68: Use a comma before “and” if it connects two independent clauses (unless they are closely connected and short).
Context: ...ty. Issues will continue to be addressed and performance improvements will be made. ...

(COMMA_COMPOUND_SENTENCE_2)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: build
🔇 Additional comments (6)
packages/website/docusaurus.config.ts (3)

6-6: LGTM! Good refactoring.

Extracting the GitHub edit URL into a constant improves maintainability and reduces duplication.


84-107: LGTM! Navigation structure is well-organized.

The navigation items are logically ordered and the labels are concise. The changes align well with the PR objectives.


126-133: LGTM! Footer links are consistent with navigation.

The footer links maintain consistency with the navigation structure, using clear and descriptive labels.

packages/website/blog/authors.yml (1)

1-7: LGTM! Author entry is well-structured.

The author entry contains all necessary information and follows YAML best practices.

packages/website/blog/2025/02-12-looking-ahead-maxgraph-in-2025.md (2)

1-6: LGTM! Frontmatter is complete and well-structured.

The frontmatter contains all necessary fields with clear and informative content.


13-13: LGTM! Truncate marker is correctly placed.

The truncate marker is well-positioned to create an engaging blog preview.

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

🧹 Nitpick comments (2)
packages/website/blog/2025/02-12-looking-ahead-maxgraph-in-2025.md (2)

47-49: Consider varying sentence beginnings.

To improve readability, consider rewording the version entries to avoid repetitive beginnings:

-- [v0.6.0](https://github.com/maxGraph/maxGraph/releases/tag/v0.6.0): Codecs are no longer registered by default.
-- [v0.11.0](https://github.com/maxGraph/maxGraph/releases/tag/v0.11.0): `MaxLog` and `MaxWindow` are no longer called directly, avoiding transitive inclusion.
-- [v0.12.0](https://github.com/maxGraph/maxGraph/releases/tag/v0.12.0): The npm package is declared without side effects.
+- Release [v0.6.0](https://github.com/maxGraph/maxGraph/releases/tag/v0.6.0): Codecs are no longer registered by default.
+- In [v0.11.0](https://github.com/maxGraph/maxGraph/releases/tag/v0.11.0): `MaxLog` and `MaxWindow` are no longer called directly, avoiding transitive inclusion.
+- With [v0.12.0](https://github.com/maxGraph/maxGraph/releases/tag/v0.12.0): The npm package is declared without side effects.
🧰 Tools
🪛 LanguageTool

[style] ~49-~49: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ctly, avoiding transitive inclusion. - [v0.12.0](https://github.com/maxGraph/maxGr...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


81-81: Fix emphasis formatting in P.S. section.

The emphasis formatting has extra asterisks.

-*P.S. We're looking for contributors and maintainers to keep the project alive and kicking. Check out ****[Issue #354](https://github.com/maxGraph/maxGraph/issues/354)**** if you're interested! 😄*
+*P.S. We're looking for contributors and maintainers to keep the project alive and kicking. Check out **[Issue #354](https://github.com/maxGraph/maxGraph/issues/354)** if you're interested! 😄*
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 19c2640 and f999345.

📒 Files selected for processing (1)
  • packages/website/blog/2025/02-12-looking-ahead-maxgraph-in-2025.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
packages/website/blog/2025/02-12-looking-ahead-maxgraph-in-2025.md

[style] ~49-~49: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ctly, avoiding transitive inclusion. - [v0.12.0](https://github.com/maxGraph/maxGr...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

🔇 Additional comments (4)
packages/website/blog/2025/02-12-looking-ahead-maxgraph-in-2025.md (4)

8-15: Well-structured introduction!

The introduction effectively sets the context and uses the truncate marker appropriately.


16-33: Well-organized documentation section!

The section effectively communicates achievements and future plans, with proper GitHub issue referencing.


62-73: Clear and concise additional topics!

The sections on stabilization and API definition effectively communicate the plans.


4-4: Verify author reference in authors.yml.

Please ensure that the author reference "tbouffard" exists in the authors.yml configuration file.

✅ Verification successful

🏁 Script executed:

#!/bin/bash
# Description: Check if the author exists in authors.yml
rg -A 5 "tbouffard:" packages/website/blog/authors.yml

Length of output: 211


Author reference verified in authors.yml.

The configuration file confirms that the author "tbouffard" is correctly specified.

@sonarqubecloud
Copy link

@tbouffard tbouffard merged commit 4132bc3 into main Feb 12, 2025
2 checks passed
@tbouffard tbouffard deleted the docs/add_blog_post branch February 12, 2025 16:44
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant