Skip to content

feat(docs): versioned docs#220

Merged
silvolu merged 2 commits intogoogleapis:masterfrom
silvolu:versioned-docs
Sep 18, 2014
Merged

feat(docs): versioned docs#220
silvolu merged 2 commits intogoogleapis:masterfrom
silvolu:versioned-docs

Conversation

@silvolu
Copy link
Contributor

@silvolu silvolu commented Sep 17, 2014

'versions.txt' contains the available versions one per line.
The json files containing the docs for for each version are stored in
'docs/json//'.
'npm run docs' creates the json files in docs/json/development,
and version.txt contains the 'development' versions, to allow to serve
the docs locally in an easy way (using for example static).

'versions.txt' contains the available versions one per line.
The json files containing the docs for for each version are stored in
'docs/json/<version>/'.
'npm run docs' creates the json files in docs/json/development,
and version.txt contains the 'development' versions, to allow to serve
the docs locally in an easy way (using for example static).
@silvolu
Copy link
Contributor Author

silvolu commented Sep 17, 2014

Staged here:
http://silvolu.github.io/gcloud-node/#/

@ryanseys
Copy link
Contributor

Whoa awesome. Can we add an explanation as to what version "development" means? i.e. is it just docs straight from the master branch?

@silvolu
Copy link
Contributor Author

silvolu commented Sep 17, 2014

Yeah, the idea for the build is to update 'development' after merging to master with the potentially new docs.
I can rename 'development' to 'master', I was worried about it potentially being confusing for local development (e.g. you are working on branch 'x', but your docs are generated and published under 'master').

@silvolu
Copy link
Contributor Author

silvolu commented Sep 18, 2014

Changed the name to 'master'

silvolu added a commit that referenced this pull request Sep 18, 2014
@silvolu silvolu merged commit 8f5fbcb into googleapis:master Sep 18, 2014
@silvolu
Copy link
Contributor Author

silvolu commented Sep 18, 2014

Merging this to proceed with the build steps, please open a new issue if you have more feedback.

sofisl pushed a commit that referenced this pull request Sep 27, 2022
sofisl pushed a commit that referenced this pull request Oct 11, 2022
sofisl pushed a commit that referenced this pull request Oct 12, 2022
* updated CHANGELOG.md

* updated package.json

* updated samples/package.json
GautamSharda pushed a commit that referenced this pull request Jan 14, 2026
GautamSharda pushed a commit that referenced this pull request Jan 14, 2026
* Initial commit.

* Add unit test.

* Add message ordering sample.

* Rename a sample.

* Address comments.
GautamSharda pushed a commit that referenced this pull request Jan 15, 2026
GautamSharda pushed a commit that referenced this pull request Jan 20, 2026
* Initial commit.

* Add unit test.

* Add message ordering sample.

* Rename a sample.

* Address comments.
GautamSharda pushed a commit that referenced this pull request Jan 21, 2026
* Initial commit.

* Add unit test.

* Add message ordering sample.

* Rename a sample.

* Address comments.
miguelvelezsa pushed a commit that referenced this pull request Jan 28, 2026
* Initial commit.

* Add unit test.

* Add message ordering sample.

* Rename a sample.

* Address comments.
miguelvelezsa pushed a commit that referenced this pull request Jan 29, 2026
…#220)

This PR was generated using Autosynth. 🌈

Synth log will be available here:
https://source.cloud.google.com/results/invocations/7b446397-88f3-4463-9e7d-d2ce7069989d/targets

- [ ] To automatically regenerate this PR, check this box.

Source-Link: googleapis/synthtool@5936421
sofisl pushed a commit that referenced this pull request Feb 3, 2026
* Initial commit.

* Add unit test.

* Add message ordering sample.

* Rename a sample.

* Address comments.
GautamSharda pushed a commit that referenced this pull request Feb 3, 2026
* Initial commit.

* Add unit test.

* Add message ordering sample.

* Rename a sample.

* Address comments.
sofisl pushed a commit that referenced this pull request Feb 4, 2026
sofisl pushed a commit that referenced this pull request Feb 5, 2026
* Initial commit.

* Add unit test.

* Add message ordering sample.

* Rename a sample.

* Address comments.
GautamSharda pushed a commit that referenced this pull request Feb 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants