codeulike

People should expand acronyms at least one place somewhere on the page. I'm now three clicks deep and looking through the youtube comments and still a bit vague as to what this is. CI/CD? Thats continuous integration right? Should everyone know thats what CI stands for? I'm sure its a very useful thing but I havent personally ever used it even though I've been a programmer for 40 years. So I'm not that famailiar with the acronyms. My point being - our industry is big and not everyone uses every thing, or knows what it is, so its useful to expand acronyms somewhere in the description.

bxparks
Agreed that CI/CD should be explained, or at least hyperlinked. However, in their minor defense, they are following the example of GitHub Actions (https://github.com/features/actions) which also does not explain those terms. But at least GitHub Actions does explain it in the docs (https://docs.github.com/en/actions).

My problem is that I know what CI/CD is, I have used a handful of popular implementations of CI/CD (e.g GitHub Actions, BitBucket Pipelines). But after clicking through most of the pages on the Bob CD website, I don't understand what exactly Bob CD does or how to use it. Is it local (like Jenkins), or is it cloud based (like GitHub Actions)? How does it integrate with my local git repo, or my GitHub or GitLab account? How do I trigger the pipeline? How do I specify the actions of the pipeline?

It feels like Bob CD website makes sense only if you already know how to use Bob CD.

(edit: fix typo)