Skip to content

Commit 47fdc27

Browse files
committed
Documented how to check local operation
1 parent 2da324d commit 47fdc27

File tree

2 files changed

+18
-1
lines changed

2 files changed

+18
-1
lines changed

Makefile

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,10 @@
33
JEKYLL_WORKDIR=target/jekyll-work
44
JEKYLL_OUTDIR=target/_site
55

6+
all:
7+
$(MAKE) html
8+
$(MAKE) jekyl-build-by-docker
9+
610
html-prepare: vim/runtime/doc vim_faq/doc target/html/doc
711
rm -f target/html/doc/*.txt
812
cp vim/runtime/doc/*.txt target/html/doc
@@ -24,7 +28,7 @@ target/html/doc:
2428
clean:
2529
rm -rf target
2630

27-
distclean:
31+
distclean: clean
2832
rm -rf vim vim_faq
2933

3034
jekyll-build-prepare:

README.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,3 +6,16 @@ There is already another similar site: <https://vimhelp.org/>.
66
The main purpose of the vimdoc-en project is to provide a handy way to see both Japanese and English versions of the help pages.
77

88
The help pages are automatically updated everyday (if there are any changes).
9+
10+
## for Developers
11+
12+
First of all, to generate everything, just run `make`.
13+
This requires Docker, so prepare it in advance.
14+
15+
Here's what's happening:
16+
17+
1. Run `make html` to generate HTML files before GitHub Pages (Jekyll) processing
18+
1. Download vim and vim\_faq
19+
2. Collect the necessary \*.txt files
20+
3. Convert the \*.txt files to \*.html
21+
2. Run `make jekyll-build-by-docker` to output all HTML files for the vimdoc-en site using GitHub Pages (Jekyll)

0 commit comments

Comments
 (0)