Skip to content

docs: quickstart and homepage improvements #2008

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

Closed
wants to merge 8 commits into from

Conversation

cahyosubroto
Copy link

@cahyosubroto cahyosubroto commented Feb 13, 2024

Describe Your Changes

In this pull request, I focused on enhancing the overall user experience and accessibility of the documentation website. Here are the key changes:

  1. Added Quickstart Documentation:

    • Included detailed Quickstart documentation to help users get started quickly.
    • Modified the configuration file to ensure the Quickstart menu appears in the Navbar, improving navigation.
  2. Revamped Homepage Design:

    • Introduced a new design for the homepage to enhance visual appeal and user engagement.

Fixes Issues

  • None

Self Checklist

  • [] Added relevant comments, especially in complex areas.
  • Updated documentation to reflect the changes made.
  • Created issues for follow-up changes or refactoring needed.

Additional Notes:
Include any additional information that might be helpful for reviewers, such as specific challenges faced, notable decisions made, or any dependencies introduced.

cc: @aindrajaya

0xHieu01 and others added 5 commits February 7, 2024 11:03
Sync dev branch to docs branch
Update the docs by adding examples of the latest documentation by Pena
Update the configuration file which shows the Quickstart menu in the Navbar
@aindrajaya aindrajaya added the type: docs Improvements or additions to documentation label Feb 13, 2024
@freelerobot freelerobot requested review from freelerobot, dan-menlo, 0xHieu01 and urmauur and removed request for dan-menlo and 0xHieu01 February 13, 2024 08:28
@freelerobot freelerobot changed the title Docs docs: quickstart and homepage improvements Feb 13, 2024
@freelerobot
Copy link
Contributor

@hiento09 for when you're back. Is there a way to enable autodeploy to github pages, with our ci, so we can preview the docs contributions?

Copy link
Contributor

@freelerobot freelerobot left a comment

Choose a reason for hiding this comment

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

Thank you - left a few change requests

Suggestion: it's probably easier to work on smaller PRs, in order to get unblocked and generally move faster


## Changes

- feat: Add Jan Hacker House event page to Docs
Copy link
Contributor

Choose a reason for hiding this comment

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

I like including the changlog in our docs - it highlights how fast our codebase moves.

However, manually copying this info is redundant, since we can just point users to the github release pages.

Is there a way to automate this, or just do a simple link-out.

Copy link
Contributor

Choose a reason for hiding this comment

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

I think we could implement GitHub API to fetch the data from the GitHub Releases page and programmatically input it into Jan AI docs.


:::

### Stable Releases
Copy link
Contributor

Choose a reason for hiding this comment

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

formatting, indentation seems off?

Copy link
Contributor

Choose a reason for hiding this comment

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

Will double check it.

sidebar_position: 3
---

# Supported Models
Copy link
Contributor

Choose a reason for hiding this comment

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

We support all GGUF models and more. I like that this page helps with SEO, by including a lot of model names, but I don't want users to get the wrong idea that these are the only models we support. Is there a way to convey both

</TabItem>
</Tabs>

2. After you run Jan, the program will take you to the Chatting window, with list of threads and each thread is a chatting box between you and the AI model.
Copy link
Contributor

Choose a reason for hiding this comment

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

Threads, not "chatting"

Copy link
Contributor

Choose a reason for hiding this comment

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

Ok I will update it.


To learn more about system requirements for your operating system, go to [Installation guide](/docs/install).

### Step 2: Select AI Model
Copy link
Contributor

Choose a reason for hiding this comment

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

This page is helpful. Thanks for including it.

<div className={clsx(styles.cards)}>
<div className={clsx(styles.card, styles.cardBluish)}>
<div>
<p>Lorem ipsum dolor</p>
Copy link
Contributor

Choose a reason for hiding this comment

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

placeholder text intentional?

Copy link
Author

Choose a reason for hiding this comment

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

Yes it is intentional. Will update it once we have the full doc complete

<img alt={"Feature logo"} src={"/img/homepage-new/bg-rocket.png"}/>
</div>
<div className={styles.cardContent}>
<h3>Praesent vel Felis Vehicula</h3>
Copy link
Contributor

Choose a reason for hiding this comment

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

placeholder text intentional?

Copy link
Author

Choose a reason for hiding this comment

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

Yes it is intentional. Will update it once we have the full doc complete

Copy link
Contributor

Choose a reason for hiding this comment

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

why do we need this?

Copy link
Author

Choose a reason for hiding this comment

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

Sorry, will remove.

Copy link
Contributor

Choose a reason for hiding this comment

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

seems like we're reincluding a lot of docusaurus default assets with this PR. why do we need these again?

Copy link
Author

Choose a reason for hiding this comment

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

Sorry, we forgot to remove them. Will remove it

Copy link
Contributor

@freelerobot freelerobot left a comment

Choose a reason for hiding this comment

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

Hey guys, not sure why I was re-requested to review this as there are unresolved comments.

Let's split this PR into smaller ones? Thank you!

Content updated for models, integration and extensions section
@0xHieu01 0xHieu01 changed the base branch from docs to docs-pena-team February 22, 2024 06:56
@0xHieu01 0xHieu01 changed the base branch from docs-pena-team to dev February 22, 2024 06:56
@0xHieu01 0xHieu01 changed the base branch from dev to docs February 22, 2024 06:57
@0xHieu01
Copy link
Contributor

Hi @cahyosubroto @aindrajaya, as a new update, we recently merge the new structure of main page to dev branch. #1941 with preview available at https://dev.jan.ai/. Thus, some of content in this PR is currently outdated when you open PR from your folk branch to docs branch. (docs branch is branch of main website jan.ai is only syncing with dev after release or urgent content update). Could you point this branch to dev branch after re-update the outdated content with new structure?

Because this PR is created from the folk repo (not have an access to Cloudflare API key deployment), when you open the PR, it won't create the preview demo. There are 2 solutions.

  • If you are already add to the repo, please create a new branch from current dev branch, then open the pull request. As team, it will auto generate preview demo with Cloudflare api key
  • Otherwise, I just created docs-pena-team may be create a pull request from your folk to docs-pena-team with update version of outdated content. Then, I can merge to docs-pena-team and create PR from docs-pena-team to dev for generate preview for easily reviewing.

cc: @0xSage @dan-jan

@0xHieu01 0xHieu01 changed the base branch from docs to docs-pena-team February 22, 2024 07:08
@aindrajaya
Copy link
Contributor

aindrajaya commented Feb 22, 2024

Thanks, @hieu-jan, for the prompt update and for notifying us about the recent merge of the new main page structure into the dev branch. I will thoroughly review the PR and make the necessary adjustments to ensure that the content aligns seamlessly with the new structure from the dev branch.
The second option is great; I will create a pull request from my fork to "docs-pena-team" with the updated version of the outdated content.

cc: @cahyosubroto

@aindrajaya aindrajaya closed this Feb 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: docs Improvements or additions to documentation
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants