Bugzilla – Full Text Bug Listing
| Summary: | provide a how-to doc that explains branding of Orion | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Rafael Chaves <eclipse> |
| Component: | Doc | Assignee: | Project Inbox <orion.doc-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | punya.biswal, snorthov |
| Version: | unspecified | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Rafael Chaves
*** Bug 468009 has been marked as a duplicate of this bug. *** Whereas this bug talks specifically about a document, it is possible some things need to changed in Orion itself to enable adopters to accomplish branding in a scalable/repeatable way. Please see bug 468009 comment 0 for examples of what adopter may need to accomplish w.r.t. branding. Please see dup (bug 468009) for more info, and to see that rebranding doc would be useful. Also, whatever solution is used for bug 403261 (after it is fixed) belongs in the rebranding doc too. As suggested by Carolyn, I created a wiki page to start collecting tips on branding: https://wiki.eclipse.org/Orion/How_Tos/How_to_brand_Orion The linked wiki page lists out branding needs but doesn't contain any solutions. In particular, the most recent master version (gba75330) hardcodes: * the landing page location (which includes a Twitter feed) * the list of OAuth providers (Google and Github) > The linked wiki page lists out branding needs but doesn't contain any solutions
Yes, there are many gaps here. Contributions to Orion to help make all of these points more flexible would be most welcome. I suggest opening individual bugs for specific issues, and if you are able to work on a fix that would be great. Sometimes a quick and dirty solution with a server configuration setting can be done to help here without too much effort.
A wiki was created. We are unlikely to do any branding work in the near future. |