Blog

Aceik & Sitecore’s Digital Wine-Down

Last week, Aceik and Sitecore brought together 16 digital experts from around Australia to discuss digital transformation – the trends, challenges and risks facing a new project in 2021. And it wouldn’t be a robust discussion without a wine tasting – kindly delivered by SocialTable and Price’s Wines.

Our moderator introduced two topics then guests were divided into groups of 6 to discuss. Upon return to the main track, guests then shared their unique discussion. And today, we wanted to share the key highlights.

Question 1

What are the biggest factors you think will influence investment and digital transformation over the next 12 months?

  • Customer-driven service channel
  • Being reactive to competitor demand
  • We’re not competing with competitors anymore, we’re competing with the most recent best experience the customer has had, and that’s the new benchmark
  • Depending on which industry the impact of COVID-19 varied (ie retail saw loads of money move into their ecommerce stores)
  • COVID-19 made getting sign-off easier on digital projects. Because digital was pretty much the only active channel
  • Increased emphasis on ROI now
  • Public sector using data in marketing campaigns
  • Coming out of COVID-19 lockdowns might be the perfect time to be disruptive

Question 2

What do you think are the biggest risks or pain points that companies aren’t aware of when embarking on a digital transformation project.

  • Budget 😊
  • Ensuring exec team is along on the journey
  • Lack of understanding of what digital transformation means
  • Finding the right agency to work with and trust
  • Exec team churn.
  • Getting staff buy in early
  • Ongoing costs of systems implementations not considered
  • Silo’d environments
  • Staff can be resistant
  • Defining success criteria
  • Lack of a clear project leader
  • Failing to train!

It was a fantastic event and we really appreciate the open sharing amongst the group!

Aceik – 2021 The Circle Back Initiative Employer

At Aceik, we believe candidate experience is all about being courteous and respectful, and we understand the time and effort that goes into every job application and recruitment process. We are pleased to announce that we are now a 2021 Circle Back Initiative Employer – we commit to respond to every applicant.

The Circle Back Initiative has been created by Talentrich to improve the experience candidates receive after submitting a job application. The initiative is a collection of Employers who commit to guiding standards on candidate communication. Initiative champions agree to respond to every applicant.

What does the candidate experience look like?

Once submitting your resume or responding to a job ad, any job candidate of Aceik can expect:

  • Aceik responds to each job candidate’s appliation with an ‘application received’.
  • Each application will be reviewed by Aceik and a shortlist of suitable candidates will be compiled and discussed internally.
  • If selection criteria is met, a candidate will receive a phone call to run through their application and experience in a little more detail.
  • Candidates not suitable for the role are advised as early in the process as possible.
  • Aceik aims to shortlist a role within 2 week of posting a vacancy.
  • A selected number of candidates are chosen to be invited to interview.
  • Interviews are conducted via video chat (presently).
  • If a suitable candidate is not identified during the interview stage, the shortlist may be revisited. Due to this, candidates on the shortlist may not be notified if they did not make the first round of interviews.
  • If necessary, second round of interviews take place.
  • Any testing or assessment takes place with preferred candidate/s.
  • Once a suitable candidate has been identified, reference checks are conducted and for some roles, Aceik also requires a police check.
  • Once the above assessments come back as successful, Aceik offers the preferred candidate the position.
  • Aceik responds to all candidates that have applied for the position, and provides feedback where possible.

Want to join the Aceik team?

Are you a digital enthusiast looking to work with a team that pushes the boundaries of technology? Email careers@aceik.com.au to tell us what you could bring to the Aceik crew or check out our available roles.

Six Aceik Team Members Named Sitecore Most Valuable Professional

Aceik today announced that an unprecedented six of its team members have been named a 2021 Most Valuable Professional (MVP) by Sitecore®, the global leader in digital experience management software. Our leader and team members, Jason Horne, Thomas Tyack, David (Danny) Newman, Jitendra Soni, David Goosem and Praveen Manchana are being honored among only 24 MVPs across Australia in the program’s 15th year.

Recognising professionals who deliver outstanding customer experiences through shared expertise on Sitecore’s products, the 2021 MVP program draws from a community of 12,000 certified developers and over 20,000 active participants. This year’s worldwide pool of 284 MVPs contributed invaluable knowledge to the community in 2020 and demonstrated true mastery of the Sitecore platform to support partners, customers and prospects.

“It’s an honour for one individual to be recognised for their community contribution, but to know we have six MVPs on our team is outstanding. This MVP designation recognises the unique skills, expertise and success that Tom, Danny, Jitendra, David and Praveen, alongside their colleagues brings to our customers’ digital experience every day,” said Jason Horne, CEO, Aceik.

About the Sitecore MVPs on the Aceik team

Jason Horne, CEO

From Jason’s initial experience of working with Sitecore 5.3 all the way back in 2008, he set out to become a Sitecore Specialist.

In 2014, Jason launched Aceik, a Sitecore specialist consultancy. And he followed this up with the launch of the Sitecore Melbourne Meetup community. His aim has been to provide an environment in which the Aceik team has the skills, tools, relationships, clients, and freedom to deliver the highest level of quality solutions in the Sitecore space.

Thomas Tyack, Chief Technical Architect

Thomas has been working with Sitecore since early 2009 and excitingly for Aceik, this is his third consecutive year as a Sitecore MVP-Technology.

Tom has his hand in many Sitecore pies including regular updates to the Sitecore Speedy module, sharing Sitecore hints through his blog and at meetups and creating a 6 Pillars of Page Speed video series (to name just a few of his contributions in the past 12 months). He also co-founded the AU Sitecore Slack workspace, a forum for Australian based developers to keep in touch.

David (Danny) Newman, Training Manager

Danny spent 8 years at Sitecore teaching developers, marketers and authors to create outstanding digital customer experiences using the Sitecore platform.

In 2019, Danny brought those skills to Aceik where he combined his Sitecore knowledge with Aceik’s practical experience to deliver a balanced Sitecore training program. Danny now provides complimentary training webinars to the Sitecore community.

Jitendra Soni, Sitecore Tech Lead

Jitendra’s very first Sitecore project was a jewellery channel in the UK all the way back in 2013. Since then, he’s delivered many Sitecore projects, including Mondelez International, Invista Group, Dentos Global USA, Manchester United, Bunnings, Bridgestone and RACQ.

Jitendra is an avid blogger on all things Sitecore.

David Goosem, Solution Architect

David has more than 10 years’ experience working both client-side and within agencies as a Sitecore developer, a role in which he delivered exceptional Sitecore websites and customer journeys. His first implementation was on Sitecore 6.4, when he became hooked on the platform’s potential and he has since worked on projects for RACQ, QSuper, RTA, ForceNet, Motorama, Endeavour Foundation and RSL Art Union.

Aside from contributing to SUGCON, David is an avid blogger on all things Sitecore as well as an active member of the Brisbane Sitecore community.

Praveen Manchana, Solution Architect

Praveen started working with Sitecore five years ago, and his first project focused on ecommerce. He considers himself privileged to spend time at Bunnings working on their Homebase project, including Click & Collect. From there, he worked with a couple of different Sitecore partners on other ecommerce projects, including Baby Bunting and Bridgestone.

Praveen has contributed many modules to the Sitecore open source community including Commerce Automation, Promotions Search on 9.2 and Sitecore Commerce 10 with SXA Storefront in Docker for Development.

When he’s not implementing or building on Sitecore, you can find him presenting at local Meetups and webinars.

“The 2021 Sitecore MVPs consist of stellar individuals who demonstrated incredible commitment to the Sitecore community during a challenging year which didn’t allow for in-person engagement,” said Tom De Ridder, CTO of Sitecore. “The 284 MVPs stepped up to the plate to bring critical knowledge and insights for the greater community through virtual channels. We are especially pleased to celebrate this group in the program’s 15th year.”

In recent months, Sitecore recognised Aceik’s success and expertise by naming the organization a Platinum partner, the highest-ranking tier of partner status in the Sitecore network and rewarded Aceik a Sitecore Experience Award Honorable Mention for its work with RAA.

More information can be found about the MVP Program on the Sitecore MVP site: http://mvp.sitecore.com.

People of Aceik: Praveen Manchana, Architect

Last year, we launched a new series to introduce you to our talented and hard working team mates. They’re behind the success of our client’s projects – working diligently to ensure we exceed our customers’ expectations.

This month, we sat down with our Architect and ecommerce expert, Praveen Manchana.



Praveen, tell us a bit about yourself.

Praveen: In terms of my background, I have been working with Microsoft Technologies for close to fifteen years now. I started as a junior developer at Dodo and from there I worked in a variety of roles across different technologies for roughly 9 years before moving onto Sitecore.

I started working with Sitecore five years ago, and my first project focused on ecommerce. I was privileged to spend time at Bunnings working on their Homebase project, including Click & Collect. From there, I worked with a couple of different Sitecore partners on other ecommerce projects, including Baby Bunting and Bridgestone.

After Bunnings, I joined another Sitecore partner for a time, where I worked on the Baby Bunting project. Again, this had a Sitecore commerce focus.

And eventually I landed at Aceik. I’ve been here a little over a year now.

You’ve spent a lot of time working on commerce projects. What do you love about it? Why the focus on Sitecore commerce?

Praveen: I have been with working with Microsoft technologies for fifteen years and to customize or add changes is a lot easier. It is a technology that I am really familiar with and it is easy to get into and learn about it. Extensibility is really good. You can achieve those customizations a lot easier, faster and cheaper using Sitecore commerce than other technologies.

Tell us about why did you decide to join Aceik.

Praveen: At the time I joined Aceik, it was really small. I wanted to be part of that growth journey. I wanted the opportunity to invest my time and energy into growing Aceik.

What are you working on at the moment?

Praveen: I’ve spent the last 9 or so months working on RACQ – trying to stabilise the environment and also working on compliance changes. Excitingly, I’m now getting involved in their rebuild project including shifting to the latest version of Sitecore.

I have seen your “deploying Sitecore on Kubernetes” blog posts and obviously, a meetup group covered the same topic not long ago. Why are you interested in that particular aspect of Sitecore?

Praveen: Sitecore had never supported containers for production use in the past. With the recent launch of Sitecore 10, they officially started supporting containers. If you run into problems and if you raise a support ticket, Sitecore will help us now. With Sitecore moving towards containers and Kubernetes, if we did not move along, we will be left behind.

Tell us about yourself outside of Aceik hours.

Praveen: Most of my time outside of work is catching up with family and friends. I love my barbecues by the way. I probably go through like two or three gas bottles every summer.

I found this really nice Middle Eastern recipe for chicken kebabs. I love it. All my friends and family, they love that as well. So, every time I am doing a barbecue they go, “Okay, make sure you do that.”

If someone wants to develop a career and follow in a similar set of footsteps as yourself, what advice or tips would you have for them?

Praveen: Set goals clearly and early. At the beginning of my career, I did not set my goals properly. I did not know what I wanted to do and I was not clear, but I think it is often the case with most of the developers. At the start of your career, you feel confused. You do not know what you want to get into. You do not know what your passion is. But as you work through a few years into your career, you will understand where your interest lies and you have to make sure that you steer in that direction. I definitely did that. I like technical things and I always made sure throughout my career when went into different roles they are all tech focused. I went into a tech lead role, but even then, I was hands on and never moved away from coding because I like it. If I was not coding, I would probably get bored.

Sitecore 10 Content Serialization and best practices – Part 3

SCS is pretty new, and there are a few basic recommendations while doing the first setup, In this blog, we will discuss those settings and options.

This blog has split into three parts, and this is part 3.

  1. Configure the relative serialization path correctly. In Microsoft NTFS the maximum length is 240. In SCS the content serialization path size limit is defined in the settings, by default, the value is 100.
{
  "$schema": "./.sitecore/schemas/RootConfigurationFile.schema.json",
  "modules": [
    "src/*/*/*.module.json"
  ],
  "serialization": {
    "defaultMaxRelativeItemPathLength": 100,
    "defaultModuleRelativeSerializationPath": "items"
  }
}

The maximum relative item path length = the file system maximum path and file name length – (the base path length + the serialization path length). for more details, please follow this link – Configure the maximum relative item path length

2. Define the hash and alias for relative serialization path – Hashing to shorten paths and aliases and to make it human readable.

It’s super important for two purposes. One is to mitigate the risk of serialization path, and second is define the structure of the project like we can define common aliases for the site.

Relative path is combination of four section (Base path + serialization path +include path content item path) , for example

C:\Users\jsoni\Sitecore\Project\src\Sites\ +  serialization\ + content\ + Home\Products\P1\test.yml

define the alias

"rules": [
  {
    "path": "/Home/Products/P1/test",
    "alias": "alpath"
  }
]

3. Sequence is most important while defining the module.json – As a rule of thumb with Sitecore, all the dependencies should be defined first, for example before defining the content we have to define the templates, layout and rendering etc.

for example

{
  "namespace": "Feature.Hero",
  "items": {
    "includes": [
      {
        "name": "templates",
        "path": "/sitecore/templates/Feature/Hero",
        "allowedPushOperations": "createUpdateAndDelete",
        "scope": "itemAndDescendants"
      },
      {
        "name": "layouts",

        "path": "/sitecore/layout/Renderings/Feature/Hero",
        "allowedPushOperations": "createUpdateAndDelete",
        "scope": "itemAndDescendants"
      }
    ]
  }
}

4. Don’t forget first-match-wins principle while defining the IA or base principle of the content sync strategy – this rule says when a content item matches a rule, all subsequent rules are ignored:

As per the Sitecore recommendation, we need Keep the following things in mind when we configure rules:

  • No path overlapping, If you follow the Helix principles I’m sure it will be much easier, otherwise it can be very hard to identify any path overlaps.
  • Again, Parent rules will override the child rule, example if you have mentioned a rule on parent item node, It will override any child rule configuration.
  • Rule scopes cannot be more inclusive than the root scope. For example, if the root scope is ItemAndChildren, the rule scope cannot be ItemAndDescendants.
  • The alias property in a rule replaces the root name property (the folder name in your file system) for this particular rule.
  • If you have configured an alias property and a scope property with an ignored value, the scope is used. Content items scoped to be ignored are not influenced by aliases.

For more details, please follow below links

I hope this blog will help you to think of a few fundamental considerations while starting to work with SCS on Sitecore.

Sitecore 10 Content Serialization and best practices – Part 2

Unicorn was the most popular plugin for content serialization. It was very straightforward and well managed; all the documents were very descriptive and easy to understand. Now we have Sitecore Content Serialization (SCS), I think we must understand what has changed. Are we losing or gaining any functionality? what changes are required to our existing setup? Re there any changes in terminology etc?

This blog has been split into three parts, and this is part two.

Below is the high-level comparison between Unicorn and SCS.

  1. SCS has an additional Visual Studio plugin to manage Content.

VS plugin provides the below options –

1. Option to push and pull changes
2. Differences between disk and database content
3. Option for selected item sync

SCS has Sitecore command line (CLI) Interface and Unicorn has it’s own page.

SCS configuration is based on JSON files and Unicorn configuration is based on XML.

The configuration file naming convention is different. The SCS configuration file names contain modules for identification and Unicorn configuration contains serialization – Although this is configurable.

The initial setup is different. For SCS we have to setup the package and to enable the CLI it’s required to install the packages.

Difference in global/shared configuration

Difference in project level configuration.

Difference in feature/module level configuration.

SCS provides more flexibility for rule based configuration, for each feature we can define a rule and each rule has the option to define the path, scope and allowed PushOperations etc.

There are changes in the configuration.

When using Unicorn we used to define the dependencies and extends options

<configuration name="Feature.Demo" description="Feature Demo" dependencies="Foundation.*" extends="Helix.Feature">

With SCS, we need to handle it while defining the feature itself and any overlap, for example if there is any specific overlap we need to make sure to put the most specific rule first.

Rule of Parent’s path override rule of children’s and dependent path.

Overall, I can see the SCS configuration is much easier and more flexible. However, I’m still looking for an option for pattern-based formats in SCS.

I hope this comparison will provide a basis to understand the difference between Unicorn and SCS.

Sitecore 10 Content Serialization and best practices – Part 1

Sitecore has introduced Sitecore Content Serialization (SCS) as part of version 10. In this blog, I will explain the basic concept of serialization and compare all Unicorn features, followed by steps for the basic setup and best practices.

This blog has split into three parts, and this is part 1.

Part 1 – Sitecore 10 SCS- Basic concept

Let’s first try to understand the definition, Serialization is the process of translating a data structure or object state into a format that can be stored (for example, in a file or memory data buffer) or transmitted (for example, across a computer network) and reconstructed later (possibly in a different computer environment) – Wikipedia

Sitecore Content Serialization (SCS) is a system for serializing, sharing, and deploying content items, as well as keeping them in version control – Sitecore

Now, we know the definition of serialization. I remember with the Sitecore 6.X Serialization guide we had an option to serialize the item tree and restore it, there were additional options to configure the serialization based on the events like item saved, created, deleted etc. and we were using SVN to store those serialized files.

Growing of TDS (Team Development for Sitecore) foundation

TDS was beneficial to manage the project and item files. I used TDS a lot with Sitecore 6.X versions. We were also using this as part of the deployment process as the underlying TDS was using the MSBuild project file to group the Sitecore items into a deployable project. Additionally to that, it has the below features which are not part of SCS.

  • File deployment into a local Sitecore instance
  • Web Deployment Package (WDP) generation
  • Code generation
  • Validators
  • Environment Validation

Note – Paid license is required for TDS and the cost was around USD 400

In my opinion it’s the end of the TDS era.

Growing of Unicorn (/unicorn.aspx)

Unicorn is a Sitecore utility and it is open source. It solves the issue of moving templates, renderings, and other database items between Sitecore instances. TDS is a monolithic product with commercial support, and marketing does a lot more than just serialization. Unicorn is relatively simple, free and open-source, and does one thing well.

I prefer using Unicorn instead of TDS. Generating the TDS code was not that easy and always needed to take care of the partial class, unnecessary field generation, etc. We can set up the template class following the helix principals.

For more details about the setup, Here is my blog post – Sitecore – Unicorn setup, patterns and tips.

In my opinion Sitecore content serialization would be a replacement of Unicorn.

Sitecore Content Serialization – Future with Sitecore 10 and current focus

SCS will do the out-of-the-box item serialization that lets you automate the synchronization of item changes. It has two options one is using the command-line interface (CLI) and the second Sitecore for Visual Studio (SVS)

Note – for using SVS it’s required to get the license and TDS and SVS are both offered under the same license.

Basic Settings and configurations

Out of the box there are three options to serialize content, The default serialization format (.Item)

  • Manually serialize, update, and revert items in the Content Editor.
  • Use Sitecore event handlers to automatically serialize items.
  • Use the Sitecore service page to serialize, update, and revert a whole database.

Item format

YAML format – using Unicorn and Sitecore content serialization.

This article is the first part to explain the basics of serialization, in the next Part 2- Compare SCS with Unicorn, I will explain the difference between Unicorn vs SCS setup.

I hope this article will help you to understand the basic concept of serialization.

Sitecore Power with ASP.NET Core and why it’s important.

Sitecore has recently introduced a development SDK with ASP.NET Core. In this blog, I will explain why it’s super important for the Business to start thinking about it and how it will change the way of Sitecore development.

In my view, technology is an essential part of running a successful business, and it keeps changing for a better purpose. It’s tough for the Business to make the right decision to choose the right technology and plan for the investment as there are a lot of factors involved like cost, technology choice, stability, future, support, extension, security, machine learning, AI, robotics etc.

Off Couse, every Business would prefer to make a one-time investment and to reuse that investment to cater to any new technology.

Is it possible today to make a one-time investment? I think it’s not, but a company like Microsoft and Sitecore they have been putting all efforts to make it happen and the release of Sitecore with ASP.NET core SDK is a big step towards that dream. In my opinion, The secret of success is to make the right choice at the right time, and don’t devote all energy in fixing the old guys.

Before getting into more details, Let’s understand the key part of the puzzle..

Why Sitecore with ASP.NET Core is so important?

Microsoft has started moving all the focus from the previous development framework (.NET Framework) to .NET Core, Why?, Okay, because .NET Framework 4.8, which was announced on 18th April 2019 will be the last major version of .NET Framework. The visual studio which is the primary IDE for the most of the development is itself is built-in .NET Framework, Although Microsoft will continue to provide the support, as I said in my first few lines, It’s a matter of making the right decision at the right time. below are some key features and needs for the changes.

  • Cross-platform & container support
  • High performance
  • Asynchronous via async/await
  • Unified MVC & Web API frameworks
  • Multiple environments and development mode
  • Dependency Injection
  • WebSockets & SignalR and  Cross-Site Request Forgery (CSRF) Protection
  • “Self hosted” Web Applications
  • Globalization and Localization
  • Swagger OpenAPI built in

SitecoreASP.NET Core rendering SDK enables SItecore headless development with ASP.NET core. This rendering SDK is in addition to the already existing Javascript Service rendering SDKs of React, Angular, Vue and JavaScript libraries. below is the flow diagram and it makes Sitecore solutions faster and easier to develop, maintain, scale, and upgrade by splitting them up into a Sitecore backend and a ASP.NET rendering host frontend. And we can build rendering hosts with the Sitecore ASP.NET Rendering SDK. That’s a fantastic option. here is a high level flow diagram.

Microsoft has already planned roadmap until 2023 releases, so this shows how important it’s that Sitecore goes with the .Net Core platform.

Source – https://dotnet.microsoft.com/platform/support/policy/dotnet-core

The most important part is, there are a lot of front end technology like Angular, React, Vue.jS, Flutter, Microsoft has launched the new platform called Blazor which will allow C# developer (Sitecore technology) stack to write the web interactive UI through the same language, WOW that’s really amazing, Microsoft has already unified the infrastructure with Azure Cloud provider, development technology with .Net Standard and front end technology through Blazor, so now to develop any complex code that includes Azure, backed like Machine learning , AU and front end all can be done through the same technology and Sitecore has release official SDK for that, so that’s the reason is very important for the business as well as for the development.

Let’s talk about the development and architecture

There are two main parts, One is rendering host front end and second is Sitecore instance backend.

  • Rendering Host – The rendering host front end is a web app made up of the Sitecore ASP.NET Rendering SDK code and static resources. The job of the rendering host is to respond to visitor requests.
  • The Sitecore instance– exposes a set of endpoints like web based native rendering hosts or third party integration
Source – https://doc.sitecore.com/developers/100/developer-tools/en/sitecore-headless-development.html

1. Setting up the sample project-

Below are the prerequisites for the installation.

Follow these steps in case of any error, Please see the reference in Troubleshooting section in the below page.

Below are simple command to setup the local environment.

dotnet new -i Sitecore.DevEx.Templates --nuget-source https://sitecore.myget.org/F/sc-packages/api/v3/index.json (Install template)

dotnet new sitecore.aspnet.gettingstarted -n MyProject (Create a new project)

.\init.ps1 -InitEnv -LicenseXmlPath "<path to your license.xml file>" -AdminPassword "<your Sitecore administrator password>“  (Prepare the container)

.\up.ps1 – (Download the Sitecore Docker images and install the containers)
Docker-compose up –d and Docker ps -a

Once you follow above steps, You should be able to see the working Sitecore instance running inside docker with ASP.NET core.

2. Below are the steps to setup the JSON rendering.

Setup the template in the project and add the standard value, As example below, Ref – https://doc.sitecore.com/developers/100/developer-tools/en/walkthrough–creating-a-simple-rendering-with-a-data-source.html

Add JSON rendering and placeholder settings As mention below.

Add a new component in the solution, A new model, View and register it.

Verify Traefik

  1. Reverse proxy
  2. Traefik provides the friendly URL for each of the instances.
  3. Low configuration setup.
  4. SSL termination

Benefit of using ASP.NET core with Sitecore.

  • Super fast.
  • Fully integrated with Visual Studio.
  • Sitecore headless development is based on ASP.NET Core, there are also fewer problems when doing the native integration

Below features are not supported.

  • Horizon
  • Edit frames
  • Sitecore Forms
  • Invocation of xConnect events, goals and outcomes from c#
  • Managed Cloud Standard and Managed Cloud Premium do not currently offer headless topologies for rendering hosts.

Helper

Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass

Troubleshooting

  • First issue while the setup was ‘Invoke-WebRequest’ is not recognized as an internal or external command

Root cause analysis and Solution.

Need to update the default shell to PowerShell for dotnetsdk –

C:\Projects\RenderingSDK\MyProject\docker\build\dotnetsdk\Dockerfile

SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"]
  • C:\Program Files\dotnet\sdk\5.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets(241,5): error NETSDK1005: Assets file ‘C:\build\src\rendering\obj\project.assets.json’ doesn’t have a target for ‘netcoreapp3.1’. Ensure that restore has run and that you have included ‘netcoreapp3.1’ in the TargetFrameworks for your project. [C:\build\src\rendering\renderinghost.csproj]

Initially, I thought it’s related to version, As I had installed both dotnetcore SDK 3.1 and 5.0, but finally had to update above command.

Extension – In case if need any extension like xConnect events and to trigger a goals, there are always a way, We can Instantiate client in a non-Sitecore context, Reference Link and can add interaction like to trigger a goal

Finally, A few development tips.

  • How to check the files running inside the containers through the VIsual Studio.
  • Dotnet Sitecore Help command
 dotnet sitecore --help
  • Sitecore login command
  dotnet sitecore login 
  • Push the serialized items command – SCS (Sitecore content serialization)
 dotnet sitecore ser push 
  • SCS (Sitecore content serialization) Publish command
 dotnet sitecore publish

Git link for the ASP.NET core Helix

https://github.com/Sitecore/Helix.Examples/tree/master/examples/helix-basic-aspnetcore

I hope this will help to start the development with ASP.NET core with Sitecore 10

Video reference –

I have also presented in Sitecore User Group Pune – Nov 2020 and explain these details.

Thank you for 2020

Despite everything 2020 threw our way, over at Aceik, we certainly had a lot to celebrate in 2020, including: 

  • PARTNERSHIPS: We partnered with a number of new clients including McGrath, RACQ and the Australian National Maritime Museum on some exciting new Sitecore projects. And we owe a huge thank you to our customers for your support throughout this year. We know it has been incredibly trying and we are grateful that you had our backs. THANK YOU! 
     
  • TEAM GROWTH: Our team and capabilities grew with the addition of 14 incredibly talented individuals including our first Chief Operating Officer/Creative Director, Head of HR and Quality Assurance Lead, to name a few. 
     
  • RECOGNITION: Sitecore promoted Aceik to their top partner tier, Platinum, named two of our team members Sitecore MVPs and awarded us the Sitecore Experience Award Honorable Mention 2020 for our work with RAA
     
  • PRODUCT DEVELOPMENT: Last year we launched our new training practice and in 2020, we added 2 new courses to the program, including Creating and Managing Content in Sitecore 10.x and Marketing Foundations for Sitecore 10.x. We wrote a top ranking blog for deploying Sitecore into Kubernetes as well as improving our existing offering – Sitecore Speedy.

Our 2021 plans are equally exciting and we’d love to share a couple with you:

  • Aceik is planning to expand our creative offering in our endeavour to provide our customers with a genuine end-to-end proposition. 
  • A rebrand is on the horizon.
  • Sustainable growth is based on insuring our customer success record. We are planning to continue to grow our team, to enable our growth and offering to our customers. Stay tuned for opportunities to join our team! (reach out to careers@aceik.com.au if you would like to work for Aceik).
  • It’s also time to diversify the team and so we’re looking to onboard 3 new pups as office mascots (kidding! But were you still reading?).

I know I say this a lot, but I truly mean it when I say, ‘thank you’. Your support has been invaluable and I’m looking forward to continuing our work together in 2021.

Cheers

Jason Horne & Aceik team

Leah Di Paola joins Aceik as Head of Human Resources

We are excited to share that Leah Di Paola, former Group HR Manager for Incitec Pivot Limited. has joined Aceik as our Head of Human Resources.

The appointment highlights Aceik’s desire to introduce more and more brands to the power of Sitecore, to enable them to drive personalised experiences and positive marketing ROI.

Di Paola has more than 15 years experience in human resources, having worked in industries such as Explosives and Fertiliser Manufacturing with Incitec Pivot and Dyno Nobel, Resourcing with Hudson Global, Procurement with the Charted Institute and Sporting Events with the Melbourne Commonwealth Games.

“I’m thrilled to be joining the multi-award winning Aceik, and am looking forward to contributing to the business’ success by empowering our people, enhancing the employee experience, and acquiring talented resources to support our clients and Sitecore relationships,” said Di Paola.

Jason Horne, Chief Executive Officer at Aceik said, “Aceik’s Sitecore knowledge is vast and our agility is unmatched. We keep up with evolving technology and can change direction more easily than larger companies, giving our clients the most innovative Sitecore solutions to their business problems.

Horne continued, “Helping our clients to realise the full potential of Sitecore’s experience platform is at the centre of everything we do. With Leah’s expertise, we’re looking forward to hiring and fostering talented developers, architects and designers to the team that will create stronger long-term relationships with our clients and Sitecore”.