globals/products.py - Issue 29516622: Issue 5511 - Create Product Help Home Template for help.eyeo.com

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments.

Keyboard Shortcuts

	File
u :	up to issue
m :	publish + mail comments
M :	edit review message
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line
<Enter> :	respond to / edit current comment
d :	mark current comment as done

	Issue
u :	up to list of issues
m :	publish + mail comments
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue
# :	close issue

	Comment/message editing
<Ctrl> + s or <Ctrl> + Enter :	save comment
<Esc> :	cancel edit

Side by Side Diff: globals/products.py

Issue 29516622: Issue 5511 - Create Product Help Home Template for help.eyeo.com (Closed) Base URL: https://hg.adblockplus.org/help.eyeo.com

Patch Set: Rebase Created Sept. 11, 2017, 2:46 p.m.

Left:
Right:

Use n/p to move between diff chunks; N/P to move between comments.

Jump to:

View unified diff | Download patch

OLD	NEW
(Empty)
	1 # This file is part of help.eyeo.com.

	2 # Copyright [C] 2016 Eyeo GmbH

	3 #

	4 # help.eyeo.com is free software: you can redistribute it and/or modify

	5 # it under the terms of the GNU General Public License as published by

	6 # the Free Software Foundation, either version 3 of the License, or

	7 # [at your option] any later version.

	8 #

	9 # help.eyeo.com is distributed in the hope that it will be useful,

	10 # but WITHOUT ANY WARRANTY; without even the implied warranty of

	11 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the

	12 # GNU General Public License for more details.

	13 #

	14 # You should have received a copy of the GNU General Public License

	15 # along with help.eyeo.com. If not, see <http://www.gnu.org/licenses/>.

	16

	17 products = {

	18 "abp": {

	19 "full_name": "Adblock Plus",

	20 "url": "https://adblockplus.org",

	21 "help_categories": [
	juliandoucette 2017/09/12 13:21:56 Note: These could be auto-generate via category pr Note: These could be auto-generate via category property in pages provided that the name/slug/icon format do not differ in contents/format. Unfortunately this couldn't be done in a global because globals don't have access to other globals. Therefore, your implementation, although (arguably) not optimal, is the best we can currently do; I think. ire 2017/09/19 10:27:18 Yes I thought about standardizing the names of the Show quoted text On 2017/09/12 13:21:56, juliandoucette wrote: > Note: These could be auto-generate via category property in pages provided that > the name/slug/icon format do not differ in contents/format. Unfortunately this > couldn't be done in a global because globals don't have access to other globals. > Therefore, your implementation, although (arguably) not optimal, is the best we > can currently do; I think. Yes I thought about standardizing the names of the icons as well, then got a bit stuck when it came to the ones that have "&", which would require us to probably write a custom function to "slugify" the name. I think this is something we can still look into, but perhaps in a separate issue. juliandoucette 2017/09/22 13:29:35 Acknowledged. Show quoted text On 2017/09/19 10:27:18, ire wrote: > On 2017/09/12 13:21:56, juliandoucette wrote: > > Note: These could be auto-generate via category property in pages provided > that > > the name/slug/icon format do not differ in contents/format. Unfortunately this > > couldn't be done in a global because globals don't have access to other > globals. > > Therefore, your implementation, although (arguably) not optimal, is the best > we > > can currently do; I think. > > Yes I thought about standardizing the names of the icons as well, then got a bit > stuck when it came to the ones that have "&", which would require us to probably > write a custom function to "slugify" the name. I think this is something we can > still look into, but perhaps in a separate issue. Acknowledged.
	22 {

	23 "name": "Popular Topics",

	24 "slug": "popular-topics",

	25 "icon": "popular-icon"

	26 },

	27 {

	28 "name": "Customization & Settings",

	29 "slug": "customization-and-settings",

	30 "icon": "settings-icon"

	31 },

	32 {

	33 "name": "Troubleshooting & Reporting",

	34 "slug": "troubleshooting-and-reporting",

	35 "icon": "reporting-icon"

	36 },

	37 {

	38 "name": "Installation",

	39 "slug": "installation",

	40 "icon": "install-icon"

	41 },

	42 {

	43 "name": "Adblock Plus for Mobile",

	44 "slug": "abp-for-mobile",

	45 "icon": "mobile-icon"

	46 }

	47 ]

	48 }

	49 }

OLD	NEW

« globals/get_page_slug.py ('K') | « globals/get_page_slug.py ('k') | pages/adblockplus/adblock-plus-breaks-the-websites-i-visit.md » ('j') | static/scss/base/_utilities.scss » ('J')