Skip to content
This repository has been archived by the owner on Jan 15, 2020. It is now read-only.

[EPIC] Unified web experience Phase 2 #64

Closed
5 tasks
dhmlau opened this issue Mar 19, 2019 · 3 comments
Closed
5 tasks

[EPIC] Unified web experience Phase 2 #64

dhmlau opened this issue Mar 19, 2019 · 3 comments
Labels
2019Q3 Target for 2019 Q3 Epic

Comments

@dhmlau
Copy link
Member

dhmlau commented Mar 19, 2019

Description / Steps to reproduce / Feature proposal

To complete the work for unified web experience, the goal is to have loopback.io shows the content of v4.loopback.io

Things to consider/discuss

In the current loopback.io, there are getting-started, examples, resources pages that are specific to the older version of LoopBack. Are we going to remove them or keep them, something like:

loopback.io/getting-started -> loopback.io/lb3/getting-started
loopback.io/resources -> loopback.io/lb3/resources

What needs to be done

  • make the existing docs work in the new framework/structure
  • decide on what to do with the existing loopback.io content (see above)
  • switch v4.loopback.io github pages to be served on loopback.io (is it an easy switch?)

@strongloop/loopback-maintainers, thoughts?

@dhmlau dhmlau added Epic 2019Q2 Target for 2019 Q2 labels Mar 19, 2019
@bajtos
Copy link
Member

bajtos commented Mar 19, 2019

IMO, it's better to preserve the LB3 version of both pages getting-started and resources.

@dhmlau
Copy link
Member Author

dhmlau commented Mar 19, 2019

IMO, it's better to preserve the LB3 version of both pages getting-started and resources.

@raymondfeng has expressed the same viewpoint.

@dhmlau
Copy link
Member Author

dhmlau commented Jun 4, 2019

Closing as done.

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

No branches or pull requests

2 participants