DotNest SDK readme
DotNest SDK is a local developer environment for building Media Themes to be deployed on sites running on DotNest. The base of the source code on the
master branch is the same Orchard version that is running on DotNest as well as all the hotfixes and mods we've applied to it. On top of that, all the open-source modules and themes are added as Git submodules, which gives you the ability to develop your theme and run your site locally in an environment quite close to the live DotNest site.
- Go to GitHub and fork the DotNest SDK repository or create an empty repository. For simplicity, we'll refer to your repository as
forkfrom now on and assume a simple branching strategy with only one additional branch for development, but your use-case might be more complex.
- Set up a mirror on Git-Hg Mirror to automatically (and continuously) synchronize every commit from the original repository to your fork. This gives you an easy way to always work with same code base as what is running on DotNest.
Git clone URLshould be
Hg clone URL(don't worry about
Hg) should be a similar URL pointing to your fork with some authentication details to allow Git-Hg Mirror to push to your repository. You create an access token under under your GitHub settings (select full
repoaccess) and use it as follows:
Mirroring directionshould be
Git to Hg.
- Make sure that you never commit anything on the branches coming from the original repository, otherwise the synchronization will fail.
Alternative: Hg instead of Git
- By setting up the mirror in a slightly different way, you can also use Mercurial for your project. In that case the authentication details are defined in the
username:passwordformat (make sure that the user has write access to the repository).
- Note that the DotNest SDK is also available as a Mercurial repository on Bitbucket, but the Git and Hg repositories of the DotNest SDK are mirrored bi-directionally, so it doesn't matter which one you're synchronizing from.
- You need to enable the
hggitextension to be able to checkout the Git submodules in a Mercurial repository.
Working with the repository
- Whenever you create any branches, make sure that you prefix their names so they don't collide with the ones in the SDK. For example, if the project you're working is called
Awesome Project, then your development branch should be created on top of
devand name it e.g.
- You might also want to change the default branch of your fork to your development branch.
- In case new commits are pushed to your fork from the original repository, check the changes (e.g. new modules might be added that you also need to add to your custom solution) and merge
devto your development branch.
- Create a custom solution file on your prefixed development branch as a copy of
AwesomeProject.sln. Your custom projects should be added to this solution, not
- From here on, general Orchard theme development rules apply with some DotNest-related extra. You can read about all these on the
Theming a DotNest sitepage of the DotNest Knowledge Base.
- If your theme contains Liquid templates, enable the
Liquid Markup View Enginefeature for these to be picked up by Orchard.
- The Media Theme on DotNest also has an automated mechanism to include some site-level resources. This might come in handy e.g. if your theme doesn't have a base theme and/or you're not overriding the
Layoutshapes. You can enable the same functionality by enabling the
DotNest SDKfeature, which will automatically include the following resources on every page load (if they are available in the active theme):
- You can synchronize content from your site running on DotNest by exporting it and then importing it locally after enabling the
Help us make it better!
In case you come across an Orchard bug during development, don't keep it to yourself: Orchard bugs should be reported at the official Orchard GitHub repository. There is a chance though that the problem you've discovered is already fixed since the latest release and we could add the necessary changes as a hotfix to DotNest (and the DotNest SDK) to improve it. You can tell us about it by opening an issue at the DotNest SDK GitHub repository. Thanks!