New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Better Forking & branch/history management instructions #9

Open

jorydotcom opened this issue Nov 24, 2020 · 0 comments

Contributor

jorydotcom commented Nov 24, 2020 •

edited

Loading

The template repo and its children repos are a bit confusing from a workflow/ contribution perspective.

Need to establish something clearer for:

establishing a new OP website from scratch
what content goes in the theme vs. in the 'template'
consuming upstream theme changes (e.g., when OASIS updates its logo or branding)
consuming upstream documentation changes (e.g. how to post a blog)
when/on what occasion downstream changes should be shared upstream
managing git history

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