Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-format for hugo docs #5489

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Re-format for hugo docs #5489

wants to merge 4 commits into from

Conversation

jameskerr
Copy link
Member

@jameskerr jameskerr commented Nov 19, 2024

Summary of changes.

In the front matter:

• sidebar_position becomes weight.
• sidebar_title becomes title.
• README becomes _index
• h1's have been removed from the markdown and rendered in the template with .Title or .Heading

If you want a different heading that what the title is, you can use the heading: key in the front matter.

Remove the => between code examples since we will have interactive playgrounds for all examples.

Comment on lines 27 to 52
<<<<<<< HEAD
Each `input` argument must be a file path, an HTTP or HTTPS URL,
an S3 URL, or standard input specified with `-`.

For built-in command help and a listing of all available options,
simply run `super` with no arguments.

`super` supports a number of [input](#input-formats) and [output](#output-formats) formats, but [Super Binary](../formats/bsup.md)
tends to be the most space-efficient and most performant. Super Binary has efficiency similar to
[Avro](https://avro.apache.org)
and [Protocol Buffers](https://developers.google.com/protocol-buffers)
but its comprehensive [type system](../formats/zed.md) obviates
the need for schema specification or registries.
Also, the [Super JSON](../formats/jsup.md) format is human-readable and entirely one-to-one with Super Binary
so there is no need to represent non-readable formats like Avro or Protocol Buffers
in a clunky JSON encapsulated form.

`super` typically operates on Super Binary-encoded data and when you want to inspect
human-readable bits of output, you merely format it as Super JSON, which is the
default format when output is directed to the terminal. Super Binary is the default
when redirecting to a non-terminal output like a file or pipe.

When run with input arguments, each input's format is [automatically inferred](#auto-detection)
and each input is scanned
in the order appearing on the command line forming the input stream.
=======

This comment was marked as resolved.

The `super` command works with data from ephemeral sources like files and URLs.
If you want to persist your data into a data lake for persistent storage,
check out the [`super db`](super-db.md) set of commands.
>>>>>>> origin/main

This comment was marked as resolved.

@@ -13,4 +13,4 @@ jobs:
steps:
- name: Send dispatch event
run: |
curl -XPOST -u "${{ secrets.PAT_USERNAME }}:${{ secrets.PAT_TOKEN }}" -H "Accept: application/vnd.github.v3+json" -H "Content-Type: application/json" https://api.github.com/repos/brimdata/zed-docs-site/dispatches --data '{"event_type":"zed-docs-update"}'
curl -XPOST -u "${{ secrets.PAT_USERNAME }}:${{ secrets.PAT_TOKEN }}" -H "Accept: application/vnd.github.v3+json" -H "Content-Type: application/json" https://api.github.com/repos/brimdata/superdb-website/dispatches --data '{"event_type":"super-docs-update", "client_payload": {"commit_sha": "${{ github.sha }}"}}'
Copy link
Contributor

Choose a reason for hiding this comment

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

For now I've just got this rigged up to send the commits on this hugo-docs branch. When we eventually merge this to main, we can switch over to an approach like the one in notify-downstream-merge.yaml that sends the merge commit SHA.

@@ -3,7 +3,7 @@ name: Notify docs update
on:
push:
branches:
- main
- hugo-docs
Copy link
Contributor

Choose a reason for hiding this comment

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

Make sure we change this back to main when we merge.

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.

2 participants