Slack link which is available on janus-idp.io is an expired link.

Describe the bug

The JFrog plugin tile has a description from Quay, when it should be for JFrog.

https://janus-idp.io/plugins

Hi team! Can we enable an RSS feed for the blog? I hypothesize that's how some folks (like me!) are notified when new articles are published. Thanks!

Goal

Provide a cookie banner to be GDBR compliant

Description

Provide a GPTs Details page for each of the GPTs in the GPT Home page to the Janus community site to provide the details of the Sample GPTs when the corresponding GPT Card is clicked.

Acceptance Criteria

The GPT Details Page should include the following:

• Header
• Title
• Description
• GitHub link, rather than NPM (linking to the GitHub URL of the Software Template, ex: https://github.com/janus-idp/software-templates/tree/main/scaffolder-templates/ansible-job)
• GPT README content (Pulled in from the GitHub, ex https://github.com/janus-idp/software-templates/blob/main/scaffolder-templates/ansible-job/README.md)

Blocker

The following issue(s) will need to be completed before this issue can be started:

• janus-idp/software-templates#137
  This issue needs to be complete for the following templates (for the sake of this issue, the README files just need to exist and not be empty)
  • Ansible Job Template
  • Quarkus Web Template
  • TechDocs Template
• #153

Goal

Post a blog on janus-idp.io which provides guidance on how a Platform Engineer can create their first Hello World golden path template

Run prettier:check in CI action

The invite links from the top nav and footer are not working. Also the footer links are not opening to a new page like the ones in the top nav.

Goal

Post a blog on janus-idp.io introducing our new Janus Showcase Application!

Goal

Post a blog on janus-idp.io which provides guidance on how a Platform Engineer can create their first Backstage frontend plugin

Changes

• Add root level start script
• Add root level tsc script

Goal

Post a blog on janus-idp.io regarding our Backstage build being available on Quay!

Link:
https://www.youtube.com/@januscommunity

The YT channel should be mentioned in the community page and also in the footer
https://janus-idp.io/community

Typo on
https://github.com/janus-idp/janus-idp.github.io/blob/main/apps/landing-page/pages/blog/exploring-quay-registry-in-backstage.mdx?plain=1#L84

- import { QuayPage, isQuayAvailable } from '@fmenesesg/backstage-plugin-quay';
+ import { QuayPage, isQuayAvailable } from '@janus-idp/backstage-plugin-quay';

Goal

Post a blog on janus-idp.io describing how to fork showcase and deploy it to cluster with BuildConfig

Goal

Post a blog on janus-idp.io introducing our new Topology plugin!

Changes

• Allow the plugin button text to wrap
• Change the key features to be a carousel

Image

What needs to be done?

Add github issue templates in janus-idp.github.io using the default templates in the janus-idp organization.

Goal

The Goal of this epic is to provide a Golden Path Templates (GPTs) page to the Janus community site to provide discovery of the details of the Sample GPTs which we have available.

Enhancement

We can take inspiration from the [Plugins page[(https://janus-idp.io/plugins/) with the following changes:

GPTs Page

Header

• Sample GPTs
• Have a GPT idea?
• Button -> Submit a proposal for a GPT!

The CTA should reference a new Issue template for this repo similar to this plugin issue template

Search

Include a search field, but do not provide the filter dropdown as the Plugins page has

GPT Cards

Each card should contain

• Title
• Description

GPT Detail Page

Header

• Title
• Description
• GitHub link, rather than NPM (linking to the GH URL of the Software Template, ex https://github.com/janus-idp/software-templates/tree/main/scaffolder-templates/ansible-job)
• Pull in the README (ex https://github.com/janus-idp/software-templates/blob/main/scaffolder-templates/ansible-job/README.md)

Notes

GPTsList should include:

• Title
• Description
• href
• githubUrl

As a starter, include the following in the GPTs page:

• https://github.com/janus-idp/software-templates/tree/main/scaffolder-templates/ansible-job
• https://github.com/janus-idp/software-templates/tree/main/scaffolder-templates/quarkus-web-template
• https://github.com/janus-idp/software-templates/tree/main/scaffolder-templates/documentation-template

Be sure to add README.md to the above scaffolder-templates directories if they don't exist

Issues in Epic

• - janus-idp/software-templates#136
• - janus-idp/software-templates#137
• - janus-idp/software-templates#140
• - #153
• - #154

Goal

Post a blog on janus-idp.io describing caveats of helm upgrade with PostgreSQL enabled.

Links

• Community Footer Section Config
• Mailing list: https://groups.google.com/g/janus-idp-community
• Google Calendar: https://calendar.google.com/calendar/u/0?cid=amFudXMuaWRwLmNvbW11bml0eUBnbWFpbC5jb20

Goal

Post a blog on janus-idp.io providing in an in depth overview for the Backstage Topology plugin covering installation/configuration/features.

Background

Currently the plugin page displays all plugins regardless of the plugin role specified in its package.json. e.g. 3scale-backend

Enhancement

• Instead of using the role property, add a tags property in the plugin's package.json. This is because the role property is not easily understandable i.e. a custom action has a role of backend-plugin-module
• Create a tag filtering mechanism based on the plugin role
• Create a search bar based on the plugin name and tags

Goal

Post a blog on janus-idp.io on how to use the helm chart to propagate app config changes to your instance.

A follow-up to the #75

Essential for community members to know where to get started and how to set up the Janus Showcase locally.
Could be enhanced with explanation of the individual plugins and how they are architected.

Goal

Post a blog on janus-idp.io introducing our new Quay plugin!

Goal

Post a blog on janus-idp.io describing how to deploy backstage simply and easily via Janus Helm chart.

We want to add the Janus custom actions to the Backstage.io custom action page

Describe the bug

The Content in the Azure Container Registry (ACR) page is the documentation for the OpenShift Image Registry plugin.

The NPM link for the ACR page also incorrectly links to the Openshift Image Registry plugin's package.

Expected Behavior

The page contents and NPM link should point to the ACR documentation and npm registry.

Changes

Remove unnecessary dependencies

• check-dependency-version-consistency- No longer needed since we have the renovate bot

The Slack link in the community page has been updated but not the one in the header and the one in the footer.

We can use this link https://janus-idp.slack.com/archives/C04EDTPJRK5 instead. We don't need to use an invitation link and it will never expire.

Originally posted by @tumido in #33 (comment)

/assign @schwesig

Idea:

• create golden path per persona and area
• stepping stones are the days in the matrix (rows are the deployment/ developing tiles)
• each stepping stone will be at least one blog entry
• each golden path blog links to the different blog entries in the right order, maybe with an intro/ tl;dr; and a connecting text part
  • therefore now blog is redundant

What needs to be done

Add blank issue templates to janus-idp.github.io with the status/triage label

Enhancement

Add category labels to plugins like Backstage

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• fix(deps): update all non-major dependencies (@docusaurus/core, @docusaurus/module-type-aliases, @docusaurus/plugin-google-gtag, @docusaurus/preset-classic, @docusaurus/theme-classic, @docusaurus/tsconfig, @docusaurus/types, @heroicons/react, @segment/analytics-next, @types/node, @types/react, @types/react-dom, autoprefixer, axios, clsx, framer-motion, lint-staged, node, pnpm, postcss, prettier-plugin-tailwindcss, react, react-cookie, react-dom, react-icons, tailwindcss, turbo, typescript)
• fix(deps): update linters (@typescript-eslint/eslint-plugin, @typescript-eslint/parser, eslint, eslint-config-turbo, eslint-plugin-license-header, eslint-plugin-react, eslint-plugin-react-hooks, prettier)
• chore(deps): update dependency husky to v9
• chore(deps): update pnpm to v9
• fix(deps): update linters (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser, eslint, eslint-config-airbnb-typescript, eslint-plugin-unicorn)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Add git hooks from janus-idp/backstage-showcase. Make sure the execute permission is set.

• post-checkout
• post-merge
• post-rewrite

Description

Provide a GPTs Home page to the Janus community site to provide discovery of the details of a list of Sample GPTs which we have available.

Acceptance Criteria

The homepage should include the following:

• Header containing:
  • Sample GPTs
  • Have a GPT idea?
  • Button -> Submit a proposal for a GPT!

The CTA should reference a new Issue template for the software templates repo similar to this plugin issue template

• Search

  • Include a search field, but do not provide the filter dropdown as the Plugins page has

• GPT Cards

  • Each card should contain:
    • Title
    • Description

Notes

• GPTsList should include:
  • Title
  • Description
  • href
  • githubUrl

As a starter, include the following in the GPTs Home page:

https://github.com/janus-idp/software-templates/tree/main/scaffolder-templates/ansible-job
https://github.com/janus-idp/software-templates/tree/main/scaffolder-templates/quarkus-web-template
https://github.com/janus-idp/software-templates/tree/main/scaffolder-templates/documentation-template

Blocker

The following issue(s) will need to be completed before this issue can be started:

• janus-idp/software-templates#136

Update the script to use pnpm install

Goal

Post a blog on janus-idp.io which provides guidance on how a Platform Engineer can create their first Backstage backend plugin

Goal

Post a blog on janus-idp.io describing the new UX with the multi-cluster plugin

Update remote content regex to include relative non image files. The website will no longer build without a fix.

Discussed with @christophe-f

Goal

Post a blog on janus-idp.io introducing our new 3scale plugin!

Provided by Francisco: https://docs.google.com/document/d/199OeA870f5Sy1FAcrjw8md22AANE3jomTzBE9K74fL0/edit#heading=h.qsl7qdn61pbl

The links don't appear to be working on the Keyclock ToC, and the "For Users" link gives a plugin not found page.

Describe the bug

When trying to create a commit, the following error occurs:

> [email protected] lint-staged
> lint-staged

✔ Preparing lint-staged...
⚠ Running tasks for staged files...
  ❯ package.json — 1 file
    ❯ * — 1 file
      ✖ turbo run prettier:fix -- [KILLED]
    ❯ *.{js,jsx,ts,tsx,mjs,cjs} — 1 file
      ✖ turbo run lint:fix -- [FAILED]
↓ Skipped because of errors from tasks.
✔ Reverting to original state because of errors...
✔ Cleaning up temporary files...

✖ turbo run lint:fix --:
 ERROR  run failed: error preparing engine: Could not find the following tasks in project: lint:fix
Turbo error: error preparing engine: Could not find the following tasks in project: lint:fix

✖ turbo run prettier:fix --:
• Packages in scope: //, docusaurus-plugin-tailwind, eslint-config-custom, tsconfig, ui, website
• Running prettier:fix in 6 packages
• Remote caching disabled
//:prettier:fix: cache bypass, force executing 0263fb2fa2ae5114
husky - pre-commit hook exited with code 1 (error)

Expected Behavior

The commit is created without error.

What are the steps to reproduce this bug?

1. Create a commit with a modification for a file that is one of the following types ({js,jsx,ts,tsx,mjs,cjs})
2. Observe above error

Add the following custom actions to the plugins page:

• SonarQube
• Regex
• Quay
• Kubernetes

References: #206

Goal

Post a blog on janus-idp.io sharing the suggested approach to add/remove GPTs, avoiding the rebuild/redeploy process