Added the last portfolio item.
This commit is contained in:
g*
parent
8682c67a8b
commit
4777d96c42
3 changed files with 64 additions and 20 deletions
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: PcVue assessment
|
||||
description: An assessment of the documentation provided by PcVue.
|
||||
title: Establish SPREAD documentation
|
||||
description: An overview of how I established the documentation function at SPREAD.
|
||||
hide:
|
||||
# - toc
|
||||
- navigation
|
||||
|
|
@ -13,27 +13,63 @@ hide:
|
|||
border-radius: 5px;
|
||||
}
|
||||
|
||||
.tooling {
|
||||
font-family: var(--secondary-font);
|
||||
div.tooling {
|
||||
margin: 1.5em 0;
|
||||
}
|
||||
|
||||
div.tooling p {
|
||||
font-family: var(--secondary-font) !important;
|
||||
font-weight: bold;
|
||||
}
|
||||
}
|
||||
</style>
|
||||
|
||||
> ### Brief<br>
|
||||
> **February 2022**<br>
|
||||
> Establish the documentation function at SPREAD.
|
||||
|
||||
<span class='tooling' markdown>:simple-materialformkdocs: MkDocs Material | :material-graphql: GraphQL | :material-language-javascript: JavaScript | :material-language-python: Python | :simple-jinja: Jinja | :material-language-markdown: MarkDown | :simple-v: Vale | :simple-githubactions: GitHub Actions | :material-docker: Docker</span>
|
||||
<div class='tooling' markdown>:simple-materialformkdocs: MkDocs Material ⋅ :material-graphql: GraphQL ⋅ :material-language-javascript: JavaScript ⋅ :material-language-python: Python ⋅ :simple-jinja: Jinja ⋅ :material-language-markdown: MarkDown ⋅ :simple-v: Vale ⋅ :simple-githubactions: GitHub Actions ⋅ :material-docker: Docker</div>
|
||||
|
||||
{ height=300px }
|
||||
|
||||
## Challenge
|
||||
|
||||
Mambu Process Orchestrator - a white-labelled product built on top of the Corezoid low-code engine - had no documentation, but was already being used by clients. Some with highly complex workflows taht were beginning to break in unexpected ways in an environment where no failure could be tolerated. The underlying technology was built by a Ukranian company, who were under strain following the invasion by Russia in the same time period.
|
||||
There was no documentation, except for a few Confluence pages put together by engineers. The challenge was to create a documentation site, create the processes and pipelines to maintain it, and to write the content. The task was made more difficult by the fact that the product was constantly changing and I had engineering time to lean on.
|
||||
|
||||
## Solution
|
||||
|
||||
Partner with Corezoid to help them develop their documentation alongside ours. Get field-tested best practices from clients who were using the tool. Ask the Solution Engineers to sketch out the most urgent work needed and teh scope they cover when workign with clients. Compile a documentation set in the shortest time possible to fill this documentation gap.
|
||||
**In the first three months:**
|
||||
|
||||
- Evaluated and selected options for the technical infrastructure.
|
||||
- Socialized the newly established function in the company.
|
||||
- Created the internal website.
|
||||
- Created the initial build pipelines.
|
||||
- Got to 50% product coverage.
|
||||
- Wrote an initial style guide for general contributions
|
||||
|
||||
{ height=300px }
|
||||
|
||||
**In the second quarter:**
|
||||
|
||||
- Got product coverage to 90%.
|
||||
- Moved to multi-repo setup, where engineering teams "owned" their content and maintained updates.
|
||||
- Built the linting pipelines for general contributions.
|
||||
- Document white-labelled products with internal customisations.
|
||||
|
||||
{ height=300px }
|
||||
|
||||
**Within the first year:**
|
||||
|
||||
- Publish the documentation site publicly.
|
||||
- Publish the SPREAD glossary of terms.
|
||||
- Create course content for new users.
|
||||
|
||||
**Within the last year:**
|
||||
|
||||
- Move to a mono-repo setup.
|
||||
- Create more course content.
|
||||
- Add AI enhancements to the build pipeline.
|
||||
- Better monitoring of product changes.
|
||||
- Re-start initiative for more people to write documentation.
|
||||
|
||||
<a href='https://docs.spread.ai' target='_blank'><div class="button">See the site</div></a>
|
||||
|
||||
|
|
|
|||
|
|
@ -13,17 +13,21 @@ hide:
|
|||
border-radius: 5px;
|
||||
}
|
||||
|
||||
.tooling {
|
||||
font-family: var(--secondary-font);
|
||||
div.tooling {
|
||||
margin: 1.5em 0;
|
||||
}
|
||||
|
||||
div.tooling p {
|
||||
font-family: var(--secondary-font) !important;
|
||||
font-weight: bold;
|
||||
}
|
||||
}
|
||||
</style>
|
||||
|
||||
> ### Brief<br>
|
||||
> **November 2023**<br>
|
||||
> Create documentation for a command-line interface (CLI) used by banking engineering teams to perform actions in Mambu.
|
||||
|
||||
<span class='tooling' markdown>:material-language-typescript: TypeScript | :material-nodejs: NodeJS</span>
|
||||
<div class='tooling' markdown>:material-language-typescript: TypeScript ⋅ :material-nodejs: NodeJS</div>
|
||||
|
||||
|
||||
{ height=300px }
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Mambu Process Orchestrator
|
||||
description: An assessment of the documentation provided by PcVue.
|
||||
description: An overview of how I documented a feature set at Mambu.
|
||||
hide:
|
||||
# - toc
|
||||
- navigation
|
||||
|
|
@ -11,29 +11,33 @@ hide:
|
|||
img {
|
||||
border: 0.5px solid #ededed;
|
||||
border-radius: 5px;
|
||||
}
|
||||
}
|
||||
|
||||
.tooling {
|
||||
font-family: var(--secondary-font);
|
||||
div.tooling {
|
||||
margin: 1.5em 0;
|
||||
}
|
||||
|
||||
div.tooling p {
|
||||
font-family: var(--secondary-font) !important;
|
||||
font-weight: bold;
|
||||
}
|
||||
}
|
||||
</style>
|
||||
|
||||
> ### Brief<br>
|
||||
> **March 2021**<br>
|
||||
> Own the documentation for the low-code orchestrator for integrations into banking services.
|
||||
|
||||
<span class='tooling' markdown>:simple-hugo: Hugo</span>
|
||||
<div class='tooling' markdown>:simple-hugo: Hugo</div>
|
||||
|
||||
{ height=300px }
|
||||
|
||||
## Challenge
|
||||
|
||||
Mambu Process Orchestrator - a white-labelled product built on top of the Corezoid low-code engine - had no documentation, but was already being used by clients. Some with highly complex workflows taht were beginning to break in unexpected ways in an environment where no failure could be tolerated. The underlying technology was built by a Ukranian company, who were under strain following the invasion by Russia in the same time period.
|
||||
Mambu Process Orchestrator - a white-labelled product built on top of the Corezoid low-code engine - had no documentation, but was already being used by clients. Some with highly complex workflows that were beginning to break in unexpected ways in an environment where no failure could be tolerated. The underlying technology was built by a Ukrainian company, who were under strain following the invasion by Russia in the same time period.
|
||||
|
||||
## Solution
|
||||
|
||||
Partner with Corezoid to help them develop their documentation alongside ours. Get field-tested best practices from clients who were using the tool. Ask the Solution Engineers to sketch out the most urgent work needed and teh scope they cover when workign with clients. Compile a documentation set in the shortest time possible to fill this documentation gap.
|
||||
Partner with Corezoid to help them develop their documentation alongside ours. Get field-tested best practices from clients who were using the tool. Ask the Solution Engineers to sketch out the most urgent work needed and the scope they cover when working with clients. Compile a documentation set in the shortest time possible to fill this documentation gap.
|
||||
|
||||
<a href='https://ecosystem.mambu.com/mpo/overview/' target='_blank'><div class="button"><abbr title='The set has largely been left unmaintained as this tool is scheduled for decomissioning.'>Read the documentation set</abbr></div></a>
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue