metafizzy / metafizzy/next-project

Better type layout tools

Open
#10 4 comments 1 reaction 0 assignees View on GitHub
Dominant language
No language data
Stars
16
Forks
1
PR merge metrics
No merged PRs in 30d

Description

There are some aspects of HTML & CSS formatted text layouts that I think could be improved until an adequate standard is determined and implemented.

For instance, there is currently support for multiple text columns within a block, however this doesn't support column rows or heights, nor does it support spanning fluid text across multiple separately located blocks. Some kind of functionality that could extend to allow for linking columns to pour remaining text into, and maybe some programmatic way to nudge text properties to reduce possibility of orphans and widows could help further the web text revolution.

Responsive designs also demand new solutions to text layout challenges. In particular, a better system to manage text issues such as dynamically inserting line breaks (although technically you could use a non-breaking space within, however it's not entirely understandable for users who may not understand the difference between using a regular space and a ` ` (non-breaking space) in terms of web integration). This is hard to explain, but I did a hand-coded convoluted solution to try to avoid most widows/orphans for this site at different breakpoints: http://instituteofcomfort.rinnai.com.au/

I mean, we've got custom fonts now, but typography controls on web are still pretty basic and I think could be a really awesome tool to start the next web design revolution.

I've got a couple other ideas regarding text layout things but it's probably best to show them than talk about them.

Contributor guide

No contributing guide indexed for this repository

Research direction

No repository files, tests, or implementation entry points are named. Start by reviewing the existing project scope and the linked example site, then turn the ideas about columns, text flow, line breaks, and widows/orphans into one specific proposal with clear acceptance criteria. Done is not defined until the intended behavior and boundaries are agreed.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, html
Domain
design, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.