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

[Proposal] Change main pages of loopback.io to use v4 pages #839

Closed
dhmlau opened this issue May 24, 2019 · 3 comments
Closed

[Proposal] Change main pages of loopback.io to use v4 pages #839

dhmlau opened this issue May 24, 2019 · 3 comments

Comments

@dhmlau
Copy link
Member

dhmlau commented May 24, 2019

Background

Currently we have 2 LoopBack web sites: loopback.io and v4.loopback.io. Our initial plan was to make the v4.loopback.io repo ready so that when we are ready (docs pages and everything are set up properly), we can make v4.loopback.io repo to serve at loopback.io.

Since we are planning to keep most of the documentation infrastructure, it might be a good idea to make changes to the existing loopback.io main pages to have the LB4 content i.e.

  • landing pages
  • getting started
  • resources
  • etc.

Proposed changes

I'd like to propose that we:

  • copy the pages from v4.loopback.io to loopback.io
  • for the LB3 pages we still want to keep, it will be moved to loopback.io/lb3/
@nabdelgadir
Copy link
Contributor

I like this proposal more than the other way around (suggested in strongloop/v4.loopback.io#65), but if for any reason this way doesn't work we still have the other proposal.

If we do this switch, then should we add redirections for current lb3 pages like loopback.io/examples -> https://loopback.io/doc/en/lb4/Examples.html to not break existing urls? I don't think this is a big deal but just something to consider.

@dhmlau
Copy link
Member Author

dhmlau commented May 25, 2019

If we do this switch, then should we add redirections for current lb3 pages like loopback.io/examples -> https://loopback.io/doc/en/lb4/Examples.html to not break existing urls? I don't think this is a big deal but just something to consider.

that's good point. Thanks for bringing this up.

@dhmlau
Copy link
Member Author

dhmlau commented Jun 4, 2019

Closing it as done. via PR #840

@dhmlau dhmlau closed this as completed Jun 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants