Skip to content

Commit b1d611a

Browse files
authored
Update README.md
1 parent effcab6 commit b1d611a

1 file changed

Lines changed: 55 additions & 39 deletions

File tree

README.md

Lines changed: 55 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -1,73 +1,62 @@
1-
# Docsy Example
1+
# Elekto Documentation
22

3-
[Docsy](https://github.com/google/docsy) is a Hugo theme for technical documentation sites, providing easy site navigation, structure, and more. This **Docsy Example Project** uses the Docsy theme, as well as providing a skeleton documentation structure for you to use. You can either copy this project and edit it with your own content, or use the theme in your projects like any other [Hugo theme](https://gohugo.io/themes/installing-and-using-themes/).
3+
Welcome to the source file repository for our documentation on [elekto.io](https://elekto.io/).
44

5-
The theme is included in this project as a Git submodule:
5+
## Introduction
66

7-
```bash
8-
▶ git submodule
9-
a053131a4ebf6a59e4e8834a42368e248d98c01d themes/docsy (heads/master)
10-
```
11-
12-
This Docsy Example Project is hosted at [https://example.docsy.dev/](https://example.docsy.dev/).
13-
14-
You can find detailed theme instructions in the Docsy user guide: https://docsy.dev/docs/
15-
16-
This is not an officially supported Google product. This project is currently maintained.
17-
18-
## Using the Docsy Example Project as a template
19-
20-
A simple way to get started is to use this project as a template, which gives you a site project that is set up and ready to use. To do this:
7+
The Elekto documenation website is built with [hugo](https://gohugo.io/) and currently uses [docsy](https://www.docsy.dev/) as its theme.
218

22-
1. Click **Use this template**.
9+
## Run website locally
2310

24-
2. Select a name for your new project and click **Create repository from template**.
25-
26-
3. Make your own local working copy of your new repo using git clone, replacing https://github.com/my/example.git with your repo’s web URL:
11+
Clone this repo (or your fork) and its submodules by using --recurse-submodules option, run:
2712

2813
```bash
29-
git clone --recurse-submodules --depth 1 https://github.com/my/example.git
14+
git clone --recurse-submodules https://github.com/elekto-io/docs.git
3015
```
3116

32-
You can now edit your local versions of the site’s source files.
33-
34-
If you want to do SCSS edits and want to publish these, you need to install `PostCSS`
17+
If you accidentally cloned this repository without `--recurse-submodules` flag, you can do the following to clone the submodules:
3518

3619
```bash
37-
npm install
20+
cd docs
21+
git submodule init
22+
git submodule update
23+
cd themes/docsy
24+
git submodule init
25+
git submodule update
3826
```
3927

40-
## Running the website locally
28+
**[Optional]** If you want to write CSS/SCSS, you need to install `postcss-cli` and `autoprefixer`, run an `npm install` to install the dependencies from `package.json`.
4129

42-
Once you've cloned or copied the site repo, from the repo root folder, run:
30+
Finally, use hugo commands to start building up the site, run the following
4331

44-
```
32+
```bash
33+
# Start the server with live-reloading and with drafts
34+
hugo -D server
35+
36+
# Start the server with live-reloading and without drafts
4537
hugo server
4638
```
4739

4840
## Running a container locally
4941

50-
You can run docsy-example inside a [Docker](ihttps://docs.docker.com/)
51-
container, the container runs with a volume bound to the `docsy-example`
42+
You can run this website inside a [Docker](ihttps://docs.docker.com/)
43+
container, the container runs with a volume bound to the `docs`
5244
folder. This approach doesn't require you to install any dependencies other
5345
than Docker.
5446

55-
1. Build the docker image
47+
Build the docker image
5648

5749
```bash
58-
docker build -f dev.Dockerfile -t docsy-example-dev:latest .
50+
docker build -f dev.Dockerfile -t elekto-docs:latest .
5951
```
6052

61-
1. Run the built image
53+
Run the built image
6254

6355
```bash
64-
docker run --publish 1313:1313 --detach --mount src="$(pwd)",target=/home/docsy/app,type=bind docsy-example-dev:latest
56+
docker run --publish 1313:1313 --detach --mount src="$(pwd)",target=/home/docsy/app,type=bind elekto-docs:latest
6557
```
6658

67-
Open your web browser and type `http://localhost:1313` in your navigation bar,
68-
This opens a local instance of the docsy-example homepage. You can now make
69-
changes to the docsy example and those changes will immediately show up in your
70-
browser after you save.
59+
Open your web browser and type `http://localhost:1313` in your navigation bar, This opens a local instance of the elekto documentation's homepage. You can now make changes to the docsy example and those changes will immediately show up in your browser after you save.
7160

7261
To stop the container, first identify the container ID with:
7362

@@ -87,3 +76,30 @@ To delete the container run:
8776
```
8877
docker container rm [container_id]
8978
```
79+
80+
## Deploy you changes
81+
82+
While the above section describes how the content is built locally, [https://elekto.io/](https://elekto.io/) is built and served by [github-pages]() on github.
83+
84+
Save your local changes by commiting them and then use the `deploy.sh` script to do the deployment.
85+
86+
```bash
87+
./deploy.sh
88+
```
89+
90+
91+
## Contributing
92+
93+
We're excited that you're interested in contributing to the Elekto documentation! Check out the resources below to get started.
94+
95+
Checkout, [How to Contribute](CONTRIBUTING.md) for getting started on how to contribute and understanding the outlines the roles for Docs contributors.
96+
97+
## Getting Help
98+
99+
The elekto project is maintained by [Manish Sahani](https://github.com/kalkayan/) and [Josh Berkus](https://github.com/jberkus), Reach out to us one way or another.
100+
101+
## Support
102+
103+
Your help and feedback is always welcome!
104+
105+
If you find an issue let us know, either by clicking the Create Issue on any of the website pages, or by directly opening an issue [here](https://github.com/elekto-io/docs/issues/new) in the repo.

0 commit comments

Comments
 (0)