Getting started draft #40
Conversation
| @@ -1,23 +1,88 @@ | |||
| --- | |||
| title: Writing your first IceRPC application | |||
| description: TODO | |||
| title: Writing your first IceRPC application in C# | |||
There was a problem hiding this comment.
I would leave this as "Writing your first IceRPC application". In the future when we have icerpc-rs we would use this same page for getting started and just use a language selector to change the content on the page.
There was a problem hiding this comment.
does this imply we will have the content for all languages on this document?
There was a problem hiding this comment.
I think it makes sense to use separate pages in this case, I belive this documents would be very different for each language,
There was a problem hiding this comment.
From the users perspective though the dont care how we internally represent the pages. All they care about is that they select their language and that they only see content relevant for that language.
MarkDoc supports a feature called partials where for longer pages we could split the markdown into seprate files and pull it into a page https://markdoc.dev/docs/partials#partials. This could be a solution when we start thinking about other languages.
.vscode/cspell.json
Outdated
| @@ -29,13 +30,15 @@ | |||
| "Renderable", | |||
| "RFCOMM", | |||
| "Roboto", | |||
| "rpcs", | |||
There was a problem hiding this comment.
Why do we need rpcs?
I would avoid the plural and rpc should be spelled RPC not rpc.
There was a problem hiding this comment.
I added this because spell check job was failing,
data\icerpc-core-data.ts
140: path: `${RPC_CORE_BASE_URL}/icerpc-protocol/mapping-rpcs-to-streams
This is a draft for the getting started page