To access the WaveMaker documentation, see WaveMaker Docs.
- Node >= 8.x
- Git
- GitHub account. Sign up, if you do not have an account with GitHub.
- See Markdown cheat sheet to get familiar with the editor.
Note
If you are already a member of WaveMaker organization, you can skip the Fork step and directly clone the repo.
-
Fork the repo. For more information, see Fork a repo.
-
Clone the
wavemaker/docsrepo. For more information, see Cloning a repository -
Open Git/GitBash
a. Go to copied location by using the following command:
cd <path>/docs/website // Example: // cd documents/gitHub/docs/websiteb. Install the package to your local machine
npm installc. Run the site using the following command.
npm startThe step-c launches the website on the local machine automatically with the following url:
http://localhost:3000/learn
-
Locate the file from the file explorer by navigating to
learn/to edit thedoc-to-be-edited.mdin your local machine. -
Open the
doc-to-be-edited.mdin any markdown editor. For example, Visual Studio Code.
---
id: page-needs-edit
title: This Doc Needs To Be Edited
---
Edit me...For more information on how to edit docs, click here
- Create the doc as a new markdown file in
/learn, examplelearn/newly-created-doc.md:
---
id: newly-created-doc
title: This Doc Needs To Be Edited
---
My new content here..- Refer to that doc's ID in an existing sidebar in
website/sidebar.json:
// Add newly-created-doc to the Getting Started category of docs
{
"docs":
{
"Getting started":
[
"documentation-reference",
"newly-created-doc" // new doc here
{
"type": "subcategory",
"label": "App Design",
"ids":
[
"app-development/ui-design/designing-app",
"app-development/ui-design/page-creation",
]
}
...
]
...
}
}Go to the blog directory to add team blog feed.
Create a file within the blog directory with a formatted name of YYYY-MM-DD-my-blog-post-title.md. The post date is extracted from the file name.
For example, at website/blog/2019-11-01-developers-team-blog:
---
title: "Welcome to the WaveMaker Developers Blog"
author: Samantha Sam
authorURL: http://twitter.com/sam**m
authorFBID: 1212***24
authorTwitter: Sama****am
---
Your blog content..Do not directly add secrets like passwords, API keys to the sourcecode. Instead add entries in the .env file in the website directory. The values to the keys are picked up from Amplify console per environment/branch. There is a sample .env.sample file with the list of environment variables that are currently in use. Copy all the keys from the .env.sample file to the newly created .env file and populate the keys with required values for local environment testing.
Check the project dotenv for more details
Add/update the following documents on releasing a new version.
- Add a new document in the
learn/wavemaker-release-notesdirectory with version name. For example,v10.2.2. - Edit the release table in the
wavemaker-release-notesfile in the/learndirectory. - Update the
sidebar.jsonfile with the new version release notes. - Remove the
currentkeyword from the previous release notes by changing thesidebar_labeland make the new document as current.