DEV Community

Cover image for Slow Steady
Rishabh Jain
Rishabh Jain

Posted on

Slow Steady

Hacktoberfest Open-Source AI Challenge Week 3: Slow and Steady Submission 🦥

Slow and Steady: A Document Studio for Academic Reports and Presentations

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 3: Slow and Steady

What I Built

I built Slow-Steady, a web-based academic document studio designed to simplify the process of preparing project reports and presentations.

Students often spend too much time formatting academic documents, organizing sections, and repeatedly checking their layouts instead of focusing on their actual project work. Slow-Steady aims to make this process more structured and convenient.

The application provides eight document options:

  • Summer Internship Report
  • Minor Project I Report
  • Minor Project II Report
  • Major Project I Report
  • Major Project II Report
  • Major Project Presentation
  • Major & Minor Project PPT
  • Summer Internship Report PPT

Users first select the document type from a dashboard. They then enter their project details in a split-screen workspace, where the editor sits beside a live preview.

The goal is simple: less repetitive formatting, clearer document preparation, and more time for meaningful project work.

Demo

Try the deployed application:

Open Slow-Steady

The application includes a document-selection dashboard, a document editor, a live preview, and editable DOCX/PPTX export functionality.

Code

The project is open source and available on GitHub:

RISHABH12005/Slow-Steady

You can explore the implementation, review the workflow, report issues, and contribute improvements.

The repository also includes automated compliance tests through GitHub Actions.

How I Built It

I built Slow-Steady as a web application using Python and FastAPI, with document-generation libraries for producing editable Word documents and PowerPoint presentations.

The main components include:

  • FastAPI: Handles the web application and document-generation requests.
  • python-docx: Generates editable Word reports.
  • python-pptx: Generates editable PowerPoint presentations.
  • HTML, CSS, and JavaScript: Provide the dashboard, responsive editor layout, and live preview interactions.
  • GitHub Actions: Runs automated tests to check the application and generated documents.
  • Render: Hosts the deployed web application.

I designed the interface around a two-step workflow: choose a document first, then work in a split-screen editor and preview.

The project focuses on reusable document structures, editable exports, and automated checks. Generated documents still need to be reviewed against the applicable academic guidelines before submission.

Why Does Open Innovation Matter?

Open innovation makes it possible for developers and students to inspect how a tool works, adapt it to their own needs, and contribute improvements rather than depending entirely on a closed service.

For Slow-Steady, an open-source approach means that contributors can improve report structures, add document profiles, strengthen formatting validation, and help make the tool more useful for different academic requirements.

It also makes the development process more transparent: users can inspect the code and automated tests instead of treating the application as a black box.

The project can grow through community contributions, shared feedback, and reusable solutions.

My Agent Session

I used AI assistance during development to refine the interface, improve the document-selection workflow, troubleshoot automated test failures, and make the preview easier to navigate.

I haven't included a public agent-session recording because I don't yet have a verified shareable session link. If I publish one through DevRelay, I'll add it here.

The Lazy Payoff

The biggest payoff is reducing repetitive setup work.

Instead of starting from a blank document every time, a student can select a document profile, enter project information, review the preview, and generate an editable file.

I haven't measured the time saved in a formal user test, so I won't claim a specific percentage or number of hours. The next step is to test the application with students, measure how long common document-preparation tasks take, and use their feedback to improve the workflow.

Slow-Steady is built around one idea: spend less time fighting document formatting and more time working on the project itself.

Prize Categories

Top comments (0)