Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document use of Cloud Native Buildpacks #312

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Document use of Cloud Native Buildpacks #312

wants to merge 2 commits into from

Conversation

c0d1ngm0nk3y
Copy link

@c0d1ngm0nk3y c0d1ngm0nk3y commented Sep 20, 2024 •
edited
Loading

This was referenced Sep 20, 2024
Open
Open
@pspinrad
Copy link
Contributor

pspinrad commented Sep 20, 2024 •
edited
Loading

Hi @c0d1ngm0nk3y -- good idea to create a sub-level for buildpacks in the table of contents, but it would cause trouble to move all the source files themselves down a level, because they're linked to from lots of other places in the CF docs and elsewhere on the web, so all of those URLs would no longer work.
WDYT would be a good strategy for adding Cloud Native buildpack pages without messing with existing file structure? /cnb subdirectory, or cnb filename prefix or suffix?
Re: terminology, in the Tanzu docs, for example this page, we're using terminology "Cloud Foundry buildpacks" and "Cloud Native buildpacks" to differentiate between the older and newer buildpack types. "Classical" here refers to the CF buildpacks in that terminology, right?

@c0d1ngm0nk3y c0d1ngm0nk3y marked this pull request as ready for review September 30, 2024 12:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@c0d1ngm0nk3y @pspinrad @pbusko