generated from pyladies/netlify-website-template
-
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
0 parents
commit 9d27a3d
Showing
20 changed files
with
772 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
# This is a comment. | ||
# Each line is a file pattern followed by one or more owners. | ||
|
||
# These owners will be the default owners for everything in | ||
# the repo. Unless a later match takes precedence, | ||
# @pyladies/tech-and-infra-admins and @pyladies/pyladies-global-admin will be requested for | ||
# review when someone opens a pull request. | ||
# @pyladies/[YOUR TEAM NAME] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
.DS_Store |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
# Code of Conduct | ||
|
||
Pyladies is dedicated to providing a respectful, harassment-free community for everyone. We do not | ||
tolerate harassment or bullying of any community member in any form. This does not only extend to | ||
members to local PyLadies communities, but to anyone who chooses to become involved in the larger | ||
PyLadies community of users, developers and integrators through events or interactions. | ||
|
||
Harassment includes offensive verbal/electronic comments related to personal characteristics or choices, | ||
sexual images or comments in public or online spaces, deliberate intimidation, bullying, stalking, | ||
following, harassing photography or recording, sustained disruption of talks, IRC chats, electronic | ||
meetings, physical meetings or other events, inappropriate physical contact, or unwelcome sexual | ||
attention. Participants asked to stop any harassing or bullying behavior are expected to comply | ||
immediately. | ||
|
||
If a participant engages in harassing behavior, representatives of the community may take reasonable | ||
action they deem appropriate, including warning the offender, expulsion from any PyLadies event, or | ||
expulsion from mailing lists, IRC chats, discussion boards and other electronic communications channels | ||
to resolve the issue. This may include expulsion from PyLadies Meetup group membership. | ||
|
||
If you are being harassed, notice that someone else is being harassed, or have any other concerns, please | ||
act to intercede or ask for help from any member of the PyLadies community, IRC chat admins, website | ||
admins, or organizers/representatives of any physical events put on under the auspices of PyLadies. | ||
|
||
This Code of Conduct has been adapted from the [Plone Foundation](https://plone.org/foundation/materials/foundation-resolutions/code-of-conduct) and is licensed under a [Creative | ||
Commons Attribution-Share Alike 3.0 Unported license](https://creativecommons.org/licenses/by-sa/3.0/) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
# PyLadies Chapter Website Contributing Guidelines | ||
|
||
Fill in your contributing guidelines here! |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
MIT License | ||
|
||
Copyright (c) 2020 PyLadies | ||
|
||
Permission is hereby granted, free of charge, to any person obtaining a copy | ||
of this software and associated documentation files (the "Software"), to deal | ||
in the Software without restriction, including without limitation the rights | ||
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | ||
copies of the Software, and to permit persons to whom the Software is | ||
furnished to do so, subject to the following conditions: | ||
|
||
The above copyright notice and this permission notice shall be included in all | ||
copies or substantial portions of the Software. | ||
|
||
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR | ||
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, | ||
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE | ||
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER | ||
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, | ||
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE | ||
SOFTWARE. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,63 @@ | ||
<!-- | ||
Please document the following for your pull request. | ||
--> | ||
|
||
# PyLadies Website Pull Request | ||
_Please document the following. We will aim to be as timely as possible in processing your pull request, however as this is a volunteer staffed project anticipate at least a week for pull requests to start to be reviewed._ | ||
|
||
## Is this pull requesting adding or updating a [PyLadies chapter information](https://github.com/pyladies/pyladies#to-add-a-new-pyladies-location)? | ||
<!-- | ||
Example of response: | ||
Mark which one is correct. | ||
--> | ||
|
||
- [ ] Yes | ||
- [ ] No | ||
|
||
### If you marked yes, is this chapter registered in the PyLadies Chapter Directory? | ||
<!-- | ||
Example of response: | ||
Mark which one is correct. | ||
--> | ||
|
||
- [ ] Yes | ||
- [ ] No | ||
|
||
### If you marked no, please register your chapter using the following form [here](https://forms.gle/LYT6TzjgJ437Y4mr8). The form can only be accessed by being logged into your official PyLadies email account. Were you able to complete the registration? | ||
<!-- | ||
Example of response: | ||
Mark which one is correct. If `No` please detail why you cannot complete the registration. | ||
--> | ||
|
||
- [ ] Yes | ||
- [ ] No, I could not because [add response below]: | ||
|
||
|
||
## Have you confirmed the website builds locally with your chapters? See [here](https://github.com/pyladies/pyladies/netlify-website-template/README.md). | ||
<!-- | ||
Example of response: | ||
Mark which one is correct. Include a screen shot confirming the website builds with your changes. | ||
--> | ||
|
||
- [ ] Yes | ||
- [ ] No | ||
|
||
## Does the Netlify preview look correct? Confirm in the checks below on the netlify/deploy-preview check. | ||
<!-- | ||
Example of response: | ||
Mark which one is correct. Include a screen shot confirming the website builds with your changes. | ||
--> | ||
|
||
- [ ] Yes | ||
- [ ] No | ||
|
||
<!-- | ||
Add any other team you think should be subscribed to this issue | ||
/cc your team | ||
--> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,48 @@ | ||
# netlify-website-template | ||
|
||
Example of PyLadies Website theme powered by Netlify with [a standard pull request template](github.com/pyladies/netlify-website-template/PULL_REQUEST_TEMPLATE). You can preview the template [here](https://netlify-template-simple.netlify.app). | ||
|
||
## What is Netlify? | ||
|
||
Netlify is a simple tool to use for continuous integration and continuous development (CI/CD). It allows you to specify custom build commands as well as run checks in your pull requests. You can additionally get a deploy preview of your website capturing the changes generated in a pull request on a Netlify hosted url. Here's [an example pull request](https://github.com/pyladies/netlify-website-template/pull/1) to see the checks and deploy. | ||
|
||
## Setting up you website with Netlify | ||
|
||
1. Fork the repo. | ||
2. This repo has `gh-pages` set as the [default branch](https://docs.github.com/en/github/administering-a-repository/setting-the-default-branch). | ||
3. Register for a Netlify account. [Open source teams qualify for free OSS accounts](https://www.netlify.com/legal/open-source-policy/), use your `pyladies` chapter email address when creating your account. You'll need to host a Netlify badge on your website which is already included in the emplate. Please note that any overages will be additionally charged. | ||
4. Setup your site with [these directions](https://www.netlify.com/blog/2016/10/27/a-step-by-step-guide-deploying-a-static-site-or-single-page-app/). As this is a simple html and css website there is no need for custom build steps. | ||
4. If you have requested a [custom domain](https://github.com/pyladies/pyladies/README.md) you can configure that within [your Netlify site](https://www.netlify.com/blog/2020/03/26/how-to-set-up-netlify-dns-custom-domains-cname-a-records/). | ||
|
||
## Template Information | ||
|
||
- Main file you'll update is `index.html` where you can add organizer information, your own chapter branding, contact links for your chapter, and replace the skyline image. | ||
- You'll want to place organizer photos can be placed in the `images/bios` directory and update the `images/skyline.jpg` with your own desired skyline image. | ||
- If you rename the skyline image modify the `style.css` to point it to the image, look for the `.skyline` css rule. | ||
- Add your custom `@pyladies/chapter-organizer` team that is created when you add your website to the [PyLadies Chapter Website repo](github.com/pyladies/chapter-websites) e.g. `@pyladies/chicago` | ||
|
||
## Local Development | ||
|
||
If you'd like to see your changes locally you can use `Python3` to serve up the content by: | ||
|
||
```bash | ||
$ cd /root-of-forked-directory | ||
$ python -m http.server # Defaults to port 8000, you can change by providing an additional integer for the desired port | ||
``` | ||
|
||
## Option: Hosting your website on GitHub pages | ||
|
||
GitHub provides a free hosted page for each [GitHub user](https://pages.github.com/). You can setup your page either via: | ||
|
||
1. Using and creating a repo `github_username.github.io`. | ||
2. Using `gh-pages` branch, which is the default branch on this template. | ||
|
||
You can look at your repository > settings > GitHub Pages for more information on generating the `CNAME` file if you have a custom domain. | ||
|
||
## Questions? | ||
|
||
Ask for help in the [PyLadies Slack](slackin.pyladies.com) in the `#project-tech-infra` channel. | ||
|
||
## Acknowledgements | ||
|
||
[PyLadies NYC](http://nyc.pyladies.com/) created this theme initially, thank you! |
Binary file not shown.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.