Repository navigation
Replies: 1 comment 1 reply
|
You used the template, not a fork. I checked your repository through GitHub's API: That decides which instructions apply. A template copy shares no git history with al-folio, so there's no "Sync fork" button, and pulling in two major versions of changes isn't practical. The upgrade docs recommend this path for pre-v1 sites: start from the v1 starter and copy your own files into it. That approach also works entirely in the browser. 1. Keep your current site running. Don't rename or edit 2. Make a fresh copy of the current al-folio. On https://github.com/alshedivat/al-folio, click Use this template → Create a new repository, name it something like 3. Turn on deployment for it, as described in the docs:
4. Point it at its test address. In url: https://jmangum.github.io
baseurl: /site-v1/Commit, and wait for the Deploy action to finish. Then go to Settings → Pages, set the branch to 5. Copy your content over. On your old repo, use Code → Download ZIP. In
For Check the test site page by page. 6. Swap it in. When the test copy looks right:
Optional, also in the browser: to run al-folio's own upgrade checker, open If this gets you onto v1, marking it as the answer will help the next person upgrading a pre-v1 template site. |
Uh oh!
There was an error while loading. Please reload this page.
Sorry for the very basic question, but I installed
al-folioon my github pages site on April 9, 2025. I used whatever the preferred install method was at that time, which I presume was either fork or template. Would like to upgrade to the current version as there appears to have been quite a bit ofal-foliodevelopment. Several questions:Thank you!
All reactions