Opened on 11/10/2016 at 04:20:27 PM
Closed on 06/19/2017 at 10:49:06 AM
Last modified on 07/22/2017 at 06:19:14 PM
#4629 closed change (fixed)
Create a default website boilerplate
Reported by: | juliandoucette | Assignee: | juliandoucette |
---|---|---|---|
Priority: | P2 | Milestone: | help.eyeo.com 1.0.0 |
Module: | Websites | Keywords: | |
Cc: | saroyanm, lisabielik | Blocked By: | #4805 |
Blocking: | Platform: | Unknown / Cross platform | |
Ready: | yes | Confidential: | no |
Tester: | Unknown | Verified working: | no |
Review URL(s): |
Description (last modified by juliandoucette)
Background
We would like to implement a default website boilerplate that developers can use as a starting point for new website implementations.
Requirements
- Straightforward usage instructions
- Standard meta data
- Realistic example content
Attachments (0)
Change History (17)
comment:1 Changed on 11/10/2016 at 04:27:19 PM by juliandoucette
- Blocked By 4607 added
comment:2 Changed on 11/10/2016 at 04:28:22 PM by juliandoucette
- Blocking 4606 added
comment:3 Changed on 11/24/2016 at 04:17:08 PM by saroyanm
- Blocked By 4630 added
- Priority changed from Unknown to P2
- Ready set
comment:4 Changed on 11/25/2016 at 01:16:54 PM by juliandoucette
- Cc lisabielik added
- Description modified (diff)
- Summary changed from UDL website boilerplate to Default website boilerplate
comment:5 Changed on 12/03/2016 at 05:18:45 PM by juliandoucette
- Blocked By 4630 removed
comment:6 Changed on 12/03/2016 at 06:11:25 PM by juliandoucette
- Owner set to juliandoucette
comment:8 Changed on 12/07/2016 at 01:41:17 PM by juliandoucette
- Review URL(s) modified (diff)
- Status changed from new to reviewing
comment:9 Changed on 01/16/2017 at 11:02:39 AM by saroyanm
- Blocking 4805 added
comment:10 Changed on 02/13/2017 at 09:13:35 PM by juliandoucette
- Blocked By 4805 added; 4607 removed
- Blocking 4606, 4805 removed
- Summary changed from Default website boilerplate to Create a default website boilerplate
- I'm going to organize website-defaults into several milestones instead of one deathless meta ticket
- I think this change is not blocked or blocking website-defaults since it will reside in it's own repository
- default-content and default-grid are no longer blocking this because they have been resolved
comment:11 Changed on 04/05/2017 at 11:17:11 AM by juliandoucette
- Priority changed from P2 to P3
comment:12 Changed on 04/05/2017 at 12:01:11 PM by juliandoucette
- Milestone set to help.eyeo.com 1.0.0
- Priority changed from P3 to P2
We can implement the code portion of this required for help center 1.0.0 (documentation not required for help.eyeo.com 1.0.0 milestone).
comment:13 Changed on 04/10/2017 at 07:42:38 PM by juliandoucette
- Blocking 1167 added
comment:14 Changed on 04/25/2017 at 12:59:31 PM by juliandoucette
- Blocking 146 added
comment:15 Changed on 06/19/2017 at 10:49:06 AM by juliandoucette
- Resolution set to fixed
- Status changed from reviewing to closed
I'm going to break this up into multiple issues.
Here is the initial commit: https://gitlab.com/eyeo/website-boilerplate/commit/e1802f8d37bc005a39bc194378d9c2732ffe7d04
comment:16 Changed on 07/10/2017 at 07:08:41 PM by juliandoucette
- Blocking 146 removed
comment:17 Changed on 07/22/2017 at 06:19:14 PM by juliandoucette
- Blocking 1167 removed
Note: See
TracTickets for help on using
tickets.