Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Unwrap the Angular Routing

Open
  • Is something wrong?
#92 0 comments 0 reactions 0 assignees View on GitHub

@copilot-swe-agent is already working on this.

Since Aug 19, 2025.

  • #89 by @copilot-swe-agent — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, jekyll
Domain
frontend, web-dev

Research direction

Start by reading app.js and the static-page routes it defines, then review the linked pull request (#89) and the Jekyll front-matter documentation. Done means every static page routed there has an equivalent directory or public HTML page with front matter and the old routing overhead is removed.

Written by the indexing model from the issue text.

Description

This is in relation to app.js, which sets the routing for the app.

Most of this file can go away and be replaced with YAML and Jekyll Front Matter syntax on the HTML page. For example https://rerum.io/#/about is routed like this in app.js

var rerum = angular.module('rerum', ['ui.bootstrap', 'ngRoute', 'ngAnimate','ngSanitize', 'angular-loading-bar', 'cfp.hotkeys', 'utils']);
rerum.config(['$routeProvider', '$locationProvider',
    function ($routeProvider, $locationProvider) {
        ...
        .when('/about', {
               templateUrl: 'app/about/about.html'
         })
   }])

That is a fair amount of overhead for a static community site. Instead, all that is needed is an /about directory or a /public/about.html file with some YAML at the top.

---
title: About Page
permalink: /about
---

Do this for all static pages that are routed to by this app.js file.

Dominant language
JavaScript
Stars
11
Forks
5
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CenterForDigitalHumanities/rerum

All issues in CenterForDigitalHumanities/rerum

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.