Skip to content

Refactor README structure for improved readability and maintainability#1258

Open
rohan-pandeyy wants to merge 1 commit intoAOSSIE-Org:mainfrom
rohan-pandeyy:docs/readme-revamp
Open

Refactor README structure for improved readability and maintainability#1258
rohan-pandeyy wants to merge 1 commit intoAOSSIE-Org:mainfrom
rohan-pandeyy:docs/readme-revamp

Conversation

@rohan-pandeyy
Copy link
Copy Markdown
Contributor

@rohan-pandeyy rohan-pandeyy commented Apr 19, 2026

Addressed Issues:

Fixes #1257

This pull request improves the documentation and project presentation for PictoPy, focusing on enhancing the README with a clearer project overview, updated social links, and a new architecture diagram. It also updates copyright information and streamlines the contributing and database documentation.

README and Documentation Enhancements:

  • Major overhaul of README.md to provide a more compelling project description, add social media badges, highlight key features, and include a demonstration section with images and video links. The technical stack section is reorganized, and a new high-level architecture diagram is added for better clarity. Contribution instructions and licensing information are now more prominent. [1] [2]
  • Updated the database documentation (docs/backend/backend_python/database.md) to replace the embedded interactive schema with a static image and a link to the interactive diagram, improving accessibility and presentation.

Legal and Contributing Updates:

  • Updated the copyright year in COPYRIGHT.md from 2025 to 2026.
  • Minor formatting and heading adjustments in CONTRIBUTING.md for consistency with the rest of the documentation.

Screenshots/Recordings:

image

Additional Notes:

AI Usage Disclosure:

We encourage contributors to use AI tools responsibly when creating Pull Requests. While AI can be a valuable aid, it is essential to ensure that your contributions meet the task requirements, build successfully, include relevant tests, and pass all linters. Submissions that do not meet these standards may be closed without warning to maintain the quality and integrity of the project. Please take the time to understand the changes you are proposing and their impact. AI slop is strongly discouraged and may lead to banning and blocking. Do not spam our repos with AI slop.

Check one of the checkboxes below:

  • This PR does not contain AI-generated code at all.
  • This PR contains AI-generated code. I have read the AI Usage Policy and this PR complies with this policy. I have tested the code locally and I am responsible for it.

I have used the following AI models and tools: TODO

Checklist

  • My PR addresses a single issue, fixes a single bug or makes a single improvement.
  • My code follows the project's code style and conventions
  • If applicable, I have made corresponding changes or additions to the documentation
  • If applicable, I have made corresponding changes or additions to tests
  • My changes generate no new warnings or errors
  • I have joined the Discord server and I will share a link to this PR with the project maintainers there
  • I have read the Contribution Guidelines
  • Once I submit my PR, CodeRabbit AI will automatically review it and I will address CodeRabbit's comments.
  • I have filled this PR template completely and carefully, and I understand that my PR may be closed without review otherwise.

Summary by CodeRabbit

  • Documentation
    • Significantly expanded README with enriched project description, features overview, technology stack, demonstration section, and architecture diagram
    • Added social media links providing quick access to community channels
    • Simplified contributing guide formatting for clarity
    • Enhanced database documentation with visual architecture diagrams
    • Updated copyright information

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 19, 2026

Walkthrough

This PR updates multiple documentation files across the project: removes emoji prefixes from CONTRIBUTING.md headings, updates the copyright year to 2026, comprehensively restructures README.md with new feature sections and social badges, and replaces an embedded database schema iframe with a static architecture image in the backend documentation.

Changes

Cohort / File(s) Summary
Metadata and Licensing
COPYRIGHT.md
Updated copyright year from 2025 to 2026.
Contributing Guidelines
CONTRIBUTING.md
Removed emoji prefixes from the main title and "Setting Up the Project" section headings.
Main Project README
README.md
Restructured with centered banner image, social links badges (Telegram, X, Discord, Medium, LinkedIn, YouTube), expanded feature descriptions, new "Demonstration" section with video link, reorganized Technology Stack section, added "High Level Architecture" section, and enhanced contribution and contributor acknowledgment sections.
Backend Database Documentation
docs/backend/backend_python/database.md
Replaced embedded interactive DB schema iframe with centered static architecture image (../../assets/database_architecture.svg); updated alternative link text to clarify opening the interactive schema in a new tab.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested labels

Documentation

Poem

🐰 The docs hop and dance with a modernish flair,
Emojis removed, the headings laid bare,
A README redesigned, so polished and bright,
The schema now static—a minimalist sight,
From twenty-twenty-five into twenty-twenty-six we bound,
PictoPy's story in documents, beautifully crowned!

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Out of Scope Changes check ❓ Inconclusive CONTRIBUTING.md emoji removal and COPYRIGHT.md year update are minor maintenance changes tangentially related to documentation improvements. Database documentation update is a scope extension, though documentation-related. Clarify whether updates to CONTRIBUTING.md, COPYRIGHT.md, and database.md were intentional or should be separated into distinct PRs focused on their respective domains.
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Refactor README structure for improved readability and maintainability' directly describes the primary change in the PR, which is a comprehensive update to README.md. It accurately captures the main objective.
Linked Issues check ✅ Passed The PR addresses issue #1257's core objectives: enhanced README with header section, badges, screenshots, reorganized sections (Overview, Features, Tech Stack, Architecture), and improved contributor-friendly structure. Additional file updates (COPYRIGHT.md, CONTRIBUTING.md, database.md) are supportive refinements.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

Comment @coderabbitai help to get the list of available commands and usage tips.

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

🧹 Nitpick comments (1)
CONTRIBUTING.md (1)

7-7: Use a subordinate heading level for “Setting Up the Project.”

Line 7 should be ## (not #) so the document has a single H1 and clearer hierarchy.

As per coding guidelines, "Confirm that the code meets the project's requirements and objectives."

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@CONTRIBUTING.md` at line 7, Change the top-level heading "Setting Up the
Project" to a subordinate heading by replacing the single '#' with '##' so the
document has only one H1 and a clear hierarchy; locate the line containing the
heading text "Setting Up the Project" and update it accordingly, ensuring the
rest of the document structure remains unchanged and the heading now uses '##'.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/backend/backend_python/database.md`:
- Line 9: Update the img tag's alt attribute in the documentation (the <img
src="../../assets/database_architecture.svg" .../> element) so the alt text
accurately describes the image content; replace alt="PictoPy Banner" with a
descriptive phrase such as "Database architecture diagram" (or similar) to
reflect that it is a database schema image and fix the spelling/grammar if
necessary.

In `@README.md`:
- Line 114: Replace the placeholder string "TODO" in the contributor thank-you
sentence that currently reads "helping TODO grow" with the actual project name
(or a neutral phrase like "this project") so the user-facing README text is not
left as an unfinished placeholder; locate the exact occurrence of "helping TODO
grow" in README.md and update it to "helping <project-name> grow" or "helping
this project grow" and search for any other "TODO" placeholders in the same file
to correct them similarly.
- Line 97: The Discord badge <img> element in README.md is missing an alt
attribute; update the <img
src="https://img.shields.io/discord/1022871757289422898?style=flat&logo=discord&logoColor=white&logoSize=auto&label=Discord&labelColor=5865F2&color=57F287"
height="30"> tag to include a concise alt text (e.g., alt="Discord server") to
satisfy markdownlint MD045 and accessibility guidelines.

---

Nitpick comments:
In `@CONTRIBUTING.md`:
- Line 7: Change the top-level heading "Setting Up the Project" to a subordinate
heading by replacing the single '#' with '##' so the document has only one H1
and a clear hierarchy; locate the line containing the heading text "Setting Up
the Project" and update it accordingly, ensuring the rest of the document
structure remains unchanged and the heading now uses '##'.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 15ead3f4-a14f-4de2-ad8f-d934f44b36b6

📥 Commits

Reviewing files that changed from the base of the PR and between 8274ebd and 2ebd299.

⛔ Files ignored due to path filters (5)
  • docs/assets/architectual-design-dark.svg is excluded by !**/*.svg
  • docs/assets/architectual-design-light.svg is excluded by !**/*.svg
  • docs/assets/banner.png is excluded by !**/*.png
  • docs/assets/database_architecture.svg is excluded by !**/*.svg
  • docs/assets/demo.png is excluded by !**/*.png
📒 Files selected for processing (4)
  • CONTRIBUTING.md
  • COPYRIGHT.md
  • README.md
  • docs/backend/backend_python/database.md


## Database Schema
<p align="center">
<img src="../../assets/database_architecture.svg" alt="PictoPy Banner" width="100%"/>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Update image alt text to match the actual content.

Line 9 uses alt="PictoPy Banner", but this is a database schema image. Please use a descriptive alt text like Database architecture diagram.

As per coding guidelines, "Verify that documentation and comments are free of spelling mistakes."

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/backend/backend_python/database.md` at line 9, Update the img tag's alt
attribute in the documentation (the <img
src="../../assets/database_architecture.svg" .../> element) so the alt text
accurately describes the image content; replace alt="PictoPy Banner" with a
descriptive phrase such as "Database architecture diagram" (or similar) to
reflect that it is a database schema image and fix the spelling/grammar if
necessary.

Comment thread README.md

## Want to Contribute?

<a href="https://discord.gg/hjUhu33uAn"><img src="https://img.shields.io/discord/1022871757289422898?style=flat&logo=discord&logoColor=white&logoSize=auto&label=Discord&labelColor=5865F2&color=57F287" height="30"></a>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Add alt text to the Discord badge image.

Line 97’s <img> is missing an alt attribute (also flagged by markdownlint MD045).

As per coding guidelines, "Confirm that the code meets the project's requirements and objectives."

🧰 Tools
🪛 markdownlint-cli2 (0.22.0)

[warning] 97-97: Images should have alternate text (alt text)

(MD045, no-alt-text)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` at line 97, The Discord badge <img> element in README.md is
missing an alt attribute; update the <img
src="https://img.shields.io/discord/1022871757289422898?style=flat&logo=discord&logoColor=white&logoSize=auto&label=Discord&labelColor=5865F2&color=57F287"
height="30"> tag to include a concise alt text (e.g., alt="Discord server") to
satisfy markdownlint MD045 and accessibility guidelines.

Comment thread README.md

## Thanks To All Contributors

Thanks a lot for spending your time helping TODO grow. Keep rocking 🥂
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Replace the placeholder “TODO” in contributor thanks text.

Line 114 currently says “helping TODO grow,” which reads like an unfinished placeholder in user-facing docs.

As per coding guidelines, "Suggest code completions when seeing a TODO or FIXME comment."

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` at line 114, Replace the placeholder string "TODO" in the
contributor thank-you sentence that currently reads "helping TODO grow" with the
actual project name (or a neutral phrase like "this project") so the user-facing
README text is not left as an unfinished placeholder; locate the exact
occurrence of "helping TODO grow" in README.md and update it to "helping
<project-name> grow" or "helping this project grow" and search for any other
"TODO" placeholders in the same file to correct them similarly.

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.

DOC: Enhance README with Modern Structure, Visuals, and Contributor-Friendly Sections

1 participant