Skip to content

Commit

Permalink
Remove beta messaging from the site and docs (#338)
Browse files Browse the repository at this point in the history
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.
  • Loading branch information
rowanmanning authored Dec 9, 2020
1 parent 7f70f23 commit 823490f
Show file tree
Hide file tree
Showing 6 changed files with 4 additions and 18 deletions.
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ Anybody working for the Financial Times is welcome to suggest changes via a GitH
There are many different ways you can contribute and help make this resource better for everyone:

- **Contribute to the Engineering Competencies**<br/>
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).
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).

- **Contribute to the documentation and website**<br/>
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)
Expand Down
4 changes: 1 addition & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,6 @@

Careers and progression for engineers in the CTO organisation.

:info: This project is currently in **BETA**.

---

- [Overview](#overview)
Expand Down Expand Up @@ -37,7 +35,7 @@ Engineering competencies are used to inform conversations about career progressi
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:

- **Contribute to the Engineering Competencies**<br/>
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).
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).

- **Contribute to the documentation and website**<br/>
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)
Expand Down
2 changes: 1 addition & 1 deletion docs/competencies.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@

# Contributing: Engineering Competencies

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.
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.

- [Language Guidelines](#language-guidelines)
- [Editing on GitHub](#editing-on-github)
Expand Down
11 changes: 0 additions & 11 deletions site/_includes/prerelease-banner.html

This file was deleted.

1 change: 0 additions & 1 deletion site/_layouts/default.html
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,6 @@
<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">

<div class="o-layout__header">
{% include prerelease-banner.html %}
{% include header.html %}
</div>

Expand Down
2 changes: 1 addition & 1 deletion site/pages/faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ either a position needs to become vacant, or a new Principal Engineer role must
created, typically when forming a new team, significantly expanding an existing one,
or some other significant change occurs in a technology group's circumstances.

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

Expand Down

0 comments on commit 823490f

Please sign in to comment.