Akumina Developer Documentation

Akumina Developer Documentation

  • API
  • Docs
  • Blog

›Modern

Akumina

  • Quickstart

Yo Akumina

  • Yo Akumina
  • Start with Yeoman
  • React
  • Simple template

Widget Builder

  • Widget Builder Structure
  • Akumina Widget Builder
  • Skipping instances
  • Token replacement for widget properties

Widget Development Quickstart

  • Setting up the Project
  • Configuring .env file
  • Configuring - akumina.sitedployer.config.json file
  • Configuring - akumina.config.json file
  • Extras

Widget Info

  • Akumina Widgets Overview
  • Building a New Widget Instance
  • Widget Views
  • Widget Properties
  • Global vs Local widgets (Widget Scoping)
  • Akumina React Widgets
  • Callbacks
  • RenderChildWidgets
  • Vendor Package List

Virtual Page Builder

  • Akumina Virtual Page Builder
  • Using Virtual Page Layouts
  • Creating a Custom Layout

Stream Card Builder

  • Installation
  • Stream Card Builder
  • Custom Cards
  • Activity Comments Config
  • Akumina Activity Stream PUSH Subscription using PowerAutomate to connect to ServiceNow
  • Akumina Activity Stream PUSH Subscription using PowerAutomate to connect to Dynamic 365

Site Deployer

  • Overview
  • Version 6.0
  • List Attribute Deployments
  • NPM Commands
  • SPA Updates and Deploying to multiple sites

Authoring

  • Content Action Event
  • Publish Validation Integration
  • Field Event Integration
  • CK Editor external plugins

Headless

  • Quickstart
  • Headless Teams support
  • Headless Troubleshooting

Modern

  • Overview
  • FAQ
  • Single Page Application
  • Modern Web Part Library
  • Google Analytics for Modern Pages

Site Creator

  • Overview
  • Adding A Custom Site Definition
  • Core Step Classes
  • Custom Site Definition Components
  • Custom Site Definition XML
  • Custom Subsite Definitions
  • Sample Step Code
  • Supported Tokens

Azure DevOps

  • CI/CD using Azure DevOps
  • Setting up a build to deploy a site package
  • Setting up a build to deploy file to App Manager hosted in an app service

Configuration

  • Configuration Context Overview
  • Edit the Redis cache timeout
  • Using a key vault for the client id and client secret

Debugging

  • Debugging in Akumina

Advanced

  • Central Site Collection Support
  • Eventing OOB Digital Workplace Events
  • Working with custom JSX Views
  • Page Indexing

Service Hub

  • Quickstart

Patch Notes

  • Patch Notes

Overview

Overview

SharePoint Online (SPO) offers two models for building sites: Classic SPO and Modern SPO leveraging the SPFx framework. Presently, there are still significant differences in capability between Classic and Modern – specifically in the arena of brand-ability, customization, third party integration and design output, however, the demand for Modern SPO sites is increasing as some customers want to be able to leverage the ‘latest and greatest’.

Akumina fully supports both models. Akumina version 4.8 supports classic and modern, while version 5.0 supports modern only.

Akumina separates Content from Function and Presentation. This abstracted approach is what allows for:

  • Easy integration with 3rd party systems outside of the Microsoft ecosystem
  • Easy adaption to a different Microsoft page rendering/compiling engine

Modern Pages and SPFx are not about new ways to manage content, they are about new ways to deliver capabilities into a page and bring that page to an audience.

Akumina’s support of both Microsoft page rendering models is not about creating a ‘new Akumina way of doing things’, rather, it is about adapting the Akumina widget technology to be delivered to an end user through either model – with complete feature parity – following Akumina’s ‘use the right tool for the right job’ deployment approach.

Two Experiences

There are two experiences that Akumina Modern supports that determine how pages are authored and how widgets are added.

Akumina Page Experience

In this model, the Akumina Virtual Page Builder is used to construct pages. Visually, the page is like its classic site counterpart, yet only Akumina widgets can be in the pages.

Modern Page Experience

In this model, Akumina widgets are delivered in the page and the Modern editing flow is used. This allows both Akumina widgets and Modern Web Parts to be in the page together.

Single Page Application (SPA)

Layered on top of the SharePoint Modern interface, the Akumina Page Experience utilizes SPA application, that’s Packed full, with design freedom, enhanced performance, and automatic page routing which creates an intuitive experience for page creators.

The enhancements that come with SPA, Virtual pages perform better, pages load faster, and proper custom navigational routing, in turn provide the end user with an experience and performance they can confidently interact with.

See https://akumina.github.io/docs/Modern-SPA

All the Akumina Benefits in a Modern Page

With the ease of adding Akumina into SPFx driven pages also comes many of the benefits as well.

Akumina Widget Targeting and Audience Segmentation are still available as those are functions of the Akumina Widgets and don’t have any dependencies on the page technology (in this case SPFx) in which they are hosted.

As well as the same multi-view and management capability for configuring widget properties and easy access content editing.

← Headless TroubleshootingFAQ →
  • Two Experiences
  • Akumina Page Experience
  • Modern Page Experience
  • Single Page Application (SPA)
  • All the Akumina Benefits in a Modern Page
Akumina Developer Documentation
Docs
Akumina Framework 5.0Akumina Widget BuilderAkumina Yeoman GeneratorSite Deployer
Community
Akumina Community Site
More
GitHubStar
Copyright © 2024 Akumina