Skip to content

Commit 823490f

Browse files
authored
Remove beta messaging from the site and docs (#338)
We need to do this before releasing v1.0.0, which I'll do once this is merged. I decided to remove the beta banner rather than change it to announce the stable version - this turned out to be a pain to do (because o-message styling seems a bit broken) and I don't have the time to properly investigate now.
1 parent 7f70f23 commit 823490f

File tree

6 files changed

+4
-18
lines changed

6 files changed

+4
-18
lines changed

CONTRIBUTING.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Anybody working for the Financial Times is welcome to suggest changes via a GitH
1515
There are many different ways you can contribute and help make this resource better for everyone:
1616

1717
- **Contribute to the Engineering Competencies**<br/>
18-
The Engineering competencies are used to inform conversations about career progression between an engineer and their line manager. Every engineer in the CTO organisation of the Financial Times can help shape these competencies. While they are in alpha and beta we are especially interested in contributions. [A guide for adding or editing competencies is here](docs/competencies.md).
18+
The Engineering competencies are used to inform conversations about career progression between an engineer and their line manager. Every engineer in the CTO organisation of the Financial Times can help shape these competencies. [A guide for adding or editing competencies is here](docs/competencies.md).
1919

2020
- **Contribute to the documentation and website**<br/>
2121
It's important that the documentation in this repo and the Engineering Progression website are clear and easy to understand. [Get started maintaining the documentation](docs/documentation.md)

README.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,6 @@
33

44
Careers and progression for engineers in the CTO organisation.
55

6-
:info: This project is currently in **BETA**.
7-
86
---
97

108
- [Overview](#overview)
@@ -37,7 +35,7 @@ Engineering competencies are used to inform conversations about career progressi
3735
Anybody working for the Financial Times is welcome to suggest changes via a GitHub issue or pull request. We maintain a [contributing guide](CONTRIBUTING.md) to help people who are interested. There are many different ways you can contribute and help make this resource better for everyone:
3836

3937
- **Contribute to the Engineering Competencies**<br/>
40-
Every engineer in the CTO organisation of the Financial Times can help shape these competencies. While they are in alpha and beta we are especially interested in contributions. [A guide for adding or editing competencies is here](docs/competencies.md).
38+
Every engineer in the CTO organisation of the Financial Times can help shape these competencies. [A guide for adding or editing competencies is here](docs/competencies.md).
4139

4240
- **Contribute to the documentation and website**<br/>
4341
It's important that the documentation in this repo and the Engineering Progression website is clear and easy to understand. [Get started maintaining the documentation](docs/documentation.md)

docs/competencies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11

22
# Contributing: Engineering Competencies
33

4-
The Engineering competencies are used to inform conversations about career progression between an engineer and their line manager. Every engineer in the CTO organisation of the Financial Times can help shape these competencies. While they are in alpha and beta we are especially interested in contributions.
4+
The Engineering competencies are used to inform conversations about career progression between an engineer and their line manager. Every engineer in the CTO organisation of the Financial Times can help shape these competencies.
55

66
- [Language Guidelines](#language-guidelines)
77
- [Editing on GitHub](#editing-on-github)

site/_includes/prerelease-banner.html

Lines changed: 0 additions & 11 deletions
This file was deleted.

site/_layouts/default.html

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,6 @@
5959
<div class="o-layout {% if layout.o_layout_type %}o-layout--{{layout.o_layout_type}}{% else %}o-layout--docs{% endif %}" data-o-component="o-layout">
6060

6161
<div class="o-layout__header">
62-
{% include prerelease-banner.html %}
6362
{% include header.html %}
6463
</div>
6564

site/pages/faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ either a position needs to become vacant, or a new Principal Engineer role must
4444
created, typically when forming a new team, significantly expanding an existing one,
4545
or some other significant change occurs in a technology group's circumstances.
4646

47-
Post Beta, we do aim to include competencies for Principal Engineers within
47+
We do aim to include competencies for Principal Engineers within
4848
the FT engineering competencies, to act as a guide for recruiting managers and
4949
existing Senior 2 Engineers.
5050

0 commit comments

Comments
 (0)