Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation: split up Add To Your Site into standalones #7051

Closed
4 tasks done
privatemaker opened this issue Jan 19, 2024 · 2 comments
Closed
4 tasks done

Documentation: split up Add To Your Site into standalones #7051

privatemaker opened this issue Jan 19, 2024 · 2 comments
Labels
type: feature code contributing to the implementation of a feature and/or user facing functionality

Comments

@privatemaker
Copy link
Contributor

privatemaker commented Jan 19, 2024

There are some pages in the documentation that are rather long in the current information architecture and file management, the most important one is:

The current #anchor style long page has some negative user-experience aspects:

  1. When loading the page via external link or manually loading these pages in browsers address bar the user lands on the page and the scrolling action starts.

decap-docs-page-title-linking

  1. When clicking on the leftbar TOC the page scrolls and properly shows the title. However, the scrolling is rather time intensive and distracting compared to a normal page load, as well as losing the entire leftbar navigation above the top of screen which is disorienting.

decap-docs-page-title-clicking

  1. These sections are semantically different (and important enough) I think that warrants it's own pages.

I propose migrating each of the Add To Your Site sections to their own pages

@privatemaker privatemaker added the type: feature code contributing to the implementation of a feature and/or user facing functionality label Jan 19, 2024
@martinjagodic
Copy link
Member

@privatemaker this is a really good point. Also, the authentication section needs an update to include other options besides Netlify. I would do the rewrite as another PR. Would you take over the file reorg?

@privatemaker
Copy link
Contributor Author

@martinjagodic yah i'm up for doing this. I will start a new PR once the Beta Features are done being merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature code contributing to the implementation of a feature and/or user facing functionality
Projects
None yet
Development

No branches or pull requests

2 participants