Skip to content

Remove granite-code-cookbook references#73

Merged
bjhargrave merged 1 commit into
mainfrom
remove-granite-code
Jun 12, 2026
Merged

Remove granite-code-cookbook references#73
bjhargrave merged 1 commit into
mainfrom
remove-granite-code

Conversation

@bjhargrave

Copy link
Copy Markdown
Collaborator

The granite-code models are gen 2 and the granite-code-cookbook recipes are not maintained. The granite-code-cookbook will soon be archived.

The granite-code models are gen 2 and the granite-code-cookbook
recipes are not maintained. The granite-code-cookbook will soon be
archived.

Signed-off-by: BJ Hargrave <hargrave@us.ibm.com>
@bjhargrave bjhargrave requested a review from serjikibm June 10, 2026 15:38
@serjikibm

Copy link
Copy Markdown
Collaborator

In the Cookbooks tab, under the Granite Code Cookbook section I see only the following two sections, which your PR removes. However I can't find the content in the md files, unless I search for them. Were they available in the side nav in the past and was dropped as a result of the migration? I am asking to make sure we are not missing other nav items. I haven't pulled the PR to test it locally yet.

image

@bjhargrave

Copy link
Copy Markdown
Collaborator Author

The PR removes those 2 pages: use-cases/text-to-*. They are available on the side nav bar before this PR.

@serjikibm

Copy link
Copy Markdown
Collaborator

There are no other references int he docs to these pages (AI validation confirmed)

Also after running locally, the Granite Code Cookbook navigation item is removed. No errors in the console. As mentioned by the author, the content being referenced is also going to be archived later.

Before the change

image

After the change

image

@serjikibm serjikibm left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

LGTM

@serjikibm

Copy link
Copy Markdown
Collaborator

@planetf1 any concerns before merging this PR?

This is the first round of contributions by document maintainers, post migration.

@planetf1

Copy link
Copy Markdown
Collaborator
  • The migration was correct. I did a page-by-page check before the cutover — all 42 Mintlify nav pages were ported faithfully, no granite-code content was dropped. That said, the migration was process-based not editorial, so it preserved whatever was there rather than making any judgements about relevance.
  • text-to-python and text-to-shell are live public pages — they were in the old Mintlify nav and are in the current Docusaurus sidebar, so users can reach them right now.
  • code.mdx, granite-code-on-replicate, and granite-code-with-continue were never in the Mintlify nav. They've been suppressed (displayed_sidebar: null) since the migration and are tracked in Content review: reconnect 6 pages suppressed during Mintlify migration #66 — which notes that code.mdx looks like an authoring oversight and suggests adding it to the Models sidebar.

The intent here looks right — gen-1 models are superseded and removing those references keeps the docs useful and relevant. One thing worth flagging: Text_to_Python.ipynb has already been updated to use granite-3.3-8b-instruct, so not all the cookbook content is gen-1. If we're happy removing the 3.3 material too (reasonable given there's no other gen-3 cookbook content), then the removal is clean.

It's also worth noting the cookbook repo itself has no Granite 4 examples yet — is there a plan to add those? is it a gap that needs filling?

One minor thing - do we want any additional link redirects from old pages to somewhere on the site (we already have a custom 404 though)

@planetf1 planetf1 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

All good to merge

@bjhargrave bjhargrave merged commit 4e8c294 into main Jun 12, 2026
3 checks passed
@serjikibm serjikibm deleted the remove-granite-code branch June 12, 2026 14:33
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.

3 participants