Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
freem
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Openai/693c70a4-9498-8011-87ee-efb5576cc53d
(section)
Add languages
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==== From what you pasted, the core structure is: ==== <syntaxhighlight lang="text">wsi-website/ βββ CONTENT.en.md βββ CONTENT.zh.md βββ Dockerfile βββ README.md βββ build-meta.sh βββ docker-compose.yml βββ mkdocs.yml βββ mkdoc-01.yml βββ mkdocs-02.yml βββ docs/ β βββ index.md β βββ iam/ β βββ nextcloud/ β βββ openwebui/ β βββ tracts/ β βββ test.md βββ node_modules/ # local build dependency tree (should be gitignored) </syntaxhighlight> From a standardized project point of view for a MkDocs + Tailwind + Docker site: * β Single project root: ~/projects/wsi-website β good. * β MkDocs configs at root: - mkdocs.yml (primary) - mkdoc-01.yml, mkdocs-02.yml (alt profiles β this is acceptable as long as we document them in README.md). * β Docs under <code>docs/</code> split by domain: iam/, nextcloud/, openwebui/, tracts/ β this matches a clean domain-driven doc structure. * β Containerization present: Dockerfile + docker-compose.yml β aligns well with the βlocal β container β VPSβ pipeline. * β Meta / helper script: build-meta.sh β good practice, just make sure itβs documented in README.md. * β Bilingual content anchors: CONTENT.en.md, CONTENT.zh.md β good as top-level content map or landing copy. The only red flag, structurally: * node_modules/ is present at root (which is normal locally) but: - It must be in .gitignore so it does not go into GitHub. - If not yet added, create/extend: ``<code>bash cat >> .gitignore << 'EOF' node_modules/ site/ dist/ .venv/ __pycache__/ .DS_Store EOF </code>`` From the perspective of βStandardized Project Structure (Local & Repo)β, you are already aligned for: * Local WSL: ~/projects/wsi-website as the working copy * GitHub repo: same root structure (minus node_modules, site, etc.) * VPS deployment: Dockerfile + docker-compose.yml ready to be used in CI/CD later. If you want, next step I can help you: * Define a canonical tree -L 2 -I 'β¦' command to paste into your README.md as the βofficial project layout viewerβ, and * Normalize which MkDocs YAML is βmainβ vs βprofile variantsβ (e.g., mkdocs.yml = production, others suffixed as mkdocs.local.yml, mkdocs.dev.yml).
Summary:
Please note that all contributions to freem are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 (see
Freem:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)