"
160 | $NewRegionParameters.Order+= "$Count of $Total"
161 |
162 | }
163 | $Count++
164 | }
165 |
166 | if (-not $stepByStep) {
167 | "$walkThruHTML"
168 | } else {
169 | if ($WalkthruName) {
170 | New-Region @newRegionParameters -AsFeaturette -ShowLayerTitle -LayerId "Walkthru_$WalkthruName"
171 | } else {
172 | New-Region @newRegionParameters -AsFeaturette -ShowLayerTitle -LayerUrl "RandomWalkthru_$(Get-random)"
173 | }
174 |
175 | }
176 |
177 |
178 |
179 | }
180 |
181 | }
182 | }
183 |
--------------------------------------------------------------------------------
/bin/Microsoft.Exchange.WebServices.dll:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/bin/Microsoft.Exchange.WebServices.dll
--------------------------------------------------------------------------------
/css/Pipeworks.less:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/css/Pipeworks.less
--------------------------------------------------------------------------------
/en-us/A_Simple_Stockticker.walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/A_Simple_Stockticker.walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_AdSense.help.txt:
--------------------------------------------------------------------------------
1 | The AdSense section of the Pipeworks manifest describes how AdSense ads will be added to a Pipeworks site.
2 |
3 | It is a hashtable, and contains:
4 |
5 | * An ID (your AdSense ID)
6 | * (Optionally) a BottomAdSlot, containing the ad slot you will display on the bottom of each page
7 | * (Optionally) a TopAdSlot, containing the ad slot you will display on the top of each page
8 |
9 |
10 | This is an example of a manifest containing only AdSense information:
11 |
12 | @{
13 | AdSense = @{
14 | Id = '7086915862223923'
15 | BottomAdSlot = '6352908833'
16 | }
17 | }
18 |
19 |
20 | See Also:
21 |
22 | * [/About_the_Pipeworks_Manifest_-_PubCenter](About The Pipeworks Manifest - PubCenter)
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_Ajax.help.txt:
--------------------------------------------------------------------------------
1 | The Ajax section of the Pipeworks manifest is boolean. By default, it's set to false. It instructs Pipeworks to use Ajax in forms.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_AllowDownload.help.txt:
--------------------------------------------------------------------------------
1 | AllowDownload is a Pipeworks Manifest setting that will make the published module downloadable.
2 |
3 |
4 | If set, a zip file will be created containing the module and all of it's requirements. This zip file will also include an install.cmd, and, optionally, a shortcut installer. The published module will contain a link "Download" that will download the .zip file.
5 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_AmazonPaymentsAccountId.help.txt:
--------------------------------------------------------------------------------
1 | The Amazon Payments Account ID. At this point, due to breaking changes in Amazon web stores, Amazon payment is not supported in Pipeworks.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_AnalyticsID.help.txt:
--------------------------------------------------------------------------------
1 | The Pipeworks setting AnalyticsID is a Google Analytics ID tracker. If provided, this will be placed on every page in the module.
2 |
3 |
4 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_Antisocial.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/About_the_Pipeworks_Manifest_-_Antisocial.help.txt
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_AppPoolPasswordSetting.help.txt:
--------------------------------------------------------------------------------
1 | The AppPoolPassWordSetting defines a SecureSetting that contains the password for the AppPool user.
2 |
3 |
4 | If this and AppPoolUser are provided, the module will be published under a specific app pool user account. This can be very useful for Intranet modules that need to run as a particular user.
5 |
6 | See Also:
7 |
8 |
9 | * [AppPoolUser](/About_the_Pipeworks_Manifest_-_AppPoolUser/)
10 | * [Scripting Securely with SecureSettings](/Scripting_Securely_with_SecureSettings/)
11 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_AppPoolUser.help.txt:
--------------------------------------------------------------------------------
1 | The AppPoolUser defines a SecureSetting that contains the password for the AppPool user.
2 |
3 |
4 | If this and AppPoolPasswordSetting are provided, the module will be published under a specific app pool user account. This can be very useful for Intranet modules that need to run as a particular user.
5 |
6 | See Also:
7 |
8 |
9 | * [AppPoolPasswordSetting](/About_the_Pipeworks_Manifest_-_AppPoolPasswordSetting/)
10 |
11 |
12 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_AsIntranetSite.help.txt:
--------------------------------------------------------------------------------
1 | If AsIntranetSite is set, the site will be published as an Intranet site. Anonymous Authentication will be turned off, and Windows Authentication will be turned on.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_BingValidationKey.help.txt:
--------------------------------------------------------------------------------
1 | The BingValidationKey will add a Bing Webmaster Tools validation key to each page. This will enable you to use the site with [Bing Webmaster Tools](http://www.bing.com/toolbox/webmaster)
2 |
3 |
4 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_Blog.help.txt:
--------------------------------------------------------------------------------
1 | The Blog Pipeworks Manifest setting is a hashtable that describes RSS feed information about the site.
2 |
3 |
4 | If provided, the home page will have a link to the blog's RSS feed, and the page will contain the appropriate metadata for search engines.
5 |
6 | If only a name and a description are provided, a feed will be automatically provided by the module's topics.
7 |
8 | Additionally, the Blog section can be used with the Blog Schematic
9 |
10 | Here is an example of a completed blog section that uses the built-in RSS feed:
11 |
12 |
13 | Blog = @{
14 | Name = "Start-Scripting"
15 | Description = "Stop-WastingTime. Start-Scripting -with PowerShell"
16 | }
17 |
18 | Here is an example that uses it's own feed:
19 |
20 |
21 | Blog = @{
22 | Name = "Start-Scripting"
23 | Description = "Stop-WastingTime. Start-Scripting -with PowerShell"
24 | Link = "http://blog.start-automating.com/"
25 | }
26 |
27 |
28 |
29 |
30 |
31 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_Bootstrap.help.txt:
--------------------------------------------------------------------------------
1 | BootStrap (or UseBootStrap) instructs Pipeworks to use Twitter Bootstrap to build a site.
2 |
3 |
4 | If the theme is not present, this will download a twitter bootstrap theme according using color scheme specified in the Style section of the Pipeworks manifest. To refresh the them, delete bootstrap.js from the JS directory of the module and republish.
5 |
6 |
7 | Using Bootstrap enables many features within Pipeworks, and changes the default layout. It enables a navbar that links to the topics and commands in the module. It also changes the deault view to a set of HangingSpans, which will expand out when clicked.
8 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_Branding.help.txt:
--------------------------------------------------------------------------------
1 | The branding section of the Pipeworks manifest describes the branding displayed on each page.
2 |
3 | By default, this will display a link to Start-Automating and to PowerShell Pipeworks.
4 |
5 | It can be blank, or can contain any HTML or Markdown you'd like.
6 |
7 |
8 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_CommandOrder.help.txt:
--------------------------------------------------------------------------------
1 | The CommandOrder is a list of strings, and it determines the order commands will be displayed (if there commands are not grouped). By default, commands will be alphabetized.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_CommandTemplate.help.txt:
--------------------------------------------------------------------------------
1 | The CommandTemplate is the PowerShell web template (.pswt) used to display each command in the site. A .pswt allows you to customize the look and feel of a pipeworks page. It directly replaces variable names within the page. By default, this is set to Command.pswt.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_CommandTrigger.help.txt:
--------------------------------------------------------------------------------
1 | The CommandTrigger section of the PipeworksManifest describes when commands will be triggered on a device. At current, only one setting is supported: Shake.
2 |
3 |
4 | Here is an example of a Pipeworks manifest with a CommandTrigger section:
5 |
6 | @{
7 | CommandTrigger = @{
8 | "Shake" = "Get-RandomPowerShellTip"
9 | }
10 | }
11 |
12 |
13 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_Css.help.txt:
--------------------------------------------------------------------------------
1 | The CSS section of the pipeworks manifest describes CSS style pages to use with each page.
2 |
3 |
4 | It is a hashtable, with the key describing the style page and the value containing the path to the page.
5 |
6 |
7 | Here's a quick example of the CSS section:
8 |
9 | @{
10 | Css = @{
11 | "PowerShellStyleSheet" = "/CSS/Gangamstyle.css"
12 | }
13 | }
14 |
15 |
16 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_DefaultCommand.help.txt:
--------------------------------------------------------------------------------
1 | The DefaultCommand section of the Pipeworks manifest describes the command that will run by default when a user visits the page.
2 |
3 |
4 | It is a hashtable, and must contain the name of the command. It may contain a nested hashtable called Parameter, which will provide parameters to the command.
5 |
6 |
7 | DefaultCommands do not need to be registered as web commands, since they cannot accept open-ended input.
8 |
9 |
10 | Here is an example:
11 |
12 |
13 | @{
14 | DefaultCommand = @{
15 | Name = 'Get-RandomPowerShellTip'
16 | }
17 | }
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_DefaultTemplate.help.txt:
--------------------------------------------------------------------------------
1 | The Default Template describes the PowerShell Web Template (.pswt) used to display the main page. A .pswt allows you to customize the look and feel of a pipeworks page. It directly replaces variable names within the page. By default, this is set to Default.pswt.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_DomainSchematics.help.txt:
--------------------------------------------------------------------------------
1 | The DomainSchematics section describes how the Pipeworks module will be published. It is a hashtable, containing a series of domains and a list of schematics to use while publishing.
2 |
3 |
4 | A site can be published to multiple domains. To do this, separate each item with a |
5 |
6 |
7 | Here's an example of a site that would be published to 4 different URLs, using the default schematic:
8 |
9 | @{
10 | DomainSchematics = @{
11 | "StartLearningPowerShell.com | Start-LearningPowershell.com | www.Start-LearningPowershell.com | www.StartLearningPowerShell.com" =
12 | "Default"
13 | }
14 | }
15 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_Download.help.txt:
--------------------------------------------------------------------------------
1 | Download is a Hashtable of files that will be downloaded when the module is published. The key of the hashtable is the URL, and the value is the local path of the downloaded file, relative to the output directory.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_ExecutionTimeout.help.txt:
--------------------------------------------------------------------------------
1 | The ExecutionTimeout allows you to customize the ASP.Net execution timeout for each page.
2 |
3 | The value must be a string that can be a timespan (for instance: '00:02:00').
4 |
5 | By default, the timeout is 2 minutes.
6 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_Facebook.help.txt:
--------------------------------------------------------------------------------
1 | The facebook section adds facebook like links, and allows using Facebook as an authentication method. It is a hashtable, and contains the AppId:
2 |
3 |
4 | Here is an example:
5 |
6 | @{
7 | Facebook = @{
8 | AppId = '452858484777409'
9 | }
10 | }
11 |
12 |
13 |
14 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_GitIt.help.txt:
--------------------------------------------------------------------------------
1 | GitIt describes projects to pull from Git prior to deployment.
2 |
3 |
4 | See Also:
5 |
6 | * [Getting GitIt](/Getting_GitIt/)
7 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_GoogleMerchantId.help.txt:
--------------------------------------------------------------------------------
1 | If provided the GoogleMerchantID can add Google Checkout integration for items on a page. Any products rendered within the page will include Google Checkout links.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_GoogleSiteVerification.help.txt:
--------------------------------------------------------------------------------
1 | The GoogleSiteVerification setting of the Pipeworks Manifest allows adds site verification tags for Google WebMaster Tools. It also adds a +1 button to each page, until AntiSocial is specified.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_Group.help.txt:
--------------------------------------------------------------------------------
1 | The Group describes how commands and topics will be displayed on the front page and in menus throughout the site.
2 |
3 |
4 | It is a list of hashtables, displayed in order. The key of each item in the hashtable will the name of the group. The value will be a list of commands or topics within the group.
5 |
6 |
7 | For example, here's the Group section for Pipeworks:
8 |
9 |
10 | @{
11 | Group = @{
12 | "Getting Started" = "About PowerShell Pipeworks", "Pipeworks Quickstart", "The Pipeworks Manifest", 'From Script To Software Service', "Powerful Powershell Formatting", "Scripting Securely with SecureSettings", "NOHtml Sites", "A Simple StockTicker", "Creating a CitiBike Station Finder"
13 | }, @{
14 | "Play with Pipeworks" = "Write-ASPDotNetScriptPage", "ConvertFrom-Markdown", "Making Editing Easier With Markdown", "Write-Crud", "Write-ScriptHTML", "Making Tables with Out-HTML", "Working with Write-Link"
15 | }, @{
16 | "Connecting the Clouds" = "Building with Bootstrap", "Get-Paid with Stripe", "Getting GitIt", "Get-Web Content From Anywhere", "Pick up the Phone with Pipeworks", "Implicit Texting with Twilio", "The Wonders of Wolfram Alpha","JQueryUI in Pipeworks", 'New-WebPage And JQuery', 'New-Region And JQueryUI', "Pipeworks Writes CRUD", "Managing Amazon Web Services with PowerShell Pipeworks", "Using Azure Table Storage in Pipeworks", "Publishing Pipeworks to Azure", 'Looking Up Locations With Resolve-Location', 'Simplifying Slideshows'
17 | }, @{
18 | "Join Windows and Web" = "Why Windows", "Scripting with Superglue", "Integrated Intranet", "Simpler SEO"
19 | }
20 | }
21 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_HiddenTopic.help.txt:
--------------------------------------------------------------------------------
1 | HiddenTopic (or HiddenTopics) is a list of topics that will be hidden from normal view. You can still visit the topic page directly to visit the topic, but it will not show up in menus.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_HideUngrouped.help.txt:
--------------------------------------------------------------------------------
1 | If HideUngroupedHelp is set, topics that are not in a Group will not be displayed in menus.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_IgnoreBuiltInCommand.help.txt:
--------------------------------------------------------------------------------
1 | If set, then built in commands cannot be used within a Pipeworks module (only commands from the current module can be). If not set, any command can be accessed via URL. If the command is not set in WebCommand, the help handler will be used. This is why [http://powershellpipeworks.com/Get-ChildItem/](http://powershellpipeworks.com/Get-ChildItem/) works, and isn't a threat.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_InnerRegion.help.txt:
--------------------------------------------------------------------------------
1 | The InnerRegion is a Pipeworks Manifest setting that describes how the inner regions within a group will be rendered. It is as Hashtable, and the input in the Hashtable will be provided to the New-Region command.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_JQueryUITheme.help.txt:
--------------------------------------------------------------------------------
1 | The JQueryUITheme describes the them used for JQueryUI. This can be any theme on the default CDNs, or 'Custom', which will use a theme located in the 'custom' directory. You can build the theme using [JQueryUI's ThemeRoller](http://jqueryUI.com/themeroller/).
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_JavaScript.help.txt:
--------------------------------------------------------------------------------
1 | The Javascript section of the Pipeworks manifest lists javascript files to include on all pages.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_Keyword.help.txt:
--------------------------------------------------------------------------------
1 | The keyword setting of the Pipeworks manifest contains a list of search keywords to add to each page of the site.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_LiveConnect.help.txt:
--------------------------------------------------------------------------------
1 | The LiveConnect section of the Pipeworks manifest describes Live Connect application data.
2 |
3 |
4 | It contains the ClientID of the app, as well as a secure setting pointing to the Client Secret Key.
5 |
6 |
7 | Here is an example:
8 |
9 |
10 | @{
11 | LiveConnect = @{
12 | ClientId = '00000000440DBD88'
13 | ClientSecretSetting = 'StartLearningPowerShellLiveSecret'
14 | }
15 | }
16 |
17 |
18 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_Logo.help.txt:
--------------------------------------------------------------------------------
1 | The logo of the pipeworks manifest is a URL to a logo file to use on all pages. The url should be root-relative (i.e. /Assets/Logo.png)
2 |
3 | Here is an example:
4 |
5 | @{
6 | Logo = "/Assets/PowershellPipeworks_150.png"
7 | }
8 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_MainRegion.help.txt:
--------------------------------------------------------------------------------
1 | The InnerRegion is a Pipeworks Manifest setting that describes how the main region of a page will be rendered. It is as Hashtable, and the input in the Hashtable will be provided to the New-Region command.
2 |
3 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_MaximumRequestLength.help.txt:
--------------------------------------------------------------------------------
1 | The Maximum Request Length describes the maximum length of a request to an ASP.NET page.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_MemberTopic.help.txt:
--------------------------------------------------------------------------------
1 | The MemberTopics section is a list of strings, and it describes topics only visible to a person after they have logged in.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_ModuleTemplate.help.txt:
--------------------------------------------------------------------------------
1 | The moduleTemplate is the PowerShell web template (.pswt) used to display the core module page. A .pswt allows you to customize the look and feel of a pipeworks page. It directly replaces variable names within the page. By default, this is set to Module.pswt.
2 |
3 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_Nest.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/About_the_Pipeworks_Manifest_-_Nest.help.txt
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_Organization.help.txt:
--------------------------------------------------------------------------------
1 | The Organization section describes information about the publishing organization, and adds some contact information to each page.
2 |
3 |
4 | This example adds a phone number and an email link:
5 |
6 | @{
7 | Organization = @{
8 | Telephone = "+1(206)607-6555"
9 | Email = "info@start-automating.com"
10 | }
11 | }
12 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_PaymentProcessing.help.txt:
--------------------------------------------------------------------------------
1 | The Payment Processing section describes how the site will tie into various example platforms. This is required for Cost to work on commands.
2 |
3 |
4 | This example will setup payments via PayPal for the email sales@start-automating.com
5 |
6 | @{
7 | PaymentProcessing = @{
8 | PaypalEmail = 'sales@start-automating.com'
9 | }
10 | }
11 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_PoolSize.help.txt:
--------------------------------------------------------------------------------
1 | The PoolSize sets the number of RunspacePools set up to handle requests. The default is 2. The more runspace pools used, the more memory your site will consume, and the more users it can handle at the same time.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_Port.help.txt:
--------------------------------------------------------------------------------
1 | The Port setting of the Pipeworks manifest determines what port to use when publishing the site as an Intranet site.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_PrivacyPolicy.help.txt:
--------------------------------------------------------------------------------
1 | The PrivacyPolicy setting of the Pipeworks manifest contains any legal privacy policy required. If none is provided, a default privacy policy will be used.
2 |
3 |
4 | For an example of this default, visit [http://powershellpipeworks.com/?ShowPrivacyPolicy=true](http://powershellpipeworks.com/?ShowPrivacyPolicy=true)
5 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_PubCenter.help.txt:
--------------------------------------------------------------------------------
1 | The PubCenter section of the Pipeworks manifest describes how PubCenter ads will be placed in a Win8 application.
2 |
3 |
4 | Like the AdSense section, it requires an ID, and a BottomAdSlot or TopAdSlot are supported:
5 |
6 |
7 | Here's an example:
8 |
9 | @{
10 | PubCenter = @{
11 | ApplicationId = "1b9271e7-0be4-4ef1-84c3-9e8f921c1b4a"
12 | BottomAdUnit = "10048228"
13 | }
14 | }
15 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_PublishDirectory.help.txt:
--------------------------------------------------------------------------------
1 | The PublishDirectory setting in the Pipeworks manifest describes where the module should be published. By default, it will be published beneath c:\inetpub\wwwroot
2 |
3 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_Schema.help.txt:
--------------------------------------------------------------------------------
1 | The schema section of the Pipeworks manifest describes itemdata schemas used on the page. This is useful for making your site HTML5 compliant, and also for allowing people to interact more reliably with the site by using Get-Web -AsMicrodata
2 |
3 |
4 | Here's an example that declares a few schemas:
5 |
6 | @{
7 | Schema = @{
8 | GamerAchievementInfo = @{
9 | Name='GamerAchievementInfo'
10 | PSTypeName='http://shouldbeonschema.org/Class'
11 | Url = 'http://UnlockAchievement.com/GamerAchievementInfo/'
12 | Property = @{
13 | Name='Name'
14 | DeclaringType = 'http://schema.org/Thing'
15 | PSTypeName='http://shouldbeonschema.org/Property'
16 | Description='The name of the item.'
17 | }, @{
18 | Name='Description'
19 | DeclaringType = 'http://schema.org/Thing'
20 | PSTypeName='http://shouldbeonschema.org/Property'
21 | Description='A short description of the item.'
22 | }, @{
23 | Name='Image'
24 | DeclaringType = 'http://schema.org/Thing'
25 | PSTypeName='http://shouldbeonschema.org/Property'
26 | Description='URL of an image of the item.'
27 | TypeName = 'Url'
28 | }, @{
29 | Name='Url'
30 | DeclaringType = 'http://schema.org/Thing'
31 | PSTypeName='http://shouldbeonschema.org/Property'
32 | Description='The namespace the class is defined in.'
33 | TypeName = 'Url'
34 | }, @{
35 | Name='GamerTag'
36 | PSTypeName='http://shouldbeonschema.org/Property'
37 | Description='The gamertag or ID of an the gamer'
38 | TypeName = 'Url'
39 | }, @{
40 | Name='Games'
41 | PSTypeName='http://shouldbeonschema.org/Property'
42 | Description='A list of games the gamer owns or has played'
43 | TypeName = 'http://UnlockAchievement.com/GameAchievementInfo'
44 | }
45 |
46 | Description="Achievement information for a gamer."
47 |
48 | ParentClass = @{
49 | Name = 'Thing'
50 | Url = 'http://schema.org/Thing'
51 | PSTypeName = 'http://shouldbeonschema.org/Class'
52 | }
53 | }
54 |
55 | GameAchievementInfo = @{
56 | Name='GameAchievementInfo'
57 | PSTypeName='http://shouldbeonschema.org/Class'
58 | Url = 'http://UnlockAchievement.com/GameAchievementInfo/'
59 | Description="Achievement information for a game."
60 |
61 | ParentClass = @{
62 | Name = 'Thing'
63 | Url = 'http://schema.org/Thing'
64 | PSTypeName = 'http://shouldbeonschema.org/Class'
65 | }
66 |
67 |
68 |
69 | Property = @{
70 | Name='Name'
71 | DeclaringType = 'http://schema.org/Thing'
72 | PSTypeName='http://shouldbeonschema.org/Property'
73 | Description='The name of the item.'
74 | }, @{
75 | Name='Description'
76 | DeclaringType = 'http://schema.org/Thing'
77 | PSTypeName='http://shouldbeonschema.org/Property'
78 | Description='A short description of the item.'
79 | }, @{
80 | Name='Image'
81 | DeclaringType = 'http://schema.org/Thing'
82 | PSTypeName='http://shouldbeonschema.org/Property'
83 | Description='URL of an image of the item.'
84 | TypeName = 'Url'
85 | }, @{
86 | Name='Url'
87 | DeclaringType = 'http://schema.org/Thing'
88 | PSTypeName='http://shouldbeonschema.org/Property'
89 | Description='The namespace the class is defined in.'
90 | TypeName = 'Url'
91 | }, @{
92 | Name='PossibleScore'
93 | PSTypeName='http://shouldbeonschema.org/Property'
94 | Description='The possible score for a game'
95 | TypeName = 'Integer'
96 | }, @{
97 | Name='MyScore'
98 | PSTypeName='http://shouldbeonschema.org/Property'
99 | Description='My score for a game'
100 | TypeName = 'Integer'
101 | }, @{
102 | Name='PercentComplete'
103 | PSTypeName='http://shouldbeonschema.org/Property'
104 | Description='The percent of achievements unlocked for the game'
105 | TypeName = 'Float'
106 | }
107 | }
108 |
109 |
110 | }
111 | }
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_SecureSetting.help.txt:
--------------------------------------------------------------------------------
1 | The SecureSetting section of the Pipeworks manifest is a list of SecureSettings that will be copied into the web.config when the module is published. Get-SecureSetting will retreive these settings when used inside of a website. This enables seamless secure scripting between a development environment and a published page.
2 |
3 |
4 | See also:
5 |
6 | * [Scripting Securely with SecureSettings](/Scripting_Securely_with_SecureSettings/)
7 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_ShortCut.help.txt:
--------------------------------------------------------------------------------
1 | The shortcut section of the Pipeworks manifest describes local shortcuts to add to the Start Menu when the module is installed. This enables easier use of PowerShell built tools by everyday users, and easy access to online help for a module.
2 |
3 |
4 | Here's an example:
5 |
6 | @{
7 | Shortcut = @{
8 | "Asset Inventory Tool" = "Show-Asset -Show"
9 | "Help" = "http://startlearningpowershell.com"
10 | }
11 | }
12 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_ShowTweet.help.txt:
--------------------------------------------------------------------------------
1 | If the the ShowTweet setting is provided in the Pipeworks Manifest, each page will show a Tweet this link on each page. This setting can be overridden by using AntiSocial.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_SimplePages.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/About_the_Pipeworks_Manifest_-_SimplePages.help.txt
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_SlideShow.help.txt:
--------------------------------------------------------------------------------
1 | The SlideShow section of the Pipeworks manifest describes a SlideShow that will be played on the landing page. SlideShow items may be HTML or image links.
2 |
3 | Here's an example:
4 |
5 | @{
6 | Slideshow = @{
7 | Slides = "/Assets/Screenshot_NowPlaying.png",
8 | "/Assets/screenshot_DJMode.png",
9 | "/Assets/Screenshot_PlayingAndRaining.png",
10 | "/Assets/Screenshot_KaraokeMode.png",
11 | "/Assets/screenshot_Raining.png",
12 | "/Assets/Screenshot_VisualSearch.png",
13 | "/Assets/Screenshot_Edit_Lyrics.png",
14 | "/Assets/Screenshot_EditMetaData.png",
15 | "/Assets/Screenshot_PlayingAndRaining.png"
16 | }
17 | }
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_Stealth.help.txt:
--------------------------------------------------------------------------------
1 | If the Stealth setting is provided in the Pipeworks Manifest, the module will not generate a robots.txt or sitemap.xml, and all pages will include meta information dissuading search engines from crawling the page.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_Style.help.txt:
--------------------------------------------------------------------------------
1 | The Style section of the Pipeworks manifest declares a CSS style to use on each page. It is also used to provide color scheme information when generating a bootstrap theme or Win8 app.
2 |
3 | This section is almost exactly like CSS, except that nesting happens with Hashtables, not whitespace, and =, not : is used to separate values.
4 |
5 |
6 | Here's a simple sample:
7 |
8 | @{
9 | Style = @{
10 | Body = @{
11 | "font-family" = "Segoe UI"
12 | "font-size" = "1.05em"
13 |
14 | "background-color" = "#FFFFFF"
15 | "color" = "#09952E"
16 | }
17 | 'a' = @{
18 | 'color' = "#09952E"
19 | }
20 | }
21 |
22 | }
23 |
24 |
25 | Here is a more comple example:
26 |
27 | @{
28 | Style = @{
29 | body = @{
30 | "font-family" = "'Segoe UI', 'Segoe UI Symbol', Helvetica, Arial, sans-serif"
31 | 'font-size' = "1.1em"
32 | 'color' = '#0248B2'
33 | 'background-color' = '#FFFFFF'
34 | }
35 | 'a' = @{
36 | 'color' = '#012456'
37 | }
38 |
39 | '.MajorMenuItem' = @{
40 | 'font-size' = 'large'
41 | }
42 | '.MinorMenuItem' = @{
43 | 'font-size' = 'medium'
44 | }
45 | '.ExplanationParagraph' = @{
46 | 'font-size' = 'medium'
47 | 'text-indent' = '-10px'
48 | }
49 | '.ModuleWalkthruExplanation' = @{
50 | 'font-size' = 'medium'
51 | 'margin-right' = '3%'
52 | }
53 |
54 | '.ModuleWalkthruOutput' = @{
55 | 'font-size' = 'medium'
56 | }
57 | '.PowerShellColorizedScript' = @{
58 | 'font-size' = 'medium'
59 | }
60 |
61 | }
62 | }
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_Table.help.txt:
--------------------------------------------------------------------------------
1 | The Table section of the Pipeworks manifest describes information stored in a public azure table that the module service can access.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_Template.help.txt:
--------------------------------------------------------------------------------
1 | The template setting of the Pipeworks manifest describes a PowerShell web template (.pswt) to use for each page on the site.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_TopicTemplate.help.txt:
--------------------------------------------------------------------------------
1 | The TopicTemplate is the PowerShell web template (.pswt) used to display each command in the site. A .pswt allows you to customize the look and feel of a pipeworks page. It directly replaces variable names within the page. By default, this is set to Topic.pswt.
2 |
3 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_TrustedWalkthrus.help.txt:
--------------------------------------------------------------------------------
1 | The TrustedWalkthrus list is a set of walkthrus that the site trusts enough to run. These walkthrus should run quickly, not require user input, not require elevation, and yet be helpful in demonstrating functionality.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_Tweet.help.txt:
--------------------------------------------------------------------------------
1 | If the Pipeworks Manifest includes the Tweet setting, a tweet this link will be added to each page. This setting can be overridden with .AntiSocial.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_TwitterId.help.txt:
--------------------------------------------------------------------------------
1 | If the Pipeworks Manifest includes the TwitterID setting, a follow for that TwitterID will be added to each page. This setting can be overridden with .AntiSocial.
2 |
3 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_UseBootstrap.help.txt:
--------------------------------------------------------------------------------
1 | BootStrap (or UseBootStrap) instructs Pipeworks to use Twitter Bootstrap to build a site.
2 |
3 |
4 | If the theme is not present, this will download a twitter bootstrap theme according using color scheme specified in the Style section of the Pipeworks manifest. To refresh the them, delete bootstrap.js from the JS directory of the module and republish.
5 |
6 |
7 | Using Bootstrap enables many features within Pipeworks, and changes the default layout. It enables a navbar that links to the topics and commands in the module. It also changes the deault view to a set of HangingSpans, which will expand out when clicked.
8 |
9 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_UseGRaphael.help.txt:
--------------------------------------------------------------------------------
1 | If UseGraphael is provided in the Pipeworks manifest, Pipeworks will download [GRaphael](http://g.raphaeljs.com/) for the creation of graphs within the page.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_UseJQuery.help.txt:
--------------------------------------------------------------------------------
1 | If UseJQuery is provided, JQuery will be downloaded and used in each page in the site.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_UseJQueryUI.help.txt:
--------------------------------------------------------------------------------
1 | If UseJQueryUI is set to true in the Pipeworks manifest, JQueryUI will be used throughout the site.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_UseRaphael.help.txt:
--------------------------------------------------------------------------------
1 | If UseGraphael is provided in the Pipeworks manifest, Pipeworks will download [Raphael](http://raphaeljs.com/) for the creation of graphs within the page.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_UseShiv.help.txt:
--------------------------------------------------------------------------------
1 | If UseShiv is provided, the HTML5 shiv tool for IE will be downloaded, and installed on each page.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_UseTableSorter.help.txt:
--------------------------------------------------------------------------------
1 | If UseTableSorter is provided, the TableSorter JQuery plugin will be downloaded, and used on each page.
2 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_UserTable.help.txt:
--------------------------------------------------------------------------------
1 | The UserTable section of the Pipeworks manifest describes how users of a site will be stored in Azure Table Storage.
2 |
3 | Here's an example (from the site [StartLearningPowerShell.com](http://start-learningpowershell.com/)
4 |
5 | @{
6 | UserTable = @{
7 | Name = 'StartLearningPowerShellUsers'
8 | Partition = 'Users'
9 | StorageAccountSetting = 'AzureStorageAccountName'
10 | StorageKeySetting = 'AzureStorageAccountKey'
11 | }
12 | }
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_WebCommand.help.txt:
--------------------------------------------------------------------------------
1 | The WebCommand section of the Pipeworks manifest describes which commands will be usable as web services, and what options to use when running a command.
2 |
3 | It is a hashtable of hashtables, where the key of each hashtable is the name of the command and the value is a hashtable containing parameters for the command Invoke-WebCommand.
4 |
5 |
6 | This is the WebCommand section of the Pipework's manifest:
7 |
8 | @{
9 | WebCommand = @{
10 | "Write-Link" = @{
11 | HideParameter = "AmazonAccessKey", "AmazonSecretKey", "AmazonReturnUrl", "AmazonInputUrl",
12 | "AmazonIpnUrl", "UseOAth", "CollectShippingAddress", "AmazonAbandonUrl", "ToFacebookLogin",
13 | "FacebookAppId", "ModuleServiceUrl", "FacebookLoginScope", "AmazonPaymentsAccountID", "GoogleCheckoutMerchantID", "SortedLinkTable"
14 | PlainOutput = $true
15 |
16 | }
17 | "New-PipeworksManifest" = @{
18 | ContentType = 'text/plain'
19 | }
20 |
21 |
22 | "ConvertFrom-Markdown" = @{
23 | ParameterAlias = @{
24 | 'm' = 'Markdown'
25 | 'md' = 'Markdown'
26 | }
27 | FriendlyName = "Mess With Markdown"
28 | HideParameter = 'Splat'
29 | }
30 |
31 | "Write-ScriptHTML" = @{
32 |
33 | PlainOutput = $true
34 | HideParameter = @('Palette', 'Start', 'End', 'Script')
35 | ParameterOrder = 'Text'
36 | ParameterAlias = @{
37 | 't'= 'Text'
38 |
39 | }
40 | FriendlyName = "Show Scripts as HTML"
41 | }
42 | "Write-ASPDotNetScriptPage" = @{
43 |
44 | ContentType = "text/plain"
45 | HideParameter = @('MasterPage', 'CodeFile', 'Inherit', 'RunScriptMethod', 'FileName')
46 | FriendlyName = "PowerShell in ASP.NET"
47 | }
48 |
49 | "Write-Crud" = @{
50 | ContentType = "text/plain"
51 | PlainOutput = $true
52 | }
53 |
54 | }
55 | }
56 |
--------------------------------------------------------------------------------
/en-us/About_the_Pipeworks_Manifest_-_WebWalkthrus.help.txt:
--------------------------------------------------------------------------------
1 | The WebWalkthrus setting of the Pipeworks manifest lists walkthrus whose output should be considered HTML. Each WebWalkthru should also be in the Trusted Walkthru list. If a trusted walkthru runs, and is not in WebWalkthrus, it's result will be piped into Out-HTML.
2 |
--------------------------------------------------------------------------------
/en-us/Building_With_Bootstrap.walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Building_With_Bootstrap.walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/Building_with_Blob_Storage.walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Building_with_Blob_Storage.walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/Creating_a_CitiBike_Station_Finder.walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Creating_a_CitiBike_Station_Finder.walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/From_Script_To_Software_Service.Walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/From_Script_To_Software_Service.Walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/Get-Paid_with_Stripe.walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Get-Paid_with_Stripe.walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/Get-Web_Content_From_Anywhere.walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Get-Web_Content_From_Anywhere.walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/Getting_GitIt.walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Getting_GitIt.walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/Getting_Started_With_Pipeworks.md:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Getting_Started_With_Pipeworks.md
--------------------------------------------------------------------------------
/en-us/Implicit_Texting_With_Twilio.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Implicit_Texting_With_Twilio.help.txt
--------------------------------------------------------------------------------
/en-us/Integrated_Intranet.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Integrated_Intranet.help.txt
--------------------------------------------------------------------------------
/en-us/JQueryUI_In_Pipeworks.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/JQueryUI_In_Pipeworks.help.txt
--------------------------------------------------------------------------------
/en-us/Looking_Up_Locations_With_Resolve-Location.walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Looking_Up_Locations_With_Resolve-Location.walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/Making_Editing_Easier_With_Markdown.walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Making_Editing_Easier_With_Markdown.walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/Making_Tables_With_Out-HTML.walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Making_Tables_With_Out-HTML.walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/Managing_Amazon_Web_Services_With_PowerShell_Pipeworks.walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Managing_Amazon_Web_Services_With_PowerShell_Pipeworks.walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/New-Region_And_JQueryUI.walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/New-Region_And_JQueryUI.walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/New-Webpage_and_JQuery.walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/New-Webpage_and_JQuery.walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/NoHTML_Sites.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/NoHTML_Sites.help.txt
--------------------------------------------------------------------------------
/en-us/Pick_up_the_Phone_with_Pipeworks.walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Pick_up_the_Phone_with_Pipeworks.walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/Pipeworks_Quickstart.walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Pipeworks_Quickstart.walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/Pipeworks_Writes_CRUD.walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Pipeworks_Writes_CRUD.walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/Powerful_Powershell_Formatting.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Powerful_Powershell_Formatting.help.txt
--------------------------------------------------------------------------------
/en-us/Publishing_Pipeworks_To_Azure.walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Publishing_Pipeworks_To_Azure.walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/Scripting_Securely_with_SecureSettings.walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Scripting_Securely_with_SecureSettings.walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/Scripting_With_Superglue.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Scripting_With_Superglue.help.txt
--------------------------------------------------------------------------------
/en-us/Simpler_SEO.walkthru.help.txt:
--------------------------------------------------------------------------------
1 | # Search Engine Optimization is very simple in PowerShell Pipeworks.
2 | # PowerShell Pipeworks can easily integrate with [Google's Webmaster tools](http://www.google.com/webmasters/tools/).
3 | New-PipeworksManifest -Name ASampleModule -GoogleSiteVerification xjCcGADm2Pnu7fF3WZnPj5UYND9SVqB3qzJuvhe0k1o
4 |
5 | # You can add Analytics trackers just as easily:
6 | New-PipeworksManifest -Name ASampleModule -AnalyticsId UA-XXXXXXX-XX
7 |
8 | # It can also work with [Bing's webmaster tools](http://www.bing.com/toolbox/webmaster)
9 | New-PipeworksManifest -Name ASampleModule -BingValidationKey 7B94933EC8C374B455E8263FCD4FE5EF
10 |
11 | # You can add meta keywords to each page
12 | New-PipeworksManifest -Name ASampleModule -Keyword A, Sample, Module
13 |
14 | # You can let people Like your site by making it a Facebook app:
15 | New-PipeworksManifest -Name ASampleModule -FacebookAppId MyFacebookAppId
16 |
17 | # You can increase sharing by adding Tweet links:
18 | New-PipeworksManifest -Name ASampleModule -Tweet
19 |
20 | # Pipeworks also automatically does a lot of little things to help SEO:
21 | # * [Sitemaps](http://start-automating.com/Sitemap.xml) are automatically generated
22 | # * Pages automatically get description <meta> tags
23 | # * Creating RSS feeds for topics and commands
24 | # * Friendly URLs for aliases, commands, and topics, like [http://start-automating.com/Training/](http://start-automating.com/Training/)
25 | $null
26 |
27 |
28 |
29 |
--------------------------------------------------------------------------------
/en-us/Simplified_SQL.walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Simplified_SQL.walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/Simplifying_Slideshows.walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Simplifying_Slideshows.walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/The_Pipeworks_Manifest.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/The_Pipeworks_Manifest.help.txt
--------------------------------------------------------------------------------
/en-us/The_Wonders_Of_Wolfram_Alpha.walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/The_Wonders_Of_Wolfram_Alpha.walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/Using_Azure_Table_Storage_in_Pipeworks.walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Using_Azure_Table_Storage_in_Pipeworks.walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/What_Pipeworks_Does.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/What_Pipeworks_Does.help.txt
--------------------------------------------------------------------------------
/en-us/Why_Windows.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Why_Windows.help.txt
--------------------------------------------------------------------------------
/en-us/Working_With_Write-Link.walkthru.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/Working_With_Write-Link.walkthru.help.txt
--------------------------------------------------------------------------------
/en-us/about_Pipeworks.help.txt:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/en-us/about_Pipeworks.help.txt
--------------------------------------------------------------------------------
/write-crud.ps1:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/StartAutomating/Pipeworks/23b133b47ae2a33869064a27b98e4f61ae4ff73e/write-crud.ps1
--------------------------------------------------------------------------------