Skip to content
This repository was archived by the owner on Dec 9, 2021. It is now read-only.

Commit c688bfb

Browse files
committed
move relaunch plan
Signed-off-by: Matt Oswalt <[email protected]>
1 parent bf0918f commit c688bfb

File tree

1 file changed

+1
-55
lines changed

1 file changed

+1
-55
lines changed

nrelabs-relaunch-plan.md

Lines changed: 1 addition & 55 deletions
Original file line numberDiff line numberDiff line change
@@ -1,57 +1,3 @@
11
# NRE Labs Technical Re-Launch Plan
22

3-
We're re-launching the NRE Labs site in early 2020, and as a result, there are a bunch of technical things
4-
that we need to do to pull this off. There will be other activities that will need to take place for the re-launch
5-
such as marketing and community-related objectives. This document will focus exclusively on the technical execution
6-
plan for the relaunch.
7-
8-
Here's a summary of what we're launching:
9-
10-
- Redesigned web site that fully integrates existing blog, pages, and NRE Labs application
11-
- Redesigned `antidote-web` including widgetization, mobile support, performance improvements, and UX
12-
- New, simpler domain - https://nrelabs.io.
13-
- New, simpler, easier to follow documentation focused entirely on the NRE Labs curriculum - https://docs.nrelabs.io
14-
15-
## Execution Plan
16-
17-
A key component to this execution plan is that we'll be building everything on a new domain, `nrelabs.io`.
18-
This will give us a chance to build everything in a safe place before we decide to go live, and will allow us to
19-
avoid all kinds of messiness in trying to ensure the old site isn't disrupted during the final stages of
20-
development. For the most part, the old site will be left alone, until we're ready to go with the new site,
21-
at which point we'll add redirects from the old domain to the new one.
22-
23-
### Phase 1 - Preparation
24-
25-
- [x] Deploy new docs PoC at https://docs.nrelabs.io
26-
- [x] Stand up new site at https://nrelabs.io
27-
- [ ] Kick off 0.5.0 platform release cycle
28-
- [ ] Kick off 1.0.1 curriculum release cycle (Fix existing issues, Check compatibility w/0.5.0, any new lessons)
29-
- [ ] Finish new docs
30-
- [ ] Move existing deployment to new `prod-old` namespace
31-
- [ ] Get webssh2 changes merged upstream or into an nre-learning fork
32-
- [ ] Add webssh2 image to platform deployment once selfmedicate is configured properly with an ingress
33-
- [ ] Finish webssh2 deployment in selfmedicate https://github.com/nre-learning/antidote-selfmedicate/pull/69
34-
- [ ] Implement cloudflare maintenance page https://github.com/nre-learning/antidote-ops/issues/16
35-
- [ ] Merge remaining Bitovi work to `antidote-web` and `nre-blog`
36-
- [ ] Deploy latest platform code to nrelabs.io and test. Work out any issues.
37-
- [ ] **Finish development** for Antidote 0.5.0 and NRE Labs 1.0.1 **before continuing**
38-
- [ ] Create 0.5.0 release of Antidote
39-
- [ ] Create Curriculum 1.0.1 release (in parallel w/0.5.0)
40-
- [ ] Deploy releases to `prod` and kick off formal testing on new domain.
41-
- [ ] Hold a formal "go/no-go" one week prior to launch
42-
43-
### Phase 2 - Go-Live
44-
45-
- [ ] Add redirects via cloudflare (all are 302 for the time being)
46-
- `labs.networkreliability.engineering` -> `nrelabs.io`
47-
- `networkreliability.engineering` -> `nrelabs.io`
48-
- `community.networkreliability.engineering` -> `discuss.nrelabs.io`
49-
- [ ] Testing
50-
51-
### Phase 3 - Clean-Up
52-
53-
- [ ] Convert new nrelabs.io cloudflare stuff to terraform
54-
- [ ] Move old domain underneath new cloudflare account as well
55-
- [ ] Update any links on Juniper or NRE Labs properties that use the old domain
56-
- [ ] Downgrade netlify plan if possible
57-
- [ ] Fix nightly builds and PTR
3+
This has been [moved](https://github.com/nre-learning/antidote-ops/issues/23)

0 commit comments

Comments
 (0)