Skip to content

Relocate event source docs#3948

Merged
knative-prow-robot merged 13 commits into
knative:mkdocsfrom
snneji:relocate-event-source-docs
Jul 7, 2021
Merged

Relocate event source docs#3948
knative-prow-robot merged 13 commits into
knative:mkdocsfrom
snneji:relocate-event-source-docs

Conversation

@snneji
Copy link
Copy Markdown
Contributor

@snneji snneji commented Jul 6, 2021

Fixes #3936

  • Moved files to the developer directory
  • Updated nav.yaml
  • Updated links

@knative-prow-robot knative-prow-robot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label Jul 6, 2021
@google-cla google-cla Bot added the cla: yes Indicates the PR's author has signed the CLA. label Jul 6, 2021
@netlify
Copy link
Copy Markdown

netlify Bot commented Jul 6, 2021

✔️ Deploy Preview for dev-knative ready!

🔨 Explore the source changes: 2a83ded

🔍 Inspect the deploy log: https://app.netlify.com/sites/dev-knative/deploys/60e5b57c255c74000846c994

😎 Browse the preview: https://deploy-preview-3948--dev-knative.netlify.app

@snneji snneji marked this pull request as draft July 6, 2021 14:11
@knative-prow-robot knative-prow-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 6, 2021
@snneji snneji changed the title Relocate event source docs (WIP) Relocate event source docs Jul 6, 2021
@knative-prow-robot knative-prow-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 6, 2021
@snneji
Copy link
Copy Markdown
Contributor Author

snneji commented Jul 6, 2021

/retest

@knative-prow-robot knative-prow-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 6, 2021
@snneji snneji marked this pull request as ready for review July 6, 2021 15:27
@snneji snneji changed the title (WIP) Relocate event source docs Relocate event source docs Jul 6, 2021
@knative-prow-robot knative-prow-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 6, 2021
Comment thread config/nav.yml Outdated
Comment on lines +73 to +84
- Creating an event source:
- Overview: developer/eventing/sources/creating-event-sources/README.md
- Writing an event source using Javascript: developer/eventing/sources/creating-event-sources/writing-event-source-easy-way/README.md
- Using the sample event source:
- Overview: developer/eventing/sources/creating-event-sources/writing-event-source/README.md
- Design of an Event Source: developer/eventing/sources/creating-event-sources/writing-event-source/01-theory.md
- Lifecycle and Types: developer/eventing/sources/creating-event-sources/writing-event-source/02-lifecycle-and-types.md
- Controller Implemetation: developer/eventing/sources/creating-event-sources/writing-event-source/03-controller.md
- Reconciler Implementation: developer/eventing/sources/creating-event-sources/writing-event-source/04-reconciler.md
- Receive Adapter Implementation: developer/eventing/sources/creating-event-sources/writing-event-source/05-receive-adapter.md
- Publishing to your cluster: developer/eventing/sources/creating-event-sources/writing-event-source/06-yaml.md
- Moving to knative-sandbox: developer/eventing/sources/creating-event-sources/writing-event-source/07-knative-sandbox.md
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would put this under Event Sources to keep all the event sources docs grouped?

Comment thread config/nav.yml
Comment thread config/nav.yml
Comment on lines +222 to +227
- CloudAuditLogsSource: eventing/samples/cloud-audit-logs-source/README.md
- CloudPubSubSource: eventing/samples/cloud-pubsub-source/README.md
- CloudSchedulerSource: eventing/samples/cloud-scheduler-source/README.md
- CloudStorageSource: eventing/samples/cloud-storage-source/README.md
- GitHub source: eventing/samples/github-source/README.md
- GitLab source: eventing/samples/gitlab-source/README.md
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same for all of these, idk why they wouldn't be part of the single Event Source docs section?

Copy link
Copy Markdown
Contributor Author

@snneji snneji Jul 7, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was confused about what to do with samples. There were three options I could think of (I was not sure which one we plan to do so I just left them where they were):

  • Do we plan to have a section of the docs for all samples?
  • Or a subsection for all samples at the end of each guide?
  • Or do we want to have samples at the end of each subgroup -- eg, event source samples, autoscaling samples?

I think if we have all the samples in the same place it might be easier to link to from the What's Next page, but this is not a strongly held position.

Will deal with samples in #3796

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer we don't have a samples section at all and just add them as part of the main docs for each thing they're a sample of. As a user I wouldn't want to look in two different places for docs on how to create a resource and then samples for them. For example, rather than having a GitLab source sample somewhere, just add GitLab source to the main event source docs and use the sample as a basis for documenting it properly.

Comment thread docs/admin/install/eventing/install-eventing-with-yaml.md
@abrennan89
Copy link
Copy Markdown
Contributor

/approve
/lgtm

Found one seemingly broken link and left some suggestions, but otherwise looks good.
Feel free to remove the hold if you want to merge this @snneji

/hold

@knative-prow-robot knative-prow-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 6, 2021
@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 6, 2021
@knative-prow-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abrennan89, snneji

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow-robot knative-prow-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 6, 2021
@knative-prow-robot knative-prow-robot removed the lgtm Indicates that a PR is ready to be merged. label Jul 7, 2021
@omerbensaadon
Copy link
Copy Markdown

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 7, 2021
@omerbensaadon
Copy link
Copy Markdown

/unhold

@knative-prow-robot knative-prow-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 7, 2021
@omerbensaadon
Copy link
Copy Markdown

/hold

@knative-prow-robot knative-prow-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 7, 2021
@snneji
Copy link
Copy Markdown
Contributor Author

snneji commented Jul 7, 2021

/unhold

@knative-prow-robot knative-prow-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 7, 2021
@omerbensaadon
Copy link
Copy Markdown

/unhold

@omerbensaadon
Copy link
Copy Markdown

/hold

@knative-prow-robot knative-prow-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 7, 2021
@knative-prow-robot knative-prow-robot removed the lgtm Indicates that a PR is ready to be merged. label Jul 7, 2021
@omerbensaadon
Copy link
Copy Markdown

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 7, 2021
@omerbensaadon
Copy link
Copy Markdown

/unhold

@knative-prow-robot knative-prow-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 7, 2021
@knative-prow-robot knative-prow-robot merged commit 0695377 into knative:mkdocs Jul 7, 2021
snneji added a commit to snneji/docs that referenced this pull request Jul 8, 2021
* Update links

* Update nav.yaml for event source move

* fix another link

* Move event source files to developer guide

* Move event samples to samples folder

* Move event samples to samples folder

* link fixes and improvements

* tweak some more links

* Update redirects

* Rebase redirects

* fixing infinite redirect bug

* Move creating event sources

Co-authored-by: Omer B <obensaadon@vmware.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Move event source docs to developer guide

4 participants