├── .github ├── ISSUE_TEMPLATE │ ├── question.md │ ├── spike.md │ ├── feature_request.md │ └── bug_report.md ├── CODEOWNERS └── PULL_REQUEST_TEMPLATE.md ├── LICENSE.md ├── README.md ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md └── kentico.gitignore /.github/ISSUE_TEMPLATE/question.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Question 3 | about: Ask a question 4 | 5 | --- 6 | 7 | ### Question 8 | 9 | What do you want to ask? 10 | 11 | ### Reference 12 | 13 | * URL 14 | -------------------------------------------------------------------------------- /.github/CODEOWNERS: -------------------------------------------------------------------------------- 1 | # Users referenced in this file will automatically be requested as reviewers for PRs that modify the given paths. 2 | # See https://help.github.com/articles/about-code-owners/ 3 | 4 | * @Kentico/developer-relations 5 | * @yuriys-kentico 6 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/spike.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Spike 3 | about: Suggest an analysis of a problem 4 | 5 | --- 6 | 7 | ### Expected result 8 | 9 | What do we want to explore and why? Which questions do we want to answer with this spike? 10 | 11 | ### Additional context 12 | 13 | Add any other context or guidelines here. 14 | 15 | ### Resources 16 | 17 | * URL 18 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature_request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Feature request 3 | about: Suggest an idea for this project 4 | 5 | --- 6 | 7 | ### Motivation 8 | 9 | Why is this feature required? What problems does it solve? 10 | 11 | ### Proposed solution 12 | 13 | An ideal solution for the above problems. 14 | 15 | ### Additional context 16 | 17 | Add any other context, screenshots, or reference links about the feature request here. 18 | -------------------------------------------------------------------------------- /.github/PULL_REQUEST_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | ### Motivation 2 | 3 | Which issue does this fix? Fixes #`issue number` 4 | 5 | If no issue exists, what is the fix or new feature? Were there any reasons to fix/implement things that are not obvious? 6 | 7 | ### Checklist 8 | 9 | - [ ] Code follows coding conventions held in this repo 10 | - [ ] Automated tests have been added 11 | - [ ] Tests are passing 12 | - [ ] Docs have been updated (if applicable) 13 | - [ ] Temporary settings (e.g. variables used during development and testing) have been reverted to defaults 14 | 15 | ### How to test 16 | 17 | If manual testing is required, what are the steps? 18 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug_report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report 3 | about: Create a report to help us improve 4 | 5 | --- 6 | 7 | ### Brief bug description 8 | 9 | What went wrong? 10 | 11 | ### Repro steps 12 | 13 | 1. Go to '...' 14 | 2. Click on '....' 15 | 3. Scroll down to '....' 16 | 4. See error 17 | 18 | ### Expected behavior 19 | 20 | What the correct behavior is? 21 | 22 | ### Test environment 23 | 24 | - Platform/OS: [e.g. .NET Core 2.1, iOS] 25 | - Browser [e.g. chrome, safari] 26 | - Version [e.g. 22] 27 | 28 | ### Additional context 29 | 30 | Add any other context about the problem here. 31 | 32 | ### Screenshots 33 | 34 | Add links to screenshots, if possible. -------------------------------------------------------------------------------- /LICENSE.md: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2016 Kentico 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Kentico Gitignore 2 | 3 | This gitignore file is designed to help you ignore/include all the right files in your Git repository for Kentico projects. 4 | 5 | ## Important notes 6 | 1. Uses the default ignore from Visual Studio as the starting point. 7 | 1. Tested in **Kentico 9** only. 8 | 1. **Ignores** the `bin` directory and **includes** the `Lib` directory. 9 | * You can restore the Kentico DLLs from the `Lib` directory after restoring a repository for the first time. 10 | 1. **Ignores** starter site files. 11 | 12 | More information at http://devnet.kentico.com/articles/gitignore-for-kentico 13 | 14 | ## Protecting sensitive settings 15 | Even if your repository is only intended for private distribution you should avoid allowing sensitive and/or environment specific data such as connection string and hash string salts from being checked into your source control. rather than ignore the whole `web.config` file, we recommend adding `file="AppSettings.config"` and `configSource="ConnectionStrings.config"` to the app settings and connection strings elements in the `web.config` respectively. Next, move the sensitive data to those files. It is also recommended that you also add template versions of these files for reference. When pulling a fresh copy of the repository the developer should request a copy of any sensitive data from another developer or some other secured location. You can find an example of this practice in the [Kentico MVC sample site on GitHub](https://github.com/Kentico/Mvc/tree/master/src/DancingGoat). 16 | 17 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. 6 | 7 | ## Our Standards 8 | 9 | Examples of behavior that contributes to creating a positive environment include: 10 | 11 | * Using welcoming and inclusive language 12 | * Being respectful of differing viewpoints and experiences 13 | * Gracefully accepting constructive criticism 14 | * Focusing on what is best for the community 15 | * Showing empathy towards other community members 16 | 17 | Examples of unacceptable behavior by participants include: 18 | 19 | * The use of sexualized language or imagery and unwelcome sexual attention or advances 20 | * Trolling, insulting/derogatory comments, and personal or political attacks 21 | * Public or private harassment 22 | * Publishing others' private information, such as a physical or electronic address, without explicit permission 23 | * Other conduct which could reasonably be considered inappropriate in a professional setting 24 | 25 | ## Our Responsibilities 26 | 27 | Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. 28 | 29 | Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. 30 | 31 | ## Scope 32 | 33 | This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. 34 | 35 | ## Enforcement 36 | 37 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at DevelopersCommunity@kentico.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. 38 | 39 | Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. 40 | 41 | ## Attribution 42 | 43 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [https://contributor-covenant.org/version/1/4][version] 44 | 45 | [homepage]: https://contributor-covenant.org 46 | [version]: https://contributor-covenant.org/version/1/4/ 47 | 48 | ![Analytics](https://kentico-ga-beacon.azurewebsites.net/api/UA-69014260-4/Kentico/Home/master/CODE_OF_CONDUCT.md?pixel) 49 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Ways to contribute 2 | 3 | 4 | There are many different ways in which you can contribute. One of the easiest ways is simply to use our software and provide us with your feedback through the right channel. You can also help us improve the open-source projects by submitting pull requests with code and documentation changes. 5 | 6 | ## Where to get support 7 | Please note that **level of provided support is always determined by the [LICENSE](LICENSE.md)** of a given open-source project. Also, always make sure you use the **[latest version](../../releases)** of any given OS project. We can't provide any help for older versions. We don't want to make things complicated so we try to take the same approach in all our repositories. 8 | 9 | ### I found a bug in a Kentico's open-source project 10 | 11 | 12 | Sorry to hear that. Just log a new [GitHub issue](../../issues) and someone will take a look at it. Remember, the more information you provide, the easier it will be to fix the issue. If you feel like it, you can also fix the bug on your own and submit a new pull request. 13 | 14 | ### I need help with using the projects and/or coding 15 | 16 | 17 | To get help with coding and structuring your projects, use [StackOverflow](https://stackoverflow.com/) to ask questions with one of the following tags: 18 | - [`kentico-cloud`](https://stackoverflow.com/questions/tagged/kentico-cloud) 19 | - [`kentico`](https://stackoverflow.com/questions/tagged/kentico) 20 | 21 | Our team members and the community monitor these channels on a regular basis. 22 | 23 | ### I want to report a security bug 24 | 25 | 26 | Security issues and bugs should be reported privately, via email, to the Kentico Developer Community Team developerscommunity@kentico.com. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. 27 | 28 | 29 | ### I have an idea for a new feature (or feedback on existing functionality) 30 | 31 | 32 | Everybody loves new features! You can submit a new [feature request](../../issues) or you can code it on your own and [send us a pull request](#submitting-pull-requests). In either case, don't forget to mention what's the use case and what's the expected output. 33 | 34 | 35 | ## Submitting pull requests 36 | 37 | 38 | Unless you're fixing a typo, it's usually a good idea to discuss the feature before you submit a pull request with code changes, so let's start with submitting a new [GitHub issue](../../issues) and discussing the whether it fits the vision of a given project. 39 | You might also read these two blogs posts on contributing code: [Open Source Contribution Etiquette](http://tirania.org/blog/archive/2010/Dec-31.html) by Miguel de Icaza and [Don't "Push" Your Pull Requests](https://www.igvita.com/2011/12/19/dont-push-your-pull-requests/) by Ilya Grigorik. Note that all code submissions will be rigorously reviewed and tested by the Kentico Maintainers teams, and only those that meet an high bar for both quality and design/roadmap appropriateness will be merged into the source. 40 | 41 | 42 | ### Example - process of contribution 43 | If not stated otherwise, we use [feature branch workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/feature-branch-workflow). 44 | 45 | To start with coding, fork the repository you want to contribute to, create a new branch, and start coding. Once the functionality is [done](#Definition-of-Done), you can submit a [pull request](https://help.github.com/articles/about-pull-requests/). 46 | 47 | ### Definition of Done 48 | 49 | 50 | - New/fixed code is covered with tests 51 | - CI can build the code 52 | - All tests are pass 53 | - New version number follows [semantic versioning](https://semver.org/) 54 | - Coding style (spaces, indentation) is in line with the rest of the code in a given repository 55 | - Documentation is updated (e.g. code examples in README, Wiki pages, etc.) 56 | - All `public` members are documented (using XML doc, phpdoc, etc.) 57 | - Code doesn't contain any secrets (private keys, etc.) 58 | - Commit messages are clear. Please read these articles: [Writing good commit messages](https://github.com/erlang/otp/wiki/Writing-good-commit-messages), [A Note About Git Commit Messages](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), [On commit messages](https://who-t.blogspot.com/2009/12/on-commit-messages.html) 59 | 60 | 61 | ### Feedback 62 | 63 | 64 | Your pull request will now go through extensive checks by the subject matter experts on our team. Please be patient. Update your pull request according to feedback until it is approved by one of the Kentico maintainers. After that, one of our team members may adjust the branch you merge into based on the expected release schedule. 65 | 66 | 67 | ## Code of Conduct 68 | 69 | 70 | The Kentico team is committed to fostering a welcoming community, therefore this project has adopted the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). If you have any additional questions or comments, you can contact us directly at developerscommunity@kentico.com. 71 | 72 | ![Analytics](https://kentico-ga-beacon.azurewebsites.net/api/UA-69014260-4/Kentico/Home/master/CONTRIBUTING.md?pixel) 73 | -------------------------------------------------------------------------------- /kentico.gitignore: -------------------------------------------------------------------------------- 1 | ## Ignore Visual Studio temporary files, build results, and 2 | ## files generated by popular Visual Studio add-ons. 3 | 4 | # User-specific files 5 | *.suo 6 | *.user 7 | *.userosscache 8 | *.sln.docstates 9 | 10 | # User-specific files (MonoDevelop/Xamarin Studio) 11 | *.userprefs 12 | 13 | # Build results 14 | [Dd]ebug/ 15 | [Dd]ebugPublic/ 16 | [Rr]elease/ 17 | [Rr]eleases/ 18 | [Xx]64/ 19 | [Xx]86/ 20 | [Bb]uild/ 21 | bld/ 22 | [Bb]in/ 23 | [Oo]bj/ 24 | 25 | # Visual Studio 2015 cache/options directory 26 | .vs/ 27 | # Visual Studio Code configurations directory 28 | .vscode/ 29 | # Uncomment if you have tasks that create the project's static files in wwwroot 30 | #wwwroot/ 31 | 32 | # MSTest test Results 33 | [Tt]est[Rr]esult*/ 34 | [Bb]uild[Ll]og.* 35 | 36 | # NUNIT 37 | *.VisualState.xml 38 | TestResult.xml 39 | 40 | # Build Results of an ATL Project 41 | [Dd]ebugPS/ 42 | [Rr]eleasePS/ 43 | dlldata.c 44 | 45 | # DNX 46 | project.lock.json 47 | artifacts/ 48 | 49 | *_i.c 50 | *_p.c 51 | *_i.h 52 | *.ilk 53 | *.meta 54 | *.obj 55 | *.pch 56 | *.pdb 57 | *.pgc 58 | *.pgd 59 | *.rsp 60 | *.sbr 61 | *.tlb 62 | *.tli 63 | *.tlh 64 | *.tmp 65 | *.tmp_proj 66 | *.log 67 | *.vspscc 68 | *.vssscc 69 | .builds 70 | *.pidb 71 | *.svclog 72 | *.scc 73 | 74 | # Chutzpah Test files 75 | _Chutzpah* 76 | 77 | # Visual C++ cache files 78 | ipch/ 79 | *.aps 80 | *.ncb 81 | *.opendb 82 | *.opensdf 83 | *.sdf 84 | *.cachefile 85 | *.VC.db 86 | 87 | # Visual Studio profiler 88 | *.psess 89 | *.vsp 90 | *.vspx 91 | *.sap 92 | 93 | # TFS 2012 Local Workspace 94 | $tf/ 95 | 96 | # Guidance Automation Toolkit 97 | *.gpState 98 | 99 | # ReSharper is a .NET coding add-in 100 | _ReSharper*/ 101 | *.[Rr]e[Ss]harper 102 | *.DotSettings.user 103 | 104 | # JustCode is a .NET coding add-in 105 | .JustCode 106 | 107 | # TeamCity is a build add-in 108 | _TeamCity* 109 | 110 | # DotCover is a Code Coverage Tool 111 | *.dotCover 112 | 113 | # NCrunch 114 | _NCrunch_* 115 | .*crunch*.local.xml 116 | nCrunchTemp_* 117 | 118 | # MightyMoose 119 | *.mm.* 120 | AutoTest.Net/ 121 | 122 | # Web workbench (sass) 123 | .sass-cache/ 124 | 125 | # Installshield output folder 126 | [Ee]xpress/ 127 | 128 | # DocProject is a documentation generator add-in 129 | DocProject/buildhelp/ 130 | DocProject/Help/*.HxT 131 | DocProject/Help/*.HxC 132 | DocProject/Help/*.hhc 133 | DocProject/Help/*.hhk 134 | DocProject/Help/*.hhp 135 | DocProject/Help/Html2 136 | DocProject/Help/html 137 | 138 | # Click-Once directory 139 | publish/ 140 | 141 | # Publish Web Output 142 | *.[Pp]ublish.xml 143 | *.azurePubxml 144 | # TODO: Un-comment the next line if you do not want to checkin 145 | # your web deploy settings because they may include unencrypted 146 | # passwords 147 | #*.pubxml 148 | 149 | *.publishproj 150 | 151 | # NuGet Packages 152 | *.nupkg 153 | # The packages folder can be ignored because of Package Restore 154 | **/packages/* 155 | # except build/, which is used as an MSBuild target. 156 | !**/packages/build/ 157 | # Uncomment if necessary however generally it will be regenerated when needed 158 | #!**/packages/repositories.config 159 | # NuGet v3's project.json files produces more ignoreable files 160 | *.nuget.props 161 | *.nuget.targets 162 | 163 | # Microsoft Azure Build Output 164 | csx/ 165 | *.build.csdef 166 | 167 | # Microsoft Azure Emulator 168 | ecf/ 169 | rcf/ 170 | # Microsoft Azure ApplicationInsights config file 171 | ApplicationInsights.config 172 | # Windows Store app package directory 173 | AppPackages/ 174 | BundleArtifacts/ 175 | 176 | # Visual Studio cache files 177 | # files ending in .cache can be ignored 178 | *.[Cc]ache 179 | # but keep track of directories ending in .cache 180 | !*.[Cc]ache/ 181 | 182 | # Others 183 | ClientBin/ 184 | [Ss]tyle[Cc]op.* 185 | ~$* 186 | *~ 187 | *.dbmdl 188 | *.dbproj.schemaview 189 | *.pfx 190 | *.publishsettings 191 | node_modules/ 192 | orleans.codegen.cs 193 | 194 | # RIA/Silverlight projects 195 | Generated_Code/ 196 | 197 | # Backup & report files from converting an old project file 198 | # to a newer Visual Studio version. Backup files are not needed, 199 | # because we have git ;-) 200 | _UpgradeReport_Files/ 201 | Backup*/ 202 | UpgradeLog*.XML 203 | UpgradeLog*.htm 204 | 205 | # SQL Server files 206 | *.mdf 207 | *.ldf 208 | 209 | # Business Intelligence projects 210 | *.rdl.data 211 | *.bim.layout 212 | *.bim_*.settings 213 | 214 | # Microsoft Fakes 215 | FakesAssemblies/ 216 | 217 | # GhostDoc plugin setting file 218 | *.GhostDoc.xml 219 | # Node.js Tools for Visual Studio 220 | .ntvs_analysis.dat 221 | 222 | # Visual Studio 6 build log 223 | *.plg 224 | 225 | # Visual Studio 6 workspace options file 226 | *.opt 227 | 228 | # Visual Studio LightSwitch build output 229 | **/*.HTMLClient/GeneratedArtifacts 230 | **/*.DesktopClient/GeneratedArtifacts 231 | **/*.DesktopClient/ModelManifest.xml 232 | **/*.Server/GeneratedArtifacts 233 | **/*.Server/ModelManifest.xml 234 | _Pvt_Extensions 235 | # LightSwitch generated files 236 | GeneratedArtifacts/ 237 | ModelManifest.xml 238 | 239 | # Paket dependency manager 240 | .paket/paket.exe 241 | 242 | # FAKE - F# Make 243 | .fake/ 244 | 245 | ## Windows ignores 246 | # Windows image file caches 247 | Thumbs.db 248 | ehthumbs.db 249 | 250 | # Folder config file 251 | Desktop.ini 252 | 253 | # Recycle Bin used on file shares 254 | $RECYCLE.BIN/ 255 | 256 | # Windows Installer files 257 | *.cab 258 | *.msi 259 | *.msm 260 | *.msp 261 | 262 | # Windows shortcuts 263 | *.lnk 264 | 265 | ## Kentico project files 266 | 267 | # Include some Kentico folders excluded by rules above 268 | !CMS/CMSAdminControls/*/ 269 | !CMS/CMSModules/System/*/ 270 | !CMS/App_Data/CIRepository/** 271 | 272 | # Kentico temporary/environment files 273 | CMS/App_Data/AzureCache 274 | CMS/App_Data/AzureTemp 275 | CMS/App_Data/CMSModules/DeviceProfile/logFiftyOne.txt 276 | CMS/App_Data/CMSModules/DeviceProfiles/logFiftyOne.txt 277 | CMS/App_Data/CMSModules/WebFarm/webfarm.sync 278 | CMS/App_Data/CMSTemp 279 | CMS/App_Data/Persistent 280 | CMS/CMSSiteUtils/Export 281 | CMS/CMSSiteUtils/Import 282 | 283 | # Ignore all smart search indexes, but not the other system folder contents 284 | CMS/App_Data/CMSModules/SmartSearch/** 285 | !CMS/App_Data/CMSModules/SmartSearch/*/ 286 | !CMS/App_Data/CMSModules/SmartSearch/_StopWords/** 287 | !CMS/App_Data/CMSModules/SmartSearch/_Synonyms/** 288 | 289 | ## Kentico Starter Sites 290 | # Starter site resource Files 291 | CMS/App_Data/DancingGoat 292 | 293 | # Starter site web templates 294 | CMS/App_Data/Templates/CommunitySite 295 | CMS/App_Data/Templates/CorporateSite 296 | CMS/App_Data/Templates/DancingGoat 297 | CMS/App_Data/Templates/EcommerceSite 298 | CMS/App_Data/Templates/IntranetPortal 299 | CMS/App_Data/Templates/PersonalSite 300 | 301 | # Starter site app themes 302 | CMS/App_Themes/CommunitySite 303 | CMS/App_Themes/CorporateSite 304 | CMS/App_Themes/EcommerceSite 305 | CMS/App_Themes/IntranetPortal* 306 | CMS/App_Themes/PersonalSite 307 | 308 | # Starter site ASPX templates 309 | CMS/CMSTemplates/CorporateSite 310 | 311 | # Starter site media libraries 312 | CMS/CommunitySite 313 | CMS/CorporateSite 314 | CMS/DancingGoat 315 | CMS/EcommerceSite 316 | CMS/IntranetPortal 317 | CMS/PersonalSite 318 | 319 | ## Project specific ignores 320 | # Sensitive settings 321 | AppSettings.config 322 | ConnectionStrings.config 323 | 324 | # Project media libraries (recommend shared file storage) 325 | # e.g. CMS/{SiteCodeName} 326 | --------------------------------------------------------------------------------