feat: use the Python course as a template for a new JavaScript course #1584
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
honzajavorek
added
the
t-academy
honzajavorek
force-pushed
the
honzajavorek/javascript2
branch
from
f4c5ab8 to
ca304ee
Compare
|
Preview for this PR was built for commit |
|
Preview for this PR was built for commit |
honzajavorek
force-pushed
the
honzajavorek/javascript2
branch
from
bc2ff07 to
eb05470
Compare
|
Preview for this PR was built for commit |
|
Preview for this PR was built for commit |
honzajavorek
force-pushed
the
honzajavorek/javascript2
branch
from
e3b6f07 to
6e6db97
Compare
|
Preview for this PR was built for commit |
honzajavorek
added a commit
that referenced
this pull request
Jun 27, 2025
… (groundworks) (#1651) See #1584 for more details. I carved out these two commits so that we can do incremental reviews of my changes in subsequent PRs instead of a huge PR with everything stuffed in it: - 8e6a303 is a copy-paste of the Python course to a new directory called `javascript2` (nothing to review, really) - 9ccf0df makes it `unlisted` There are, of course, more changes to come. This is just groundworks. The `unlisted` trick was recommended by @TC-MO in a [Slack convo](https://pyvec.slack.com/archives/C03BHBQNNG3/p1750773530207319), hopefully ensuring the duplicated course won't be visible on production. Apparently it behaves differently dev vs prod, so I couldn't really verify it properly locally. I tried running `npm run build` hoping I'd get a prod build of the docs, but I only got errors. Using `npm start` I can see the pages in the navigation, but the warning is in place, so I think Docusaurus picks it up correctly: <img width="781" alt="Screenshot 2025-06-27 at 10 37 52" src="https://github.com/user-attachments/assets/7753def0-c08d-47b5-b0c7-96c98541399a" /> Hopefully in the prod build it won't be in the navigation. But in the case it's not gonna work properly on prod, I'm ready to revert this PR immediately.
honzajavorek
force-pushed
the
honzajavorek/javascript2
branch
from
6e6db97 to
104c5cc
Compare
|
Preview for this PR was built for commit |
This was referenced Jun 27, 2025
Merged
honzajavorek
force-pushed
the
honzajavorek/javascript2
branch
from
104c5cc to
82bf3ee
Compare
|
Preview for this PR was built for commit |
|
Preview for this PR was built for commit |
honzajavorek
added a commit
that referenced
this pull request
Jun 30, 2025
When working on #1584 I realized it'd be better if the lesson started with JSON and continued with CSV, not the other way. In Python it doesn't matter and in JavaScript it's easier to start with JSON, which is built-in, and only then move to CSV, which requires an additional library. So for the sake of having both lessons aligned, I want to change the order in the Python lesson, too. So most of the diff is just the two sections reversed, and the two exercises reversed. I made only a few additional changes to the wording.
honzajavorek
force-pushed
the
honzajavorek/javascript2
branch
from
d284f74 to
b689317
Compare
|
Preview for this PR was built for commit |
|
Preview for this PR was built for commit |
|
Preview for this PR was built for commit |
honzajavorek
force-pushed
the
honzajavorek/javascript2
branch
from
ee7ae7d to
fa29e5a
Compare
|
Preview for this PR was built for commit |
daveomri
pushed a commit
to daveomri/apify-docs
that referenced
this pull request
Sep 3, 2025
daveomri
pushed a commit
to daveomri/apify-docs
that referenced
this pull request
Sep 3, 2025
…ript (apify#1761) Part of apify#1584⚠️ 🐍 Includes a small change also to an exercise in the original `scraping_basics_python` lesson --------- Co-authored-by: gullmar <[email protected]>
daveomri
pushed a commit
to daveomri/apify-docs
that referenced
this pull request
Sep 3, 2025
daveomri
pushed a commit
to daveomri/apify-docs
that referenced
this pull request
Sep 3, 2025
…ipt (apify#1760) Part of apify#1584, fixes apify#1648⚠️ 🐍 Includes respective changes also to the original `scraping_basics_python` lesson --------- Co-authored-by: Michał Olender <[email protected]>
daveomri
pushed a commit
to daveomri/apify-docs
that referenced
this pull request
Sep 3, 2025
As I progressed with apify#1584 I felt the code examples were starting to be more and more complex. Then I remembered that when I was young, us jQuery folks used to lean towards a naming convention where variables holding jQuery selections were prefixed with $. I changed the code examples in all lessons to adhere to this as I feel it makes them more readable and less cluttered. ----- ℹ️ The changes still use `$.map` and `$.each`, because they were made prior to the facb3c0 commit. It's gonna happen, but not yet.
daveomri
pushed a commit
to daveomri/apify-docs
that referenced
this pull request
Sep 3, 2025
As I progressed with apify#1584 I felt the code examples were starting to be more and more complex. Then I remembered that when I was young, us jQuery folks used to lean towards a naming convention where variables holding jQuery selections were prefixed with $. I changed the code examples in all lessons to adhere to this as I feel it makes them more readable and less cluttered. ----- ℹ️ The changes still use `$.map` and `$.each`, because they were made prior to the facb3c0 commit. It's gonna happen, but not yet.
daveomri
pushed a commit
to daveomri/apify-docs
that referenced
this pull request
Sep 3, 2025
As I progressed with apify#1584 I felt the code examples were starting to be more and more complex. Then I remembered that when I was young, us jQuery folks used to lean towards a naming convention where variables holding jQuery selections were prefixed with $. I changed the code examples in all lessons to adhere to this as I feel it makes them more readable and less cluttered. ----- ℹ️ The changes still use `$.map` and `$.each`, because they were made prior to the facb3c0 commit. It's gonna happen, but not yet.
daveomri
pushed a commit
to daveomri/apify-docs
that referenced
this pull request
Sep 3, 2025
As I progressed with apify#1584 I felt the code examples were starting to be more and more complex. Then I remembered that when I was young, us jQuery folks used to lean towards a naming convention where variables holding jQuery selections were prefixed with $. I changed the code examples in all lessons to adhere to this as I feel it makes them more readable and less cluttered. ----- ℹ️ The changes still use `$.map` and `$.each`, because they were made prior to the facb3c0 commit. It's gonna happen, but not yet. --------- Co-authored-by: gullmar <[email protected]>
daveomri
pushed a commit
to daveomri/apify-docs
that referenced
this pull request
Sep 3, 2025
…ript (apify#1848) Part of apify#1584 ----⚠️ 🐍 This PR contains also changes to the Python course, to keep the lessons consistent and synced. --------- Co-authored-by: Michał Olender <[email protected]>
daveomri
pushed a commit
to daveomri/apify-docs
that referenced
this pull request
Sep 3, 2025
…ut JavaScript (apify#1846) Part of apify#1584 ----⚠️ 🐍 This PR contains also a small change to the Python course, to keep the lessons consistent and synced. --------- Co-authored-by: gullmar <[email protected]>
honzajavorek
added a commit
that referenced
this pull request
Sep 3, 2025
…cript (#1847) Part of #1584 ----⚠️ 🐍 This PR contains also changes to the Python course, to keep the lessons consistent and synced. --------- Co-authored-by: Michał Olender <[email protected]> Co-authored-by: gullmar <[email protected]>
honzajavorek
force-pushed
the
honzajavorek/javascript2
branch
from
9d7c368 to
479a736
Compare
|
Preview for this PR was built for commit |
honzajavorek
force-pushed
the
honzajavorek/javascript2
branch
from
479a736 to
5b59e87
Compare
|
Preview for this PR was built for commit |
honzajavorek
force-pushed
the
honzajavorek/javascript2
branch
from
5b59e87 to
1ed4660
Compare
|
Preview for this PR was built for commit |
honzajavorek
force-pushed
the
honzajavorek/javascript2
branch
from
1ed4660 to
86bb36f
Compare
|
Preview for this PR was built for commit |
honzajavorek
force-pushed
the
honzajavorek/javascript2
branch
from
86bb36f to
2ec727c
Compare
|
Preview for this PR was built for commit |
5 tasks
Collaborator
Author
|
Closing in favor of #1907 |
honzajavorek
added a commit
that referenced
this pull request
Nov 21, 2025
The aim of this PR is to publish the new JS course as described in the PR description of #1584, and to unlist the old JS course. The old one should be still accessible for a grace period. _Replacing the old JS course with a new one, which is identical to the Python course, has been previously sanctioned by both Ondra and Michał._ ### The Plan - [x] The `scraping_basics_javascript` root leads to the new JS course. - [x] The pages of the old JS course move to `legacy/web-scraping-for-beginners`. It's gonna be a read-only archive. Must be `noindex` to avoid cannibalization issues. - [x] The `web-scraping-for-beginners`, i.e. the root of the old JS course URLs, leads to redirects which take people to corresponding pages in the new JS course. This lets us use the SEO juice from the old URLs. - [x] The redirects add `#old-js-course` to the URL. The new JS course pages contain a component which, if `#old-js-course` is present in the URL, displays a _commemorative plaque_ about the change and link the old JS course. This improves UX: "Hey, you have until 1.1.2026 to go through this course. After that please refer to the newly updated JS course <link>." - [ ] At some point in future, we'll nuke the archive of the old JS course and link Internet Archive instead in the _commemorative plaque_. _The Plan is a result of a [long discussion between Michał, Aleš, and me](https://pyvec.slack.com/archives/C03BHBQNNG3/p1756992893312119), which takes into account both the UX of existing users of the JS course and SEO._ ### Related Work - Depends on #1889 - Closes #1584 - Closes #1579 - Fixes #947 - Discovered #1900 - Closes #2009 (PoC) - Contains #2023 - Closes #1550 <!-- CURSOR_SUMMARY --> --- > [!NOTE] > Publishes the new JS course, archives the old one with redirects and an on-page notice, and updates links, content, and Nginx rewrites across the docs. > > - **Academy: New JS course rollout** > - Publishes `academy/webscraping/scraping_basics_javascript/*` (new slugs, content, and index) and updates internal references to it. > - Archives the old JS course under `academy/webscraping/scraping_basics_legacy/*` with `noindex` and a legacy notice. > - Adds `src/components/LegacyJsCourseAdmonition.jsx` and integrates it into new course pages to show a notice when `?legacy-js-course=` is present. > - Updates course metadata (titles/sidebar labels) in Expert/Anti‑scraping lessons and adds caution notes where content depends on the legacy course. > - Updates homepage card and other references to point to `'/academy/scraping-basics-javascript'`. > - **Routing/Redirects (Nginx)** > - Redirects old JS course paths `^/academy/web-scraping-for-beginners...` to `'/academy/scraping-basics-javascript'` with `?legacy-js-course=...`. > - Adds other redirects (e.g., output-schema → dataset-schema, academy php path, advanced web scraping path fix). > - **Content/link maintenance** > - Repoints numerous lessons to new paths (e.g., tutorials, Puppeteer/Playwright, advanced courses) and updates sample URLs in integrations (Make) to the new JS course. > - Minor copy/heading tweaks (e.g., RPA title), and consistent slug/slug changes across documents. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 2840ebd. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY --> --------- Co-authored-by: Michał Olender <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a proof of concept exploring whether using the Python course as a template for a brand new JavaScript course would take less time than trying to improve the original JavaScript course. This work is sanctioned by both @mnmkng and @TC-MO. If viable, this should have the potential to implement #1550 and, of course, deprecate #1579
Done
Challenges
Todo