Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
C
coko-website
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
coko-material
coko-website
Commits
25f94c0d
Commit
25f94c0d
authored
3 years ago
by
julientaq
Browse files
Options
Downloads
Patches
Plain Diff
change readme
parent
d55da79c
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Pipeline
#28774
failed with stages
in 0 seconds
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+1
-63
1 addition, 63 deletions
README.md
with
1 addition
and
63 deletions
README.md
+
1
−
63
View file @
25f94c0d
# webbook from anything
coko website based on flax
\ No newline at end of file
1.
A reading interface
A. basic text styles (designer work)
B. changing reading (reader choices)
C. size changer (warning: browser zoom + )
D. font changer (not much)
E. night mode / light mode
F. offline mode
G. Table of contents (per book)
H. Table of contents (per chapter)
I. element numbering
2.
A blog interface
→ push stuff to a backend
→ pull stuff from a backend
→ theme for the blog
→ Wax to write stuff
→ reading interface from the blog a bit different
3.
PRINT with PAGEDJS (custom size printing)
4.
pull stuff from anywhere
5.
BUILD
→ install eleventy
```
sh
npm
install
-g
@11ty/eleventy
```
→ or run eleventy
```
sh
npx @11ty/eleventy
--serve
```
## Using nunjucks for templating
IDEAS:
-
set/get reading position with cookies? (should we?) or use the browser save.
“last time you read this book, you were at this position. Do you want to resume your reading?” → netflix reading :D
search:
→ one searchindex json per book
→ one search pager per book
→ if something is found:
→ show all the content, hide any element that doesn’t have a
`mark`
element in it.
→ each element is a previewable link to the element itself is the book.
→ each element needs to have an id to be usable later
This diff is collapsed.
Click to expand it.
Preview
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment