LBRYCommunity/lbry.tech
1
0
Fork 0
Code Issues 13 Pull requests 8 Projects Releases Packages Wiki Activity

Closes #44 and #46

Browse source
This commit is contained in:
ポール ウェッブ 2018-05-17 14:09:18 -05:00
parent d1eb063e56
commit 6aeaf0e334
4 changed files with 48 additions and 26 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

28
.vuepress/scss/pages/_page.scss
View file

@ -60,6 +60,10 @@
h2 {
font-size: 1.5rem;
+ h3 {
margin-bottom: 1rem; padding-top: 0.25rem;
}
}
h3 {
@ -85,16 +89,30 @@
}
p, ol, ul {
line-height: 1.33;
margin-bottom: 2rem;
position: relative;
@media (min-width: 901px) {
font-size: 1.25rem;
line-height: 1.55;
}
@media (max-width: 900px) {
font-size: 1.05rem;
line-height: 1.33;
}
}
ol, ul {
padding-top: 0.5rem;
li {
&:not(:last-of-type) {
margin-bottom: 0.25rem;
}
}
+ h2, + h3, + h4, + h5 {
padding-top: 2rem;
}
}
@ -108,9 +126,15 @@
}
p {
margin-bottom: 2rem;
img {
float: right;
}
+ ol, + ul {
top: -2rem;
}
}
a:not(.button) {

6
.vuepress/scss/partials/_footer.scss
View file

@ -6,7 +6,7 @@
padding-left: env(safe-area-inset-left);
> div:first-of-type {
@media (max-width: 900px) {
@media (max-width: 980px) {
overflow: auto;
overflow-scrolling: touch;
white-space: nowrap;
@ -19,7 +19,7 @@
padding-top: 2rem;
padding-bottom: 2rem;
@media (min-width: 901px) {
@media (min-width: 981px) {
align-items: stretch;
display: flex;
flex-flow: row wrap;
@ -30,7 +30,7 @@
padding-left: 0.5rem;
vertical-align: bottom;
@media (max-width: 900px) {
@media (max-width: 980px) {
display: inline-block;
transform: translate3d(0, 0, 0);
transition: opacity 0.2s 0.2s ease, transform 0.4s 0.2s cubic-bezier(0.215, 0.61, 0.355, 1);

21
.vuepress/theme/Layout.vue
View file

@ -3,11 +3,12 @@
<nav class="navigation">
<div class="inner-wrap">
<router-link class="navigation__item" to="/" title="Go back home">LBRY</router-link>
<router-link class="navigation__item" to="/overview.html" title="TBD">Overview</router-link>
<router-link class="navigation__item" to="/documentation.html" title="TBD">Documentation</router-link>
<router-link class="navigation__item" to="/contribute.html" title="TBD">Contribute</router-link>
<router-link class="navigation__item" to="/develop.html" title="TBD">Develop</router-link>
<router-link class="navigation__item" to="/resources" title="TBD">Resources</router-link>
<router-link class="navigation__item" to="/overview.html" title="LBRY overview">Overview</router-link>
<router-link class="navigation__item" to="/documentation.html" title="View LBRY docs">Documentation</router-link>
<router-link class="navigation__item" to="/contribute.html" title="Contribute to LBRY">Contribute</router-link>
<router-link class="navigation__item" to="/develop.html" title="Develop with LBRY">Develop</router-link>
<router-link class="navigation__item" to="/resources" title="View LBRY resources">Resources</router-link>
</div>
</nav>
@ -143,11 +144,11 @@
<edit-link :path="this.$page.path"></edit-link>
</li>
<li><a href="">Get</a></li>
<li><a href="">Learn</a></li>
<li><a href="">News</a></li>
<li><a href="">Chat</a></li>
<li><a href="">GitHub</a></li>
<li><router-link to="/overview.html" title="LBRY overview">Overview</router-link></li>
<li><router-link to="/documentation.html" title="View LBRY docs">Documentation</router-link></li>
<li><router-link to="/contribute.html" title="Contribute to LBRY">Contribute</router-link></li>
<li><router-link to="/develop.html" title="Develop with LBRY">Develop</router-link></li>
<li><router-link to="/resources" title="View LBRY resources">Resources</router-link></li>
<li><a href="/sitemap.html">Sitemap</a></li>
<li>MIT Licensed</li>

13
contribute.md
View file

@ -32,14 +32,11 @@ GitHub is the preferred channel for [bug reports](#report-a-bug) and [feature re
### Reporting a Bug
A bug is a _demonstrable problem_ that is caused by the code in the repository. Good bug reports are extremely helpful - thank you!
Guidelines for bug reports:
1. **Identify the correct repo**. See [ecosystem overview](#ecosystem-overview). While it's okay if you get this wrong, it's a big help to us if you get it right.
1. **Use the GitHub issue search** &mdash; check if the issue has already been reported (or fixed). Be sure to include closed tickets in your search.
1. **Follow the instructions** - When you open an issue inside of GitHub, each repo contains a template for how to create a good bug report. Please follow it!
2. **Use the GitHub issue search** &mdash; check if the issue has already been reported (or fixed). Be sure to include closed tickets in your search.
3. **Follow the instructions** - When you open an issue inside of GitHub, each repo contains a template for how to create a good bug report. Please follow it!
Well-specified bug reports save developers lots of time and are extremely appreciated, typically with an LBRY credit tip.
@ -49,9 +46,9 @@ Feature requests are welcome. Before you submit one be sure to:
1. **Identify the correct repo**. See [ecosystem overview](#ecosystem-overview).
1. **Use the Github Issues search** and check the feature hasn't already been requested. Be sure to include closed tickets.
2. **Consider whether it's feasible** for us to tackle this feature in the next 6-12 months. The LBRY team is currently stretched thin just adding basic functionality. If this is a nice to have rather than a need, it is probably more clutter than helpful.
3. **Make a strong case** to convince the project's leaders of the merits of this feature. Please provide as much detail and context as possible. This means explaining the use case and why it is likely to be common.
2. **Use the Github Issues search** and check the feature hasn't already been requested. Be sure to include closed tickets.
3. **Consider whether it's feasible** for us to tackle this feature in the next 6-12 months. The LBRY team is currently stretched thin just adding basic functionality. If this is a nice to have rather than a need, it is probably more clutter than helpful.
4. **Make a strong case** to convince the project's leaders of the merits of this feature. Please provide as much detail and context as possible. This means explaining the use case and why it is likely to be common.
## Coding