Architectural blueprints often contain forward looking statements by
their definition so we should exclude them from the default FutureTense
linting warning

This change only excludes blueprints currently emiting the warning and
an update to the blueprint template to exclude future ones

Marcel Amirault authored 1 year ago and Marcin Sedlak-Jakubowski committed 1 year ago

The disqus integration was removed from the docs site,
so these identifiers don't do anything now.

Thong Kuah authored 1 year ago and Lorena Ciutacu committed 1 year ago

As we renamed Pods to Cells

Thong Kuah authored 1 year ago and Kamil Trzciński committed 1 year ago

Adds redirects

This only provides a heading, but no description.
Claims an entry in index to fill data next.

Kamil Trzciński authored 2 years ago and Thong Kuah committed 2 years ago

This tries to highlight some features, define them and provide
a placeholder of some ideas for solutions to implement them.

The disclaimer will be added automatically when the
docs site builds and deploys.

Marcel Amirault authored 2 years ago and Suzanne Selhorn committed 2 years ago

All blueprints should use the same disclaimer, and they should have
the disclaimer at the very top of the page

Kamil Trzciński authored 2 years ago and Dylan Griffith committed 2 years ago

The intent is to describe all technical challenges in a coherent way.