Round 1 PDF due 3 Nov · 7 days left

Your CodeNexus India 2026 PPT, built to the round’s rules.

WeCodeCoders gives no slide template for this round. Paste your GitHub repo or drop in your notes, and devreport writes 9 slides from what the rules ask for in a few minutes. You submit the PDF.

See a sample deck No repo handy? Try a sample

Free to try. 15 free credits on sign‑up (enough for your first deck). No card.

9 slides from the round’s written rules
Charts and diagrams from your own files
Usually three to five minutes, a little longer for a big repo

The Moloch theme, on an example deck

There is no official CodeNexus India 2026 template, so this is a student’s CIFAR-10 coursework deck in devreport’s Moloch theme, which is why it has 10 pages. Your deck follows the 9 slides below, in that order, and is written from your own repo and notes.

Page 1 of an example deck in the CodeNexus India 2026 theme — 1 / 10

Page 2 of an example deck in the CodeNexus India 2026 theme — 2 / 10

Page 3 of an example deck in the CodeNexus India 2026 theme — 3 / 10

Page 4 of an example deck in the CodeNexus India 2026 theme — 4 / 10

Page 5 of an example deck in the CodeNexus India 2026 theme — 5 / 10

Page 6 of an example deck in the CodeNexus India 2026 theme — 6 / 10

Page 7 of an example deck in the CodeNexus India 2026 theme — 7 / 10

Page 8 of an example deck in the CodeNexus India 2026 theme — 8 / 10

Page 9 of an example deck in the CodeNexus India 2026 theme — 9 / 10

Page 10 of an example deck in the CodeNexus India 2026 theme — 10 / 10

There is no CodeNexus India 2026 template yet, so the page starts you on Moloch: dark teal with IBM Plex Sans, the typeface WeCodeCoders’ own site uses. Switch to any other theme before or after the build.

How it works

1Start from the button
The 9-slide CodeNexus India 2026 plan comes picked, in the Moloch theme. (Or start a deck, choose Slides and pick it under “Follow a template”.)
2Give it your material
The problem statement, your idea notes with the team details the cover asks for, and your repo or screenshots if you have them.
3Answer its questions
It asks for any cover detail your notes don’t have, and what it needs to know about the idea.
4Check it and submit the PDF
Fix a word on the page yourself or ask for changes, then download the PDF.

The round

Organiser: WeCodeCoders (online, on Unstop)
Deadline: 3 November 2026, 6 PM IST (Round 1: PDF Submission on Unstop, open from 10 AM on 2 November). WeCodeCoders’ own page gives the 48 hours as 2 Nov 10 AM to 4 Nov 10 AM, so check the official WhatsApp group for which one holds
What you submit: One project PDF. Round 1’s form on Unstop has a text box, not a file upload, so share the PDF as a link. Teams that qualify send an updated PDF, the working project link and the repository in Round 2
The rules: wecodecoders.in

Not an official template. WeCodeCoders publishes no slide template for this round yet. WeCodeCoders sends the problem statement and the official PDF format to everyone at 9 AM on 2 November, an hour before the clock starts. The slides below follow the round’s written rules on its page, and the look is devreport’s Moloch theme. devreport is not affiliated with CodeNexus India 2026 or WeCodeCoders; the round’s rules decide what you may submit.

The 9 slides, from the round’s rules

Start from the button and the deck follows these, in this order, in the Moloch theme.

Slide	What the rules ask for	What to give devreport
1. Cover	Your project and team	Your project name and team name as registered
2. The Problem as You Read It	The problem as you read it, and which part of it you took on	The problem statement they send at 9 AM, and the part your team chose
3. Who Has It	Who holds this problem and what it costs them today	Who the users are and what you know about the cost to them; no numbers are made up
4. Solution and Workflow	Your solution and the workflow through it: the main journey a judge will follow	What you built and the steps a user takes; it draws the flow
5. Features	The features you completed, and anything you knowingly left undone	What works and what doesn’t yet, or the repo so it can read them
6. Tech Stack	The technology stack, and a short summary of how it is put together	Your repo (it reads the dependencies) or the list of tools
7. Testing Notes	Testing notes for the main journeys	What you tried on each main journey and what happened
8. What Comes Next	Where the product would go next if you carried on with it (the judging sheet wants a credible plan)	Your next steps, in order
9. Team and Links	Team and participant details, the working project link and the source-code repository	Each member’s name and role, and the two links. A missing one stays blank for you to fill in

Questions

Is this the official CodeNexus India 2026 template?

No. WeCodeCoders hasn’t published a slide template for this round, so there is none to rebuild. The 9 slides here follow the round’s written rules, and the look is devreport’s Moloch theme. devreport is not affiliated with CodeNexus India 2026 or WeCodeCoders.

What if the organisers send a template or format later?

WeCodeCoders sends the problem statement and the official PDF format to everyone at 9 AM on 2 November, an hour before the clock starts. If you get a .pptx, upload it under “Follow a template” when you start the deck and it follows that file’s slides and headings. For a deck you have already made, ask for the changes the format needs.

Can I submit the devreport PDF?

The round asks for one project PDF. Round 1’s form on Unstop has a text box, not a file upload, so share the PDF as a link. Teams that qualify send an updated PDF, the working project link and the repository in Round 2. Check the organiser’s rules when in doubt.

We only have an idea, no code yet. Does it still work?

Yes. A repo is optional. Upload the problem statement, your notes on the idea and any data or screenshots, and it writes the slides from those. It won’t invent research, users or results you don’t give it.

Can I fix things myself before submitting?

Yes. Click any text on a slide to change it, move or resize charts and pictures, or ask for a change in plain words. Hand edits are free.

How long does it take?

Usually three to five minutes, a little longer for a big repo, plus the time you take to answer its questions.

What does it cost?

New accounts get 15 free credits. A deck costs 10 credits and each change you ask for afterwards costs 1; editing text on the page yourself and switching themes are free. A build that fails gives its credits back.

Other hackathon templates

CodeNexus India 2026, filled from your notes.

Your idea and repo in; the CodeNexus India 2026 slides out as a PDF. Not affiliated with the organisers.

Make my CodeNexus India 2026 deck