Files
backstage/microsite
Damola Obaleke 2ec0734a61 Created technical article blog 2025-08-8-migrating-legacy-services-to-a-modern-developer-portal (#30844)
* Created 2025-08-8-migrating-legacy-services-to-a-modern-developer-portal.md

Signed-off-by: Damola Obaleke <45045727+damolaobaleke@users.noreply.github.com>
Signed-off-by: Damola Obaleke <damolaobaleke@gmail.com>

* Update 2025-08-8-migrating-legacy-services-to-a-modern-developer-portal.md

added in # prettier-ignore which Jeff added

Signed-off-by: Damola Obaleke <45045727+damolaobaleke@users.noreply.github.com>
Signed-off-by: Damola Obaleke <damolaobaleke@gmail.com>

* Update 2025-08-8-migrating-legacy-services-to-a-modern-developer-portal.md

added in truncate tag

Signed-off-by: Damola Obaleke <45045727+damolaobaleke@users.noreply.github.com>
Signed-off-by: Damola Obaleke <damolaobaleke@gmail.com>

* Update 2025-08-8-migrating-legacy-services-to-a-modern-developer-portal.md

currently adding the assets directory for images just fixed formatting

Signed-off-by: Damola Obaleke <45045727+damolaobaleke@users.noreply.github.com>
Signed-off-by: Damola Obaleke <damolaobaleke@gmail.com>

* Add files via upload

Signed-off-by: Damola Obaleke <45045727+damolaobaleke@users.noreply.github.com>
Signed-off-by: Damola Obaleke <damolaobaleke@gmail.com>

* Add files via upload

Signed-off-by: Damola Obaleke <45045727+damolaobaleke@users.noreply.github.com>
Signed-off-by: Damola Obaleke <damolaobaleke@gmail.com>

* Delete 2025-08-08 directory

Signed-off-by: Damola Obaleke <45045727+damolaobaleke@users.noreply.github.com>
Signed-off-by: Damola Obaleke <damolaobaleke@gmail.com>

* Update 2025-08-8-migrating-legacy-services-to-a-modern-developer-portal.md

Fixed all assets, being reference from assets directory
Fixed all formatting issues

Signed-off-by: Damola Obaleke <45045727+damolaobaleke@users.noreply.github.com>
Signed-off-by: Damola Obaleke <damolaobaleke@gmail.com>

* added dark version image of plugin ecosystem

Signed-off-by: Damola Obaleke <45045727+damolaobaleke@users.noreply.github.com>
Signed-off-by: Damola Obaleke <damolaobaleke@gmail.com>

* Update and rename 2025-08-8-migrating-legacy-services-to-a-modern-developer-portal.md to 2025-08-8-migrating-legacy-services-to-a-modern-developer-portal.mdx

1. took out #prettier ignore line
2. Added dark version image
3. renamed to .mdx extension

Signed-off-by: Damola Obaleke <45045727+damolaobaleke@users.noreply.github.com>
Signed-off-by: Damola Obaleke <damolaobaleke@gmail.com>

* Rename to 2025-08-08-migrating-legacy-services-to-a-modern-developer-portal.mdx to 2025-08-08-migrating-legacy-services-to-a-modern-developer-portal.mdx

Signed-off-by: Damola Obaleke <45045727+damolaobaleke@users.noreply.github.com>
Signed-off-by: Damola Obaleke <damolaobaleke@gmail.com>

* fixed formatting with prettier. ran yarn prettier:fix

Signed-off-by: Damola Obaleke <damolaobaleke@gmail.com>

* deleted image 5

Signed-off-by: Damola Obaleke <damolaobaleke@gmail.com>

* deleted image and used prettier fix

Signed-off-by: Damola Obaleke <damolaobaleke@gmail.com>

* removed yarn duplicate version packages in lock file

Signed-off-by: Damola Obaleke <damolaobaleke@gmail.com>

* took out backstage/cli package and added it as a dev dependency

Signed-off-by: Damola Obaleke <damolaobaleke@gmail.com>

* removed backstage/cli dependency

Signed-off-by: Damola Obaleke <damolaobaleke@gmail.com>

* removed backstage/cli dependency and updated yarn lock

Signed-off-by: Damola Obaleke <damolaobaleke@gmail.com>

* reverting yarn lock so there are no changes

Signed-off-by: Damola Obaleke <damolaobaleke@gmail.com>

* reverting yarn lock so there are no changes

Signed-off-by: Damola Obaleke <damolaobaleke@gmail.com>

* reverting yarn lock so there are no changes

Signed-off-by: Damola Obaleke <damolaobaleke@gmail.com>

---------

Signed-off-by: Damola Obaleke <45045727+damolaobaleke@users.noreply.github.com>
Signed-off-by: Damola Obaleke <damolaobaleke@gmail.com>
2025-08-12 17:26:05 +02:00
..

Backstage Documentation

This folder holds the service and configuration that runs Backstage's documentation hosted at https://backstage.io.

It pulls content in from the root /docs folder and builds it into the resulting HTML web site.

This website was created with Docusaurus.

What's In This Document

Getting Started

Testing the web site locally is a great way to see what final website will look like after publishing, and is ideal for testing more complex changes, large updates to navigation, or complex page designs that may include special alignment, which may not otherwise be validated through continuous integration.

Installation

$ yarn install

Local Development

$ yarn start

This command starts a local development server and opens up a browser window. Most content changes made to the docs/ root folder are reflected live without having to restart the server.

Build

$ yarn build

This command generates static content into the build directory, which is what will be deployed to GitHub pages from the master branch.

Directory Structure

Your project file structure should look something like this

my-docusaurus/
  docs/
    doc-1.md
    doc-2.md
    doc-3.md
  website/
    blog/
      2016-3-11-oldest-post.md
      2017-10-24-newest-post.md
    core/
    node_modules/
    pages/
    static/
      css/
      img/
    package.json
    sidebars.js
    siteConfig.js

Editing Content

Editing an existing docs page

Edit docs by navigating to docs/ and editing the corresponding document:

docs/doc-to-be-edited.md

---
id: page-needs-edit
title: This Doc Needs To Be Edited
---

Edit me...

For more information about docs, click here

Editing an existing blog post

Edit blog posts by navigating to website/blog and editing the corresponding post:

website/blog/post-to-be-edited.md

---
id: post-needs-edit
title: This Blog Post Needs To Be Edited
---

Edit me...

For more information about blog posts, click here

Adding Content

Adding a new docs page to an existing sidebar

  1. Create the doc as a new markdown file in /docs, example docs/newly-created-doc.md:

    ---
    id: newly-created-doc
    title: This Doc Needs To Be Edited
    ---
    
    My new content here..
    
  2. Refer to that doc's ID in an existing sidebar in website/sidebars.js:

    // Add newly-created-doc to the Getting Started category of docs
    module.exports = {
    ...
    docs: {
     "Getting Started": [
       "quick-start",
       "newly-created-doc" // new doc here
     ],
     ...
    },
    ...
    }
    

For more information about adding new docs, click here

Adding a new blog post

  1. Make sure there is a header link to your blog in website/siteConfig.js:

    website/siteConfig.js

    headerLinks: [
        ...
        { blog: true, label: 'Blog' },
        ...
    ]
    
  2. Create the blog post with the format YYYY-MM-DD-My-Blog-Post-Title.md in website/blog:

    website/blog/2018-05-21-New-Blog-Post.md

    ---
    author: Frank Li
    authorURL: https://twitter.com/foobarbaz
    authorFBID: 503283835
    title: New Blog Post
    ---
    
    Lorem Ipsum...
    

For more information about blog posts, click here

Adding items to your site's top navigation bar

  1. Add links to docs, custom pages or external links by editing the headerLinks field of website/siteConfig.js:

    website/siteConfig.js

    {
      headerLinks: [
        ...
        /* you can add docs */
        { doc: 'my-examples', label: 'Examples' },
        /* you can add custom pages */
        { page: 'help', label: 'Help' },
        /* you can add external links */
        { href: 'https://github.com/facebook/docusaurus', label: 'GitHub' },
        ...
      ],
      ...
    }
    

For more information about the navigation bar, click here

Adding custom pages

  1. Docusaurus uses React components to build pages. The components are saved as .js files in website/pages/en:

  2. If you want your page to show up in your navigation header, you will need to update website/siteConfig.js to add to the headerLinks element:

    website/siteConfig.js

    {
      headerLinks: [
        ...
        { page: 'my-new-custom-page', label: 'My New Custom Page' },
        ...
      ],
      ...
    }
    

Learn more about Docusaurus custom pages.

Full Documentation

Full documentation can be found on the Docusaurus website.

Additional notes

  • If you want to make images zoomable on click, add the data-zoomable attribute to your img element.

    • In a docs or blog .md file, convert ![This is image](/microsite/static/img/code.png) syntax to <img data-zoomable src="/microsite/static/img/code.png" alt="This is image" />
  • Code block line highlighting uses custom magic comments. Currently, we have the following magic comments:

    • Highlight line(s)
      • highlight-next-line
      • highlight-start
      • highlight-end
    • Add line(s)
      • highlight-add-next-line
      • highlight-add-start
      • highlight-add-end
    • Remove line(s)
      • highlight-remove-next-line
      • highlight-remove-start
      • highlight-remove-end

Feedback widget

A feedback widget is provided by the docusaurus-pushfeedback plugin, which connects to the https://pushfeedback.com service. Styling of the button is configured in microsite/src/theme/customTheme.scss, while the plugin itself is configured in microsite/docusaurus.config.js.

Feedback submissions are connected to an account owned by @Rugvip and are available on request, reach out to @Rugvip on Discord.