Skip to content

dev-build config files + file cleanup + content draft updates#53

Merged
emiliom merged 4 commits intooceanhackweek:devfrom
emiliom:em_updates
Mar 26, 2020
Merged

dev-build config files + file cleanup + content draft updates#53
emiliom merged 4 commits intooceanhackweek:devfrom
emiliom:em_updates

Conversation

@emiliom
Copy link
Copy Markdown
Member

@emiliom emiliom commented Mar 26, 2020

Merging into new dev branch, for now

emiliom added 4 commits March 23, 2020 15:09
-  Cleaned up file names for sections: section-01.html, section-02.html, etc. Removed unused section file
- Front-page "button" definitions moved from config.yml to section-01.html
- Small clean up of config.yml
New jekyll config file to be used for development builds pushed to https://staff.washington.edu/emiliom/out/ohw20draft/ for convenient, static inspection by others. Also small updates to README and InstructionSiteUpdates.md (renamed)
Many content updates, specially front-page sections. Added covid19 section.
@emiliom emiliom changed the title dev-build config files + content draft updates dev-build config files + file cleanup + content draft updates Mar 26, 2020
@emiliom
Copy link
Copy Markdown
Member Author

emiliom commented Mar 26, 2020

@ocefpaf - I thought I had merged this PR. Hmm. I'll merge now.

It's my best attempt at pushing my changes to the repo without impacting the live site.

@emiliom emiliom merged commit e0c34f7 into oceanhackweek:dev Mar 26, 2020
Comment thread .gitignore
.sass-cache/
_site/

_config_localdev.yml
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is OK to commit this file. If I recall correctly one can use it to build and serve locally.
(However, I'm pretty sure we can make due with a single one too.)

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I recall correctly one can use it to build and serve locally. (However, I'm pretty sure we can make due with a single one too.)

Yes, I created it for that purpose, to be able to correctly view locally without needing to execute jekyll serve (after much trial and error). I used that in turn to build the site such that I could push the files to a web location and have it work, as it did in the draft site. It boiled down to custom base_url and url values in _config.yml, and it's possible that they can be supplied as arguments to jekyll build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants