Skip to content

Commit 3652344

Browse files
authored
DESIGN: New Splash page(pyOpenSci#83)
This adds a new fresh layout to our landing page. We still need to add some more content around who we serve and how peer review works. Some of this will be in the community handbook so will continue to work on this all.
1 parent a9c837a commit 3652344

13 files changed

+199
-83
lines changed

.gitignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,3 +5,4 @@ _config-dev.yml
55
_config.yml
66
Gemfile.lock
77
.DS_Store
8+
images/full-images/

_data/navigation.yml

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,12 @@
11
# main links
22
main:
3-
4-
- title: "Get In Touch"
5-
url: /get-involved-contact/
6-
- title: "Contributors"
7-
url: /contributors/
83
- title: "Resources"
94
url: /resources/
105
- title: "Our Packages"
116
url: /python-packages/
127
- title: "Blog"
138
url: /blog/
9+
- title: "Contributors"
10+
url: /contributors/
11+
- title: "Get In Touch"
12+
url: /get-involved-contact/

_data/packages.yml

Lines changed: 25 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,51 +2,75 @@
22
description: 'Jointly: A Python package for synchronizing multiple sensors with accelerometer data'
33
maintainer: ["Arne Herdick", "Felix Musmann", "Ariane Sasso", "Justin Albert", "Bert Arnrich"]
44
link: "https://github.com/hpi-dhc/jointly"
5+
date-accepted:
6+
highlight:
57
- package-name: devicely
68
description: 'Devicely: A Python package for reading, timeshifting and writing sensor data'
79
maintainer: ["Ariane Sasso", "Jost Morgenstern", "Felix Musmann", "Bert Arnrich"]
810
link: "https://github.com/hpi-dhc/devicely"
11+
date-accepted:
12+
highlight:
913
- package-name: earthpy
1014
description: 'Explore and plot raster and vector spatial data using open source Python tools.'
1115
maintainer: ["Leah Wasser", "Max Joseph"]
1216
link: "https://github.com/earthlab/earthpy"
1317
- package-name: nbless
1418
description: 'Construct, deconstruct, convert, execute, and prepare slides from Jupyter notebooks.'
1519
maintainer: ["Martin Skarzynski"]
20+
date-accepted:
21+
highlight:
1622
link: "https://github.com/py4ds/nbless"
1723
- package-name: pandera
1824
description: 'Validate the types, properties, and statistics of pandas data structures'
1925
maintainer: ["Niels Bantilan"]
26+
date-accepted:
27+
highlight: True
2028
link: "https://github.com/cosmicBboy/pandera"
21-
- package-name: movingpandas
29+
- package-name: MovingPandas
2230
description: 'Trajectory classes and functions built on top of GeoPandas'
2331
maintainer: ["Anita Graser"]
32+
date-accepted:
33+
highlight: True
2434
link: "https://github.com/anitagraser/movingpandas"
2535
- package-name: physcraper
2636
description: 'Physcraper: a Python package for continually updated phylogenetic trees using the Open Tree of Life'
2737
maintainer: ["Luna Luisa Sánchez-Reyes", "Martha Kandziora", "Emily Jane McTavish"]
2838
link: "https://github.com/McTavishLab/physcraper"
39+
date-accepted:
40+
highlight:
2941
- package-name: pyrolite
3042
description: 'Tools for getting the most from your geochemical data'
3143
maintainer: ["Morgan Williams"]
44+
date-accepted:
45+
highlight:
3246
link: "https://github.com/morganjwilliams/pyrolite"
3347
- package-name: pystiche
3448
description: 'A Framework for Neural Style Transfer'
3549
maintainer: ["Philip Meier"]
3650
link: "https://github.com/pmeier/pystiche"
51+
date-accepted:
52+
highlight:
3753
- package-name: pydov
3854
description: 'Python package to retrieve data from Databank Ondergrond Vlaanderen (DOV)'
3955
maintainer: ["DOV-Vlaanderen"]
4056
link: "https://github.com/DOV-Vlaanderen/pydov"
57+
date-accepted:
58+
highlight:
4159
- package-name: openomics
4260
description: 'A bioinformatics library to integrate multi-omics datasets & interface with public annotation databases.'
4361
maintainer: ["Nhat Tran"]
4462
link: "https://github.com/BioMeCIS-Lab/OpenOmics"
63+
date-accepted:
64+
highlight:
4565
- package-name: phenopype
4666
description: 'A phenotyping pipeline for Python.'
4767
maintainer: ["Moritz Lürig"]
4868
link: "https://github.com/mluerig/phenopype"
69+
date-accepted:
70+
highlight: True
4971
- package-name: pygmt
5072
description: 'A Python interface for the Generic Mapping Tools.'
5173
maintainer: ["Dongdong Tian", "Max Jones", "Michael Grund", "Wei Ji Leong", "Will Schlitzer"]
5274
link: "https://github.com/GenericMappingTools/pygmt"
75+
date-accepted:
76+
highlight: True

_pages/contributors.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ a community of practice around scientific software in Python.
1717
of today!
1818

1919

20-
## How can I contribute?
20+
## How Can I Contribute?
2121

2222
There are many different ways to get involved with pyOpenSci! Contributions
2323
of all kinds are welcome - big and small, technical and non-technical.

_pages/home.md

Lines changed: 80 additions & 76 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
layout: single
2+
layout: splash
33
title: "Welcome to pyOpenSci"
44
author_profile: false
55
published: true
@@ -9,81 +9,85 @@ header:
99
overlay_image: images/header.jpg
1010
overlay_filter: 0.6
1111
actions:
12-
- label: "Resources"
13-
url: "/resources/"
14-
- label: "GitHub"
15-
url: "https://github.com/pyOpenSci"
12+
- label: "Submit a Package"
13+
url: "https://github.com/pyOpenSci/software-review/issues"
14+
- label: "Read our Handbook"
15+
url: "/contributing-guide/intro)"
16+
mission:
17+
- excerpt: 'We build diverse community that supports free and open Python tools for processing scientific data. We also build technical skills needed to contribute to open source and that support open science. Join our global community.'
18+
programs:
19+
- image_path: images/brooke-cagle-group-unsplash.png
20+
image_caption: "Brooke Cagle, Unsplash"
21+
alt: "placeholder image 1"
22+
title: "Diverse Community"
23+
excerpt: "We are building a diverse and supportive community with skills that support open source and open science. Join the discussion on [twitter](https://www.twitter.com/pyopensci) or follow along on [discourse](https://pyopensci.discourse.group/)."
24+
- image_path: images/desola-lanre-ologun-unsplash.png
25+
image_caption: "Desola Lanre Ologun, Unsplash"
26+
alt: "placeholder image 2"
27+
title: "Open Peer Review"
28+
excerpt: "Our open peer review process of Python tools supports standardized software quality and usability. It also provides needed credit and visibility to tool maintainers. Finally it removes redundancy of packages with similar functionaly across the scientific Python ecosystem."
29+
url: https://www.pyopensci.org/contributing-guide/open-source-software-submissions/author-guide.html
30+
btn_label: "Read More About Our Peer Review"
31+
btn_class: "btn--primary"
32+
- image_path: images/brooke-cagle-unsplash.png
33+
title: "Skills for Open Source and Open Science"
34+
image_caption: "Brooke Cagle, Unsplash"
35+
excerpt: "We will develop a mentorship and training program over the next year to support those who are new to open science and code review. Stay tuned for more."
1636
---
1737

18-
## About pyOpenSci
38+
{% include feature_row id="mission" type="center" %}
39+
{% include feature_row id="programs"%}
40+
41+
<div class="notice--info" markdown="1">
42+
## Recent Blog Posts & Updates
43+
44+
<div class="feature__wrapper">
45+
{% for post in site.categories['highlight'] limit:3 %}
46+
<div class="feature__item">
47+
<div class="archive__item">
48+
<div class="archive__item-body">
49+
<h3 class="archive__item-title"><a href="{{ site.baseurl }}{{ post.url}}" rel="permalink">{{ post.title }}</a></h3>
50+
<div class="archive__item-excerpt">
51+
<p>{{ post.excerpt | markdownify }}</p>
52+
</div>
53+
</div>
54+
</div>
55+
</div>
56+
{% endfor %}
57+
</div>
58+
59+
<p><a href="/python-packages/" class="btn btn--info btn--large">View All Posts <i class="fa fa-4 fa-arrow-circle-right" aria-hidden="true"></i></a></p>
60+
</div>
61+
62+
63+
<!-- packages reviewed -->
64+
65+
66+
## Recently Accepted Python Packages
67+
68+
<div class="grid__wrapper">
69+
<!-- Only print packages that are highlighted -->
70+
{% for apackage in site.data.packages %}
71+
{% if apackage.highlight %}
72+
<div class="grid__item cards">
73+
<article class="archive__item" itemscope="" itemtype="https://schema.org/CreativeWork">
74+
<h2 class="archive__item-title no_toc" itemprop="headline">
75+
<a href="{{ apackage.link }}" rel="permalink">{{ apackage.package-name }}</a>
76+
</h2>
77+
<p class="page__meta">
78+
<span class="page__meta-readtime"><i class="fas fa-feather" aria-hidden="true"></i>
79+
<!-- Commas in between authors -->
80+
{% for aMaintainer in apackage.maintainer %}
81+
{{ aMaintainer }}{% if forloop.last == false %}, {% endif %}
82+
{% endfor %}
83+
</span>
84+
</p>
85+
<p class="archive__item-excerpt" itemprop="description">{{ apackage.description | markdownify }}</p>
86+
</article>
87+
88+
</div>
89+
{% endif %}
90+
{% endfor %}
91+
</div>
92+
<a href="/python-packages/" class="btn btn--info">View All Accepted Packages <i class="fa fa-4 fa-arrow-circle-right" aria-hidden="true"></i></a>
1993

20-
pyOpenSci promotes open and reproducible research through peer-review of
21-
scientific Python packages. We also build technical capacity by providing a
22-
curated repository of high-quality packages and enabling scientists to write
23-
and share their own software. We hope to foster a greater sense of community
24-
among scientific Python users so that we can help each other become better
25-
programmers and researchers. See our [list of Python packages]({% link _pages/python-packages.md %})
26-
for an idea of the open-source projects that pyOpenSci has assisted.
27-
28-
pyOpenSci is being modeled after the successful [rOpenSci](https://ropensci.org/) community.
29-
30-
## Get Involved
31-
32-
There are many different ways to get involved with pyOpenSci.
33-
34-
1. **[Join a community meeting](#community-meetings)**: We have monthly video meetings that you are welcome to attend.
35-
2. **[Join our community forum](https://pyopensci.discourse.group/)**. This is an online space
36-
for discussion within the pyOpenSci community. Announcements for new meetings will be posted here.
37-
3. **Submit a package to pyOpenSci**. We are looking for Python packages that
38-
support scientific Python community. Read more about our
39-
[review process and scope](https://www.pyopensci.org/contributing-guide/open-source-software-peer-review/aims-and-scope.html).
40-
4. <a href="https://forms.gle/6NknPgrZguaQayjP8" target="_blank">**Volunteer to be a reviewer for pyOpenSci**</a>. We are looking for people who
41-
can help review software packages as they are submitted.
42-
5. **Help with technical infrastructure**. pyOpenSci has a few pieces of technical
43-
infrastructure (like this site) which need maintenance and development.
44-
6. **Spread the word**! pyOpenSci is a community-driven project. Tell your friends,
45-
recommend that a colleague submit a package, mention us at conferences, spread the word!
46-
7. Help us build our online presence! We need help spreading the word to the community using social media. Help us by talking about pyopensci at a meeting and / or supporting our social media presence. Do you have graphic skills? We will also need a logo at some point!
47-
48-
### Community meetings
49-
50-
Currently, the pyOpenSci team holds community meetings roughly every 2 weeks. These are
51-
held remotely, and open to anyone who would like to attend. We discuss ideas for improving
52-
the process / technology / community management / etc of the pyOpenSci community, and
53-
would value your participation!
54-
55-
The best place to find information about the next community meeting is
56-
[in the community forum](https://pyopensci.discourse.group). We post dates / times
57-
for new meetings there.
58-
59-
### Who's Involved
60-
61-
See our [contributors page]({% link _pages/contributors.md %}) for a list of the contributors
62-
in the pyOpenSci community.
63-
64-
## FAQ
65-
66-
### What's the difference between pyOpenSci and JOSS?
67-
68-
The [Journal of Open Source Software](https://joss.theoj.org/) is a community dedicated
69-
to improving the visibility and quality of scientific software. They do
70-
so by providing a review and publishing process similar to pyOpenSci so that authors
71-
of packages can publish their packages with a DOI and citable artifact.
72-
JOSS reviews are [more limited scope](https://joss.readthedocs.io/en/latest/review_criteria.html) compared to pyOpenSci and the
73-
[submission criteria](https://joss.readthedocs.io/en/latest/review_criteria.html)
74-
are, in places, less stringent than those of pyOpenSci.
75-
76-
pyOpenSci encourages a more hands-on approach in the review process, and
77-
focuses more around software best-practices than publishing.
78-
We encourage our reviewers to provide more hands-on assistance and
79-
give more in-depth feedback than is typically required in JOSS. The goal
80-
of pyOpenSci is to ensure that all of its packages meet a minimum level
81-
of best practices and standards, and our review processes often take longer
82-
in order to help authors reach this bar. pyOpenSci also accepts some packages
83-
that JOSS does not such as API wrappers to access data.
84-
85-
pyOpenSci has a close relationship with JOSS, and we see these two communities
86-
as complementary of one another. **Any package that passes the pyOpenSci review and is [within scope](https://joss.readthedocs.io/en/latest/submitting.html#submission-requirements) for JOSS
87-
can be fast-tracked through the JOSS review process** (with the exception of a few
88-
JOSS-specific tasks you may need to perform). We hope that this encourages
89-
authors to submit to both JOSS and pyOpenSci.

_posts/2019-10-25-welcome-to-pyopensci.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,7 @@ header:
99
overlay_color: "#333"
1010
categories:
1111
- updates
12+
- blog-post
1213
---
1314

1415
## Welcome To PyOpenSci!

_posts/2019-11-18-pandera-dataframe-validation.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,7 @@ categories:
1313
- pandas
1414
- data-validation
1515
- dataframes
16+
- highlight
1617
---
1718

1819
Modern data engineering and analysis workflows will often involve using data

_posts/2020-04-29-movingpandas-movement-data-analysis.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,7 @@ categories:
1212
- blog-post
1313
- pandas
1414
- spatial
15+
- highlight
1516
---
1617

1718
Movement data is everywhere: from tracking apps that record human or vehicle movement to ecologists monitoring wildlife behaviour. Movement data analysis is challenging since movement data combines time series and spatial data analyses questions. Existing spatial analysis libraries, such as GeoPandas, are great at handling spatial data but they don't support moving objects.

_posts/2022-09-10-executive-director-pyopensci-leah-wasser-updates.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,7 @@ header:
1010
categories:
1111
- updates
1212
- blog-post
13+
- highlight
1314
redirect_from:
1415
- /pyopensci-updates/executive-director-pyopensci-leah-wasser-updates/
1516
---

assets/css/main.scss

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,90 @@ body {font-size:90%}
1010

1111
}
1212

13+
/* package cards splash */
14+
15+
.grid__wrapper {
16+
display: flex;
17+
}
18+
19+
.card p {
20+
font-size: .9em
21+
}
22+
23+
.cards h2 a {
24+
text-decoration: none;
25+
font-size: 1.2em;
26+
}
27+
28+
/* author list */
29+
.cards .page__meta-readtime {
30+
font-size: 1.1em;
31+
}
32+
33+
.cards {
34+
display: block;
35+
top: 0px;
36+
position: relative;
37+
max-width: 262px;
38+
background-color: #f2f8f9;
39+
border-radius: 4px;
40+
padding: 32px 24px;
41+
margin: 12px;
42+
text-decoration: none;
43+
z-index: 0;
44+
overflow: hidden;
45+
border: 1px solid #f2f8f9;
46+
47+
&:hover {
48+
transition: all 0.2s ease-out;
49+
box-shadow: 0px 4px 8px rgba(38, 38, 38, 0.2);
50+
top: -4px;
51+
border: 1px solid #cccccc;
52+
background-color: white;
53+
}
54+
55+
&:before {
56+
content: "";
57+
position: absolute;
58+
z-index: -1;
59+
top: -16px;
60+
right: -16px;
61+
background: #00838d;
62+
height: 32px;
63+
width: 32px;
64+
border-radius: 32px;
65+
transform: scale(2);
66+
transform-origin: 50% 50%;
67+
transition: transform 0.15s ease-out;
68+
}
69+
70+
&:hover:before {
71+
transform: scale(2.15);
72+
}
73+
}
74+
75+
/* Fix buttons and text in notice boxes */
76+
.notice--info .btn.btn--info {
77+
color:#fff;
78+
}
79+
80+
.notice--info .archive__item-excerpt {
81+
font-size: .95em;
82+
}
83+
84+
.notice--info h2 {
85+
font-size: 1.5em;
86+
}
87+
88+
.notice--info h3 a, .notice--info h2 a:visited {
89+
font-size: 1.5em;
90+
text-decoration: none;
91+
font-size: 1.0em;
92+
}
93+
/* Adding a 3 col grid */
94+
95+
96+
1397
@charset "utf-8";
1498
@import "minimal-mistakes/skins/{{ site.minimal_mistakes_skin | default: 'default' }}"; // skin
1599
@import "minimal-mistakes"; // main partials

0 commit comments

Comments
 (0)