LBRYCommunity/lbry.tech

Fork

You've already forked lbry.tech

Code Issues 13 Pull requests 8 Projects Releases Packages Wiki Activity

Spacing on headers #44

New issue

Closed

opened 2018-05-16 17:39:34 +02:00 by kauffj · 0 comments

kauffj commented

2018-05-16 17:39:34 +02:00

(Migrated from github.com)

Copy link

When headers are stacked they can be a little tight, see this page: http://beta.lbry.tech/develop.html

The h2, h3, and p are all stacked right next to each other.

When headers are stacked they can be a little tight, see this page: http://beta.lbry.tech/develop.html The h2, h3, and p are all stacked right next to each other.

No Branch/Tag specified

Branches Tags

master

dependabot/npm_and_yarn/cacheable-request-and-got-10.2.7

dependabot/npm_and_yarn/http-cache-semantics-and-updates-4.1.1

dependabot/npm_and_yarn/json5-2.2.3

dependabot/npm_and_yarn/qs-6.5.3

dependabot/npm_and_yarn/decode-uri-component-0.2.2

trackers

dependabot/npm_and_yarn/undefsafe-2.0.5

dependabot/npm_and_yarn/node-fetch-2.6.7

dependabot/npm_and_yarn/markdown-it-12.3.2

BryanLunduke-patch-1

lbry_sdk_directory_refactor

seanyesmunt-patch-1

fix-build

lbrytv-api

devprogram-fixes

fix_some_bugs

android-build-steps-update

No results found.

Labels

Clear labels

Work is part of a proposal

campaign-blocker

consider soon

Discuss this issue at the next planning meeting, then remove this label

Content

dependencies

Pull requests that update a dependency file

Welcome to Hacktoberfest

help wanted

Extra attention is needed

icebox

Long-term storage

level: 1

No knowledge of the existing code required

level: 2

Some knowledge of the existing code is recommended

level: 3

Significant knowledge of the existing code is recommended

level: 4

Intimate knowledge of the existing code is recommended

needs: exploration

Solution unclear, needs research

needs: grooming

Issue needs to be groomed before work can start

needs: priority

Priority level needs to be defined

needs: repro

Issue needs step-by-step instructions on how to reproduce in latest code

needs: tech design

Needs technical design signoff before implementation can begin

on hold

Temporarily paused

priority: blocker

Issue is blocking release, do ASAP

priority: high

Work needs to be moved into sprint ASAP

priority: low

Work should be done but can stay in the backlog for now

priority: medium

Work needs to be done within 2-3 sprints

resilience

Tom's Wishlist

type: bug

Existing functionality is wrong or broken

type: discussion

A conversation. No specific changes requested

type: improvement

Existing (or partially existing) functionality needs to be changed

type: new feature

New functionality that does not exist yet

type: refactor

Minimal user-visible changes, but significant internal work

type: task

Either work that's not related to the code, or a small chore that does not fit into other categories

type: testing

Solution needs additional user testing

unplanned

Work that was not planned into the spirnt, took priority over planned work

No labels

Milestone

Clear milestone

No items

No milestone

lbry.tech May 23rd

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry.tech#44

Reference in a new issue

Repository

LBRYCommunity/lbry.tech

Title

Body

No description provided.

Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?