Update development instructions #96

Closed
opened 2021-07-24 18:26:02 +00:00 by pat-s · 0 comments
Member

The current development instructions could need some more information showcasing the shortest way to make a change in the theme and see a preview of the website.

I'll outline my way for the most recent PR which feels quite unintutive. If there are other ways, we should note them down :)

  1. Make a change in src/main.scss
  2. Run npm run watch to rebuild the theme (including static/styles/main.css which is the one which will trigger a change in the website later on
  3. Copy all assets to the local gitea repo checkout (docs/themes/gitea)
  4. Run make server or hugo server and observe the changes

While the "copy to local checkout" is tricky as local paths are involved, I was wondering if we should suggest to checkout this repo as a git repo within gitea.

This would remove the need for step (3) - but maybe there are better ways?

Another option could be to have Netlify Pull Request previews, i.e. netlify renders Gitea.io with the theme resources from the pull request and displays a live-preview of the changes with a dummy URL in the PR.
I have two other hugo-based blogs running this way and like this setup a lot.
Let me know if I can help.

The current development instructions could need some more information showcasing the shortest way to make a change in the theme and see a preview of the website. I'll outline my way for the most recent PR which feels quite unintutive. If there are other ways, we should note them down :) 1. Make a change in `src/main.scss` 2. Run `npm run watch` to rebuild the theme (including `static/styles/main.css` which is the one which will trigger a change in the website later on 3. Copy all assets to the local gitea repo checkout (`docs/themes/gitea`) 4. Run `make server` or `hugo server` and observe the changes While the "copy to local checkout" is tricky as local paths are involved, I was wondering if we should suggest to checkout this repo as a git repo within `gitea`. This would remove the need for step (3) - but maybe there are better ways? Another option could be to have Netlify Pull Request previews, i.e. netlify renders Gitea.io with the theme resources from the pull request and displays a live-preview of the changes with a dummy URL in the PR. I have two other hugo-based blogs running this way and like this setup a lot. Let me know if I can help.
6543 referenced this issue from a commit 2021-09-12 17:08:33 +00:00
6543 closed this issue 2021-09-12 17:08:33 +00:00
This repo is archived. You cannot comment on issues.
No description provided.