Skip to content

docs: remove AI-generated content warnings and simplify Request Scan page#75

Open
aimensahnoun wants to merge 1 commit into03-03-docs_nav_hide_community_page_from_resources_while_keeping_source_file_remove_resources_community_from_the_resources_navigation_in_docs.json_to_make_the_community_page_inaccessible_in_the_docs_ui_for_now_while_preserving_resourcefrom
03-03-docs_resources_clean_easyinvoice_and_request_scan_pages_for_tools_examples_refine_the_tools_examples_docs_by_removing_low-value_placeholder_sections_while_keeping_the_key_product_walkthrough_content_intact._-_request-network-api
Open

docs: remove AI-generated content warnings and simplify Request Scan page#75
aimensahnoun wants to merge 1 commit into03-03-docs_nav_hide_community_page_from_resources_while_keeping_source_file_remove_resources_community_from_the_resources_navigation_in_docs.json_to_make_the_community_page_inaccessible_in_the_docs_ui_for_now_while_preserving_resourcefrom
03-03-docs_resources_clean_easyinvoice_and_request_scan_pages_for_tools_examples_refine_the_tools_examples_docs_by_removing_low-value_placeholder_sections_while_keeping_the_key_product_walkthrough_content_intact._-_request-network-api

Conversation

@aimensahnoun
Copy link
Member

@aimensahnoun aimensahnoun commented Mar 3, 2026

TL;DR

Removed AI-generated content warnings and cleaned up documentation pages for EasyInvoice API demo and Request Scan.

What changed?

  • Removed AI-generated content warning blocks from both the EasyInvoice API demo app and Request Scan documentation pages
  • Deleted the "Intended Audience" section from the Request Scan page that listed various user types (accountants, developers, analysts, researchers, enthusiasts)
  • Updated the CardGroup component from 3 columns to 2 columns and removed the "Demo Video" card from the Request Scan page

How to test?

  • Navigate to the EasyInvoice API demo app documentation page and verify the warning banner is no longer displayed
  • Check the Request Scan documentation page to confirm the AI warning is removed and the "Intended Audience" section is gone
  • Verify the card layout displays correctly with 2 columns instead of 3

Why make this change?

This change removes outdated AI-generated content disclaimers and streamlines the documentation by removing redundant sections, making the pages cleaner and more focused on essential information.

…xamples

Refine the Tools & Examples docs by removing low-value placeholder sections
while keeping the key product walkthrough content intact.
- `request-network-api/easyinvoice-api-demo-app.mdx`
  - removed the AI-generated warning banner at the top of the page
  - kept existing EasyInvoice content and media unchanged
- `resources/request-scan.mdx`
  - removed the AI-generated warning banner
  - removed the top “Demo Video” card from the page header card group
  - removed the “Intended Audience” section
  - kept the embedded demo video section in the body
  - adjusted top card group layout to `cols={2}` after card removal
This was referenced Mar 3, 2026
Copy link
Member Author

aimensahnoun commented Mar 3, 2026

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

This stack of pull requests is managed by Graphite. Learn more about stacking.

@aimensahnoun aimensahnoun changed the title docs(resources): clean EasyInvoice and Request Scan pages for tools/examples Refine the Tools & Examples docs by removing low-value placeholder sections while keeping the key product walkthrough content intact. - `request-network-api/easyinvoice-api-demo- docs: remove AI-generated content warnings and simplify Request Scan page Mar 3, 2026
@aimensahnoun aimensahnoun marked this pull request as ready for review March 3, 2026 14:40
@greptile-apps
Copy link

greptile-apps bot commented Mar 3, 2026

Greptile Summary

This PR cleans up two documentation pages by removing AI-generated content warning banners and streamlining the Request Scan page structure. The changes are minimal, well-scoped, and purely cosmetic/editorial — no logic, API, or code behaviour is affected.

Key changes:

  • Removed <Warning> AI-generated content banners from both easyinvoice-api-demo-app.mdx and request-scan.mdx
  • Removed the "Intended Audience" section from request-scan.mdx
  • Removed the "Demo Video" <Card> from the <CardGroup> and reduced cols from 3 to 2 on request-scan.mdx
  • Note: the ### Demo Video section with the embedded YouTube iframe still exists in the request-scan.mdx page body — it is still accessible by scrolling, just no longer surfaced via a quick-link card at the top

Confidence Score: 5/5

  • This PR is safe to merge — it is a purely editorial cleanup with no risk of breaking functionality.
  • Both changes are straightforward documentation edits: removing outdated warning banners and trimming redundant sections. No links are broken, no components are misconfigured, and the ### Demo Video section with its iframe remains in the page body even though its quick-link card was removed. There are no logic, syntax, or structural issues.
  • No files require special attention.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    subgraph Before
        A1["Warning: AI-Generated Content"] --> B1["Page Content"]
        B1 --> C1["CardGroup cols=3\nTry it out, Demo Video, View Source"]
        C1 --> D1["Intended Audience Section"]
        D1 --> E1["Usage and rest of page"]
    end

    subgraph After
        A2["Page Content starts directly"] --> C2["CardGroup cols=2\nTry it out, View Source"]
        C2 --> E2["Usage and rest of page\nDemo Video section still present"]
    end

    Before -->|"PR removes banners, Intended Audience, Demo Video card"| After
Loading

Last reviewed commit: 1f904bb

Copy link

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

2 files reviewed, no comments

Edit Code Review Agent Settings | Greptile

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.

1 participant