<figure class="table"><table><thead><tr><th>Subsector</th><th>title</th><th>date</th><th>category</th></tr></thead><tbody><tr><td>1<img src="https://res.cloudinary.com/platformable/image/upload/v1701431546/platformablewebsite2023/Innovate_Proactively_52637ba201.png" alt="Innovate Proactively.png" srcset="https://res.cloudinary.com/platformable/image/upload/v1701431546/platformablewebsite2023/thumbnail_Innovate_Proactively_52637ba201.png 245w,https://res.cloudinary.com/platformable/image/upload/v1701431546/platformablewebsite2023/small_Innovate_Proactively_52637ba201.png 500w," sizes="100vw" width="500px"></td><td>title</td><td>2023/14/1</td><td>&nbsp;</td></tr><tr><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr><tr><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr></tbody></table></figure>

large_value model 1280x720.png

medium_value model 1280x720.png

small_value model 1280x720.png

thumbnail_value model 1280x720.png

value model 1280x720.png

# How to create a new Document
Documents are .md files hosted on a repository

### To create a new document follow this steps:

1.- Click on Catalog -> Software
2.- Click on Create Button (top right)
3.- Follow instructions

# How to add a Document
Documents needs to have a special file structure as described below:

```
├── README.md
├── catalog-info.yaml
├── docs
│   └── index.md
├── mkdocs.yml
└── src
    └── // The code of your component
```

### Add the mkdocs configuration file
Create a file called mkdocs.yml in the root of a component you want to document in Backstage. Inside that YAML file, add the following content, replacing {component-name} with the name of your component.
```
site_name: '{component-name}'

plugins:
  - techdocs-core
# example navigation  
nav:
  - Introduction: index.md
```

### Update the YAML metadata
Use the catalog-info.yaml file of our component to tell Backstage where to find the documentation.
Add the backstage.io/techdocs-ref annotation to the list of annotations.

```
annotations:
  backstage.io/techdocs-ref: dir:.
  
```  
If your docs are located elsewhere, you must explicitly point to them like this:
```
apiVersion: backstage.io/v1alpha1
kind: Component
metadata:
  name: sample-service
  description: # ...
  annotations:
    backstage.io/techdocs-ref: url:https://github.com/your-org/your-repo/tree/main
spec:
  type: service
  owner: engineering
  lifecycle: experimental
  ````

⚠️ The GitHub URL must be prefixed with url: or the documentation will not render in Backstage.


# Add existing Documentation
### Enter the URL to your source code repository to add it to your Backstage App.

### Link to an existing entity file
> Example: https://github.com/backstage/backstage/blob/master/catalog-info.yaml

The wizard analyzes the file, previews the entities, and adds them to the Scaffolded Backstage App catalog.

### Link to a repository 
GitHub only
> Example: https://github.com/backstage/backstage

>> The wizard discovers all catalog-info.yaml files in the repository, previews the entities, and adds them to the Scaffolded Backstage App catalog.

If no entities are found, the wizard will prepare a Pull Request that adds an example catalog-info.yaml and prepares the Scaffolded Backstage App catalog to load all entities as soon as the Pull Request is merged.

![Alt text](https://www.markdownguide.org/assets/images/markdown-guide-og.jpg "a title")



```css
#button {
 border: none;
}
```

* Item
* Item
- Item
- Item


~~~~
This is a
piece of code
in a block
~~~~



# Header 1
## Header 2
### Header 3
#### Header 4 ####
##### Header 5 #####
###### Header 6 ######


| Month    | Savings |
| -------- | ------- |
| January  | $250    |
| February | $80     |
| March    | $420    |


Open Ecosystem

Open Banking

Open Health

NEW Traceability

Open Ecosystems

Engage

fake post to test components

Related articles