Documentation

Your work deserves one home.

A practical guide to using Jijingibase to manage your developer workspace, publish products, gather feedback, and share what you build.

Getting started Learn the basics and open your workspace. Your workspace Organize projects and manage your work. Products and publishing Prepare projects for public sharing. Discover pages Showcase your developer profile and products. Feedback and communication Review feedback and respond thoughtfully. Environment variables Handle configuration and secrets carefully.

1. Getting started

Jijingibase is a workspace for developers to organize projects and the work around them. You can manage your lab, publish eligible projects, and give people a public place to discover your work.

Open Jijingibase and sign in or create an account if registration is available.
Explore the workspace tools available to your account.
When ready, publish the projects you want people to see and check your public Discover presence.

2. Your workspace

Your workspace is the private area where you manage projects and related tools. Use clear project names and descriptions, review changes before publishing, and check visibility settings before sharing content.

Available tools can vary as Jijingibase evolves. Follow the controls and status shown in your workspace.

3. Products and publishing

Publishing can make eligible projects visible on public surfaces, including the Discover directory. A project in your private workspace is not automatically public everywhere.

Open the relevant project in your workspace.
Review its title, summary, links, and publication options.
Choose the intended public destinations and publish using the controls provided.
Visit the public page to confirm the displayed information is accurate.

Only publish content you have permission to share.

4. Discover pages

A Discover page is a public-facing place for people to learn about a developer and explore published products. Keep public profile information and product details relevant, clear, and up to date.

Check your public page after making changes to ensure visitors see the information you intended to share.

5. Feedback and communication

Use the available feedback tools to review suggestions, understand reported issues, and communicate clearly. Keep replies professional and avoid including passwords, private keys, or other confidential information in public responses.

6. Environment variables and secrets

Environment variables help configure applications without placing sensitive values directly in source code. Keep secrets private, use the intended environment for each value, and rotate any credential that may have been exposed.

Never publish API keys, passwords, or private tokens in public descriptions or repositories.
Double-check environment names and values before saving changes.
Use the workspace's available controls and follow your provider's security guidance.

7. Privacy and visibility

Review each feature's visibility settings before publishing. Share only information intended for the public, and do not place personal data or confidential project details in public content.

8. Help and support

If you need help, visit the contact page. When reporting a problem, include the relevant page or feature and the steps needed to reproduce it, but do not send passwords or secret keys.