docs: Add documentation for vibe coding #1756
Conversation
patrikbraborec
force-pushed
the
add/vibe-code-docs
branch
from
0c7656b to
e9d37ef
Compare
patrikbraborec
force-pushed
the
add/vibe-code-docs
branch
from
e9d37ef to
50abbe0
Compare
|
Preview for this PR was built for commit |
Bugbot found 3 bugsTo see them, have a team admin activate your membership in the Cursor dashboard. |
|
Preview for this PR was built for commit |
🚨 Bugbot Trial ExpiredYour team's Bugbot trial has expired. Please contact your team administrator to turn on the paid plan to continue using Bugbot. A team admin can activate the plan in the Cursor dashboard. |
patrikbraborec
force-pushed
the
add/vibe-code-docs
branch
from
4865262 to
1d95fec
Compare
|
Preview for this PR was built for commit |
|
@TC-MO thanks a lot of a quick review, and good points. The last thing is with the change of title from From my point of view, I like the @jancurn are you are OK with the title |
|
For what it's worth I took a deep dive after this review to double check it, and couldn't find any documentation that would refer to this practice as Examples: I would strongly recommend |
TC-MO
left a comment
TC-MO
left a comment
There was a problem hiding this comment.
A few small things I noticed
|
Sure, we can keep "Build with AI" just make sure to use the term "vibe coding" in the description bellow for SEO |
Co-authored-by: Michał Olender <[email protected]>
|
Preview for this PR was built for commit |
|
BTW I find the links to sitemap.xml and robots.txt confusing, they are more prominent than the actual llms.txt links - I'd get rid of them and just list a table like:
On top of that, each individual documentation page is available also in Markdown, by adding the |
|
The table doesn't have any links. I think it serves as a nice explanation of differences between those 3 files. We'll definitely add info about making it a .md page |
|
But when looking how to vibe code with Apify, why do I need to get a "lecutre" about robots.txt and sitemap ? It adds confusion rather than clarity |
Co-authored-by: Michał Olender <[email protected]>
|
Preview for this PR was built for commit |
Bugbot found 2 bugsTo see them, have a team admin activate your membership in the Cursor dashboard. |
|
Preview for this PR was built for commit |
TC-MO
left a comment
TC-MO
left a comment
There was a problem hiding this comment.
2 final notes after that it LGTM
|
Thanks, done |
|
Preview for this PR was built for commit |
TC-MO
left a comment
TC-MO
left a comment
There was a problem hiding this comment.
LGTM, one final comment, but more of a question than anything to change
| /> | ||
| </CardGrid> | ||
|
|
||
| ## Build with AI |
There was a problem hiding this comment.
Any reason why not H3? I thought it would fit nicely as a separate developer path.
There was a problem hiding this comment.
The main reason is that the Start Locally in Your IDE and Start in Apify Web IDE are mode step-by-step tutorials where you finish with Actor. The Build with AI is more like things we have to support you in building Actors. Therefore, I tried to divide it.
There was a problem hiding this comment.
Hmm I guess that is true, we could maybe ponder if it shouldn't then fall under Start locally but as far as I am concerned we can do it at later date. thanks!
|
So, are we ready to merge it? |
|
All engines go from my side, approval etc |
Co-authored-by: Martin Adámek <[email protected]> Co-authored-by: Michał Olender <[email protected]>
The pull request introduces a new prompt component and documentation for AI-assisted coding.