pages/deployments.html - Issue 6275268058546176: Issue 2157 - Update Large Scale Deployments landing page

Side by Side Diff: pages/deployments.html

Issue 6275268058546176: Issue 2157 - Update Large Scale Deployments landing page (Closed)

Patch Set: Created June 11, 2015, 1:54 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
1 title=Large Scale Deployments	1 title=Large Scale Deployment

	2 noheading=True

	3 notoc=True

2	4

	5 <head>

	6 <link type="text/css" href="/css/lsd.css" rel="stylesheet">

	7 <meta name="title" content="{{meta-title Large Scale Deployment}}" />

	8 <meta property="og:title" content="{{meta-title Large Scale Deployment}}" />

	9 <meta name="description" content="{{meta-description Adblock Plus is a great a sset to any company, university or large IT infrastructure. We are happy to help you deploy it across your entire network.}}" />

	10 <meta property="og:description" content="{{meta-description Adblock Plus is a great asset to any company, university or large IT infrastructure. We are happy to help you deploy it across your entire network.}}" />

	11 </head>

3	12

4 <p>{{s1 Adblock Plus is a great asset to every company, university or large IT i nfrastructure containing multiple working stations.}}</p>	13 <div id="lsd-header-block">

5 <p>{{s2 How does Adblock Plus benefit you?}}</p>	14 <h1>{{page-header Adblock Plus for Administrators}}</h1>

6 <ul>	15 <p>{{lsd-description Adblock Plus is a perfect tool for every university, comp any or any IT infrastructure with multiple working stations.}}</p>

7 <li>	16 </div>

8 {{s3 Considerably decreased privacy and security risks}}	17 <div id="lsd-icon-wrapper">

9 </li>	18 <span class="lsd-icon lsd"></span>

10 <li>	19 </div>

11 {{s4 A better browsing experience for your users – no distractions from annoyin g pop-ups, blinking banners and video ads}}	20 <div>

12 </li>	21 <div class="lsd-feature-wrapper">

13 <li>	22 <span class="lsd-icon bandwidth"></span>

14 {{s5 It's FREE}}	23 <span class="lsd-feature-text">{{lsd-bandwidth Save bandwidth}}</span>

15 </li>	24 </div>

16 </ul>	25 <div class="lsd-feature-wrapper">

17 <p>{{s6 We are happy to help you deploy it over your entire network! Please cont act us at: <a href="mailto:deployment-support@adblockplus.org" style="white-spac e: nowrap;"><fix>deployment-support@adblockplus.org</fix></a>}}</p>	26 <span class="lsd-icon efficient"></span>

18 <p>{{s7 Already deployed Adblock Plus? How was the experience? What can we do be tter? <a href="mailto:deployment-support@adblockplus.org">Let us know!</a>}}</p>	27 <span class="lsd-feature-text">{{lsd-efficient More efficient working enviro nment}}</span>

19 <p><a href="https://adblockplus.org/forum/viewforum.php?f=21">{{s8 More about th e project}}</a></p>	28 </div>

	29 <div class="lsd-feature-wrapper">

	30 <span class="lsd-icon privacy"></span>

	31 <span class="lsd-feature-text">{{lsd-privacy Enhanced privacy & security}}</ span>

	32 </div>

	33 <div class="lsd-feature-wrapper">

	34 <span class="lsd-icon gpl"></span>

	35 <span class="lsd-feature-text">{{lsd-gpl GPLv3 Licence}}</span>

	36 </div>

	37 </div>

	38

	39 <hr class="lsd-feature-separator" />

	40 <p>{{contact-us We would like to hear from you! <a href="mailto:deployment-suppo rt@adblockplus.org">Contact & technical support</a>}}</p>

	41 <div class="toc">
	saroyanm 2015/06/11 14:02:38 @Sebastian I just hard-coded this here to make it @Sebastian I just hard-coded this here to make it more descriptive on the example, I'm not sure whether I should create separate ticket for implementing toc that could be placed anywhere on the page, will appreciate your input here. What you think how it would be better to implement the TOC on this page so it could be placed after contact details ? Sebastian Noack 2015/06/11 14:34:00 So you did hard-code the toc to not have it at the Show quoted text On 2015/06/11 14:02:38, saroyanm wrote: > @Sebastian I just hard-coded this here to make it more descriptive on the > example, I'm not sure whether I should create separate ticket for implementing > toc that could be placed anywhere on the page, will appreciate your input here. > What you think how it would be better to implement the TOC on this page so it > could be placed after contact details ? So you did hard-code the toc to not have it at the top of the page as usual? Is it generally a good idea to introduce this inconsistency? Or do I miss the point? saroyanm 2015/06/11 14:44:29 Well actually this is something that probably need Show quoted text On 2015/06/11 14:34:00, Sebastian Noack wrote: > On 2015/06/11 14:02:38, saroyanm wrote: > > @Sebastian I just hard-coded this here to make it more descriptive on the > > example, I'm not sure whether I should create separate ticket for implementing > > toc that could be placed anywhere on the page, will appreciate your input > here. > > What you think how it would be better to implement the TOC on this page so it > > could be placed after contact details ? > > So you did hard-code the toc to not have it at the top of the page as usual? Is > it generally a good idea to introduce this inconsistency? Or do I miss the > point? Well actually this is something that probably needs to be changed as I mentioned I've hardcoded to show you the problem, as you can see in the mockup TOC is placed after contact details: https://issues.adblockplus.org/attachment/ticket/2157/LSD_Mockup_02.png So the current Mockup is inconsistent to what we currently have in CMS. I'm not sure whether make sense to update the mockup or implement Custom TOC that can be placed anyway in the page. I would actually vote for second one, because if we will update the mockup we should also need to consider the placement of LSD icon next to title. Sebastian Noack 2015/06/11 14:53:58 Yeah, that's what I mean. And yes, we should eithe Show quoted text On 2015/06/11 14:44:29, saroyanm wrote: > On 2015/06/11 14:34:00, Sebastian Noack wrote: > > On 2015/06/11 14:02:38, saroyanm wrote: > > > @Sebastian I just hard-coded this here to make it more descriptive on the > > > example, I'm not sure whether I should create separate ticket for > implementing > > > toc that could be placed anywhere on the page, will appreciate your input > > here. > > > What you think how it would be better to implement the TOC on this page so > it > > > could be placed after contact details ? > > > > So you did hard-code the toc to not have it at the top of the page as usual? > Is > > it generally a good idea to introduce this inconsistency? Or do I miss the > > point? > > Well actually this is something that probably needs to be changed as I mentioned > I've hardcoded to show you the problem, as you can see in the mockup TOC is > placed after contact details: > https://issues.adblockplus.org/attachment/ticket/2157/LSD_Mockup_02.png > > So the current Mockup is inconsistent to what we currently have in CMS. > I'm not sure whether make sense to update the mockup or implement Custom TOC > that can be placed anyway in the page. I would actually vote for second one, > because if we will update the mockup we should also need to consider the > placement of LSD icon next to title. Yeah, that's what I mean. And yes, we should either get rid of this inconsistency moving the TOC to the top of the page, or add a mechanism to generate the TOC here. I don't mind. So I looped in Sven and Thomas.
	42 <ul>

	43 <li><a href="#what-is-lsd">{{what-is-lsd-header What are large scale deploym ents?}}</a></li>
	Sebastian Noack 2015/06/11 14:34:00 Since this page is specific to large scale deploym Since this page is specific to large scale deployments I don't think you need to add "lsd" to all message ids here. saroyanm 2015/06/11 16:27:48 I get rid of some of them, but sometimes it's desc Show quoted text On 2015/06/11 14:34:00, Sebastian Noack wrote: > Since this page is specific to large scale deployments I don't think you need to > add "lsd" to all message ids here. I get rid of some of them, but sometimes it's descriptive I think for example in this case what-is-lsd make more sense. Sebastian Noack 2015/06/12 11:22:58 Well, you could simply change "what-is-lsd" in "ab Show quoted text On 2015/06/11 16:27:48, saroyanm wrote: > On 2015/06/11 14:34:00, Sebastian Noack wrote: > > Since this page is specific to large scale deployments I don't think you need > to > > add "lsd" to all message ids here. > > I get rid of some of them, but sometimes it's descriptive I think for example in > this case what-is-lsd make more sense. Well, you could simply change "what-is-lsd" in "about". And with most other like "lsd-header-block" and "lsd-icon-wrapper" I don't see why you didn't simply remove "lsd" there. saroyanm 2015/06/12 12:03:07 lsd-header-block and lsd-icon-wrapper are IDs, ple Show quoted text On 2015/06/12 11:22:58, Sebastian Noack wrote: > On 2015/06/11 16:27:48, saroyanm wrote: > > On 2015/06/11 14:34:00, Sebastian Noack wrote: > > > Since this page is specific to large scale deployments I don't think you > need > > to > > > add "lsd" to all message ids here. > > > > I get rid of some of them, but sometimes it's descriptive I think for example > in > > this case what-is-lsd make more sense. > > Well, you could simply change "what-is-lsd" in "about". And with most other like > "lsd-header-block" and "lsd-icon-wrapper" I don't see why you didn't simply > remove "lsd" there. lsd-header-block and lsd-icon-wrapper are IDs, please note that we are loading also other CSS styles here, so in future for example if we will have header-block ID in header then we could override that rule apart of having multiple IDs with same name, so that why I prefer some kind of prefix in the IDs and Class names for this page. Sure in case we will have several page with similar styles we should somehow change the styles to some generic name. Sebastian Noack 2015/06/12 12:07:35 You are right, my bad. I were only talking about m Show quoted text On 2015/06/12 12:03:07, saroyanm wrote: > On 2015/06/12 11:22:58, Sebastian Noack wrote: > > On 2015/06/11 16:27:48, saroyanm wrote: > > > On 2015/06/11 14:34:00, Sebastian Noack wrote: > > > > Since this page is specific to large scale deployments I don't think you > > need > > > to > > > > add "lsd" to all message ids here. > > > > > > I get rid of some of them, but sometimes it's descriptive I think for > example > > in > > > this case what-is-lsd make more sense. > > > > Well, you could simply change "what-is-lsd" in "about". And with most other > like > > "lsd-header-block" and "lsd-icon-wrapper" I don't see why you didn't simply > > remove "lsd" there. > > lsd-header-block and lsd-icon-wrapper are IDs, please note that we are loading > also other CSS styles here, so in future for example if we will have > header-block ID in header then we could override that rule apart of having > multiple IDs with same name, so that why I prefer some kind of prefix in the IDs > and Class names for this page. > Sure in case we will have several page with similar styles we should somehow > change the styles to some generic name. You are right, my bad. I were only talking about message IDs which aren't shared across pages, hence shouldn't mention lsd here. saroyanm 2015/06/12 13:46:04 Done. Show quoted text On 2015/06/12 12:07:35, Sebastian Noack wrote: > On 2015/06/12 12:03:07, saroyanm wrote: > > On 2015/06/12 11:22:58, Sebastian Noack wrote: > > > On 2015/06/11 16:27:48, saroyanm wrote: > > > > On 2015/06/11 14:34:00, Sebastian Noack wrote: > > > > > Since this page is specific to large scale deployments I don't think you > > > need > > > > to > > > > > add "lsd" to all message ids here. > > > > > > > > I get rid of some of them, but sometimes it's descriptive I think for > > example > > > in > > > > this case what-is-lsd make more sense. > > > > > > Well, you could simply change "what-is-lsd" in "about". And with most other > > like > > > "lsd-header-block" and "lsd-icon-wrapper" I don't see why you didn't simply > > > remove "lsd" there. > > > > lsd-header-block and lsd-icon-wrapper are IDs, please note that we are loading > > also other CSS styles here, so in future for example if we will have > > header-block ID in header then we could override that rule apart of having > > multiple IDs with same name, so that why I prefer some kind of prefix in the > IDs > > and Class names for this page. > > Sure in case we will have several page with similar styles we should somehow > > change the styles to some generic name. > > You are right, my bad. I were only talking about message IDs which aren't shared > across pages, hence shouldn't mention lsd here. Done.
	44 <li><a href="#why-lsd-header">{{why-lsd-header Why to deploy Adblock Plus in an administered environment?}}</a></li>

	45 <li><a href="#how-deploy-abp">{{how-deploy-abp-header How to deploy Adblock Plus?}}</a></li>

	46 <li><a href="#additional-resources">{{additional-resources-header Additional resources}}</a></li>

	47 <li><a href="#organisations-using-abp">{{organisations-using-abp Organizatio ns using Adblock Plus}}</a></li>

	48 </ul>

	49 </div>

	50 <h2 id="what-is-lsd">{{what-is-lsd-header What are large scale deployments?}}</h 2>

	51 <p>{{what-is-lsd-overview When installing the Adblock Plus extension for multipl e machines and user accounts, it is time-consuming and tedious to perform a manu al installation on each device. Administrators can utilize various tools to auto mate the installations, eg installer scripts or even configuration management so ftware.}}</p>

	52 <p>{{what-is-lsd-consideration Any mass installation of a browser extension has to take a number of things into account, like: desired browsers, operating syste ms, internal policies or infrastructure in general.}}</p>

	53 <h2 id="why-lsd-header">{{why-lsd-header Why to deploy Adblock Plus in an admini stered environment?}}</h2>

	54 <p>{{why-lsd-overview Adblock Plus is a great tool for every administered enviro nment (university, school, company, governmental institution etc) containing mul tiple working station in the IT infrastructure.}}</p>

	55 <p>{{why-lsd-advantages Adblock Plus considerably decreases security and privacy risks over the entire IT network. Malware and viruses are often spread via anno ying advertisement, which our extension blocks by default. Moreover, use of Adbl ock Plus considerably decreases the bandwidth usage. The overall browsing experi ence and working efficiency of the end users in networks using Adblock Plus is c onsiderably increased. The users are not annoyed by pop-ups, blinking banners an d misleading advertising, which helps them to focus better.}}</p>

	56 <h2 id="how-deploy-abp">{{how-deploy-abp-header How to deploy Adblock Plus?}}</h 2>

	57 <p>{{how-deploy-abp-overview We are currently working on the best solutions for large scale deployments. These are, however, mostly dependent on the browser use d.}}</p>

	58 <p>{{how-deploy-abp-contact Contact & technical support: <a href="mailto:deploym ent-support@adblockplus.org">deployment-support@adblockplus.org</a>}}</p>

	59 <h2 id="additional-resources">{{additional-resources-header Additional resources }}</h2>

	60 <p>{{lsd-forum-info You can ask questions or contribute to the discussion about deployment-related topics in our <a href="https://adblockplus.org/forum/viewforu m.php?f=21">forum</a>.}}</p>

	61 <p>{{lsd-issues-info If you want to create a ticket related to the Large Scale D eployments project, please check the <a href="https://issues.adblockplus.org/wik i/large-scale-deployments">current list of the issues</a> first. Please tag your issue with the following keyword: <strong>large-scale-deployments</strong>. If you find a bug you can directly file a ticket on the <a href="https://issues.adb lockplus.org/">Adblock Plus issue tracker</a>.}}</p>

	62 <h2 id="organisations-using-abp">{{organisations-using-abp Organizations using A dblock Plus}}</h2>

	63 <div class="lsd-organisation-wrapper">

	64 <img alt="Unalaska City School District" src="/img/lsd/unalaska-logo.png">

	65 <div>

	66 <p>

	67 {{unalaska-school-quote "With extremely limited bandwidth here in remote A laska, I find that every bit that travels over the satellite counts."}}

	68 </p>

	69 <p>

	70 <i>- {{unalaska-school-author Brent Bain, <a href="http://ucsd.net/">Unala ska City School District</a>}}</i>

	71 </p>

	72 </div>

	73 </div>

	74 <div class="lsd-organisation-wrapper">

	75 <img alt="Compnology" src="/img/lsd/compnology-logo.png" />

	76 <div>

	77 <p>

	78 {{compnology-quote "Due to Malvertising and the crypto-locker and like mal ware we are interested in utilizing your software."}}

	79 </p>

	80 <p>

	81 <i>- {{compnology-author Charles Hix, <a href="http://www.compnology.com/" >Compnology</a>}}</i>

	82 </p>

	83 </div>

	84 </div>

	85 <div class="lsd-organisation-wrapper">

	86 <img alt="International School of Geneva" src="/img/lsd/is-geneva-logo.png" />

	87 <div>

	88 <p>

	89 {{geneva-int-school-quote “Adblock Plus allows our students and teachers t o remain focused on their learning and teaching."}}

	90 </p>

	91 <p>

	92 <i>- {{geneva-int-school-author Josue Mouco, <a href="http://ecolint.ch/"> International School of Geneva</a>}}</i>

	93 </p>

	94 </div>

	95 </div>

	96 <div class="lsd-organisation-wrapper">

	97 <img alt="Seven Energy International Limited" src="/img/lsd/7energy-logo.png" />

	98 <div>

	99 <p>

	100 {{7energy-quote "I would definitely recommend Adblock Plus for businesses not only was it really easy to push out to all of my end point users agree it is so nice to have it installed."}}

	101 </p>

	102 <p>

	103 <i>- {{7energy-author Daniel Sanders, <a href="http://www.sevenenergy.com/ ">Seven Energy International Limited</a>}}</i>

	104 </p>

	105 </div>

	106 </div>

	107 <div class="lsd-organisation-wrapper">

	108 <img alt="Holstebro Kommune" src="/img/lsd/holstebro-logo.png" />

	109 <div>

	110 <p>

	111 {{holstebro-quote "After the deployment of Adblock Plus we had a great dec rease in server load, which lead to better performance for our users."}}

	112 </p>

	113 <p>

	114 <i>- {{holstebro-author Anders Erfurt Høj Thomsen, <a href="http://www.ho lstebro.dk/">Holstebro Kommune</a>}}</i>

	115 </p>

	116 </div>

	117 </div>

OLD	NEW

« no previous file with comments | « locales/zh_CN/deployments.json ('k') | static/css/lsd.css » ('j') | no next file with comments »