LogoLogo
  • Technical Direction
  • Technical overview
    • Technical Implementation
    • API Design Guide
      • Data Definitions and Standards
      • Data Transfer Objects
      • Documentation
      • Environments
      • Error Handling
      • Example API Service
      • GraphQL Naming Conventions
      • Methods
      • Naming Conventions
      • Once Only Principle
      • Pagination
      • Resource Oriented Design
      • REST Request
      • REST Response
      • Security
      • Versioning
    • Ísland.is Public Web Data Flow
    • Code Reviews
    • Code Standards
    • Monorepo
    • Project Management
    • Teamwork
    • Architectural Decision Records
      • Use Markdown Architectural Decision Records
      • Use NX
      • Continuous Integration
      • CSS
      • Branching and Release Strategy
      • Error Tracking and Monitoring
      • What API Management Tool to Consider
      • Viskuausan Static Site Generator
      • Use OAuth 2.0 and OpenID Connect As Protocols for Authentication and Authorization
      • Unified Naming Strategy for Files and Directories
      • CMS
      • Open Source License
      • What Chart Library Should We Use Across Island.is?
      • What Feature Flag Service/application Should We Use at Island.is?
      • Logging, Monitoring and APM Platform
      • ADR Template
    • Log Management Policy
  • Products
    • Island.is Authentication Service
      • Terminology
      • Integration Options
      • Authentication Flows
      • Authorising API Endpoints
      • Session Lifecycle
      • Scopes and Tokens
      • Delegations
      • Configuration
      • Tools and Examples
      • Environments
      • Test IAS with Postman
      • Using the IAS admin portal
    • Notifications / Hnipp
      • New Notification Setup Guide
      • Notifications service workflow overview
      • Email notifications
    • Pósthólfið
      • Security Checklist
      • Introduction
      • Skjalatilkynning API
      • Skjalaveita API
      • Sequence Diagram
      • Interfaces
    • Straumurinn (X-Road)
      • Architecture Guidelines for Service Providers and Consumers
      • Setting up an X-Road Security Server
        • Network Configuration
      • X-Road - Uppfærsla á öryggisþjónum
      • Straumurinn - Notkun og umsýsla
      • X-Road Central - current version
  • Development
    • Getting Started
    • Generating a New Project
    • Definition of done
    • Devops
      • Continuous Delivery
      • Database
      • Dockerizing
      • Environment Setup
      • Logging
      • Metrics
      • NextJS Custom Server
      • Observability
      • Operations Base Principles
      • Security
      • Service Configuration
      • Support
    • AWS Secrets
    • Feature Flags
    • Documentation Contributions
    • Defining Monorepo Boundaries With Tags
    • OpenAPI
    • Code Generation
    • Workspace Settings (Deprecated)
    • External Contributions
  • REFERENCE
    • Problems
      • 400 Validation Failed
      • 400 Attempt Failed
      • 403 Bad Subject
      • 400 500 Template API Error
    • Glossary
  • Misc
    • Guide: Adding a Payment Step to an Application
    • Guide: Enable Organisations to Make Requests to an Application
    • README Template
Powered by GitBook
On this page
  • Context and Problem Statement
  • Decision Drivers
  • Considered Options
  • Decision Outcome
  • Pros and Cons of the Options
  • Docusaurus v2
  • Gatsby
  • NextJS + NestJS
  • Other honorable mentions

Was this helpful?

  1. Technical overview
  2. Architectural Decision Records

Viskuausan Static Site Generator

  • Status: accepted

  • Deciders: devs

  • Date: 2020-09-07

We're going to create a web app for Viskuausan (API Catalog). Viskuausan consists of three main components:

  • Web service catalogue

    • Displays an overview of web services.

    • Displays details about each web service.

  • Data definition catalogue

    • Displays an overview of data definitions

    • Displays details about each data definition

  • Design guidelines

    • Static text content describing best practices for API development

The two catalogue components require:

  • Data storage

  • API communication

  • API GW and X-Road integration

  • Other custom implementations

The design guidelines component require:

  • Static content written in markdown

Context and Problem Statement

Viskuausan is proving to be more complex and larger platform than just a simple documentation site from static content. Which React framework provides the most out-of-the-box features that we need?

Decision Drivers

  • Should be able to support markdown content rendered to HTML

  • Should be open source

  • Should be customizable to island.is UI design

Considered Options

  • NextJS + NestJS

Decision Outcome

Chosen option: NextJS + NestJS

NestJS is used to create backend services and Viskuausan needs few backend services related to the X-Road and API GW integrations. Provides functionalities like ORM, dependency injection, unit testing.

Pros and Cons of the Options

All of the considered options are built using React, are open source and popular site generators.

Docusaurus v2

  • Good, because it focuses on documentation

  • Good, because it supports TypeScript

  • Good, because it is extendable via plugins & themes

  • Good, because it is ready for translations

  • Good, because it supports document versioning

  • Good, because it has content search out-of-the-box

  • Bad, because it is still in beta

  • Bad, because it requires manual setup for typescript compile-time type checking

  • Bad, because it needs manual setup for ORM, dependency injection, testing and more.

  • Bad, because it is not suitable for larger websites which needs more backend

    api functionality.

Gatsby

  • Good, because it has rich ecosystem of plugins

  • Good, because it supports TypeScript

  • Good, because it is really flexible

  • Good, because it has GraphQL support for external data

  • Bad, because it has high project complexity

  • Bad, because it has high learning curve

  • Bad, because it requires manual setup for TypeScript compile time type checking

NextJS + NestJS

  • Good, because it is flexible

  • Good, because it supports TypeScript

  • Good, because it is already in use in the monorepo

    • Will make it easier to move into the island.is web

  • Good, because it is easy to use islandis-ui components

  • Bad, because it requires customization to render markdown

Other honorable mentions

  • Built using Gatsby so we would rather go with Gatsby than Docz so

    unnecessary to list as an option

PreviousWhat API Management Tool to ConsiderNextUse OAuth 2.0 and OpenID Connect As Protocols for Authentication and Authorization

Last updated 2 years ago

Was this helpful?

Should use NodeJS and React as outlined in

NextJS is the chosen web framework for all island.is websites needing server side rendering. As Viskuausan will probably be merged with island.is main website, creating it using same frameworks makes it easy to merge later on. It is easier to reuse Island UI components using NextJS over Docusaurus. Docusaurus main advantage over Next is out-of-the-box markdown support but it is easy to add markdown support in NextJS using library.

Is relatively easy using

SÍ technical direction
Docusaurus v2
GatsbyJS
Remark
Remark
Docz