JuliaHealth / juliahealth.github.io

Website for the JuliaHealth organization (powered by Franklin.jl).
https://juliahealth.org
14 stars 9 forks source link

[Bug] page doesn't open on the browser directly #119

Open Farreeda opened 1 year ago

Farreeda commented 1 year ago

This error appears julia> serve() ┌ Franklin Warning: in <config.md> │ No 'config.md' file found. It is recommended to keep one. │ │ Relevant pointers: │ - workflow and folder structure: https://franklinjl.org/workflow/ └ ERROR: ArgumentError: The current directory doesn't have a_layoutor_cssfolder; change directory to a valid Franklin folder. Each time it only works when changing the commit by those steps written by @TheCedarPrince

  1. Move to the dev branch of the website
  2. Run git log to make sure I am on commit "Remove Franklin compat entry"
  3. If not, add the remote by doing "git remote add juliahealth https://github.com/JuliaHealth/juliahealth.github.io"
  4. Then, pull from the remote by doing "git fetch juliahealth"
  5. Then, merge the local dev branch with juliahealth/dev by doing "git merge juliahealth/dev" from your local dev branch
  6. Open Julia then activate the environment
  7. Instantiate or update the environment at this point
  8. Run "using Franklin" and then "serve()"
TheCedarPrince commented 1 year ago

Oh! Since you are working on a fork, each time you want to update your branches to match the one on the original repo, you have to pull in the changes from the original repo by doing remote fetch juliahealth. Once that is done, you can merge your branches with the origin branch you are targeting. You also may need to rebase the forked version of the branch on the original fetched branch you are wanting to match to.

Otherwise, I do not encounter this bug. Things seem to be working fine on my end; wonder if there may be some kind of git issue. If the above doesn't work, maybe try recloning the repo onto your computer and then making sure you can pull recent information. Let me know how things work/don't work out for you! :smile:

Thanks for opening the issue!