aio: Consider implementation of max-wid centered content concept for documentation pages · Issue #22246 · angular/angular · GitHub

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[x] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

Currently content may be difficult to read on larger resolution screen sizes as there are no constraints to the width (documentation pages).

Expected behavior

Add width constraint to content to improve legibility.

Minimal reproduction of the problem with instructions

Sample page: https://angular.io/guide/forms

What is the motivation / use case for changing the behavior?

Discussion and exploration of concept upon team request -- to improve legibility on large resolution screens

The issue is that we have a sidenav 'slide drawer' which is a fixed item and will need to explore options.

Related issue - please set a max line length so that we keep to a scannable amount of text (~75 characters) per line and then just add white space around that if screen/window is wider: #24707

Examples

angular.io (from @ocombe):

next.angular.io:

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.

I believe this is resolved in the latest versions of the site:

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

aio: Consider implementation of max-wid centered content concept for documentation pages · Issue #22246 · angular/angular · GitHub

Repository navigation

aio: Consider implementation of max-wid centered content concept for documentation pages #22246

I'm submitting a...

Current behavior

Expected behavior

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

aio: Consider implementation of max-wid centered content concept for documentation pages · Issue #22246 · angular/angular · GitHub

Repository navigation

aio: Consider implementation of max-wid centered content concept for documentation pages #22246

Description

I'm submitting a...

Current behavior

Expected behavior

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Activity

sjtrimble commented on Feb 15, 2018

jenniferfell commented on Aug 29, 2018

Splaktar commented on Jan 17, 2020

angular-robot commented on Jun 4, 2021

angular-robot commented on Jun 25, 2021

petebacondarwin commented on Oct 9, 2021

angular-automatic-lock-bot commented on Nov 9, 2021

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions