@@ -59,6 +59,10 @@ Exploramus, Communicamus, Crescimus<br>
5959<small style =" font-size : 1rem ; color : #555 ;" >We explore, we share, we grow.</small >
6060</div >
6161
62+ Civitas Clojure offers a hassle-free way to host and share your notebooks without the overhead of creating a new project each time.
63+ By providing a shared, well-organized platform, it lets you focus on your ideas and code while automatically publishing your work to GitHub Pages.
64+ This streamlines collaboration, increases visibility, and makes contributing simple and efficient—so you can spend less time on setup and more time creating.
65+
6266Learning technical subjects involves navigating complex webs of concepts.
6367Currently, resources for learning Clojure exist as isolated articles, unconnected tutorials, or flat lists that do not
6468capture how ideas relate to each other.
@@ -93,28 +97,24 @@ ClojureCivitas can be used as a library to simplify publishing your own garden o
9397
9498### File system organization
9599
96- | Directory | Description |
97- | ---------------------| -------------------------------------------------------------|
98- | ` src ` | Code for building a website and database |
99- | ` content ` | Notebooks (Clojure and Markdown), images, data files |
100- | ` content/posts ` | Time-anchored content (blog posts, announcements, analyses) |
101- | ` content/pages ` | Timeless or evolving content related to this site |
102- | ` content/tutorials ` | Learning materials (tutorials, workshops, guides) |
103- | ` content/talks ` | Presentation slides and related materials |
104- | ` content/ideas ` | Drafts, experiments, and work-in-progress content |
105- | ` site ` | Quarto configuration for the website |
106-
107- Each of ` posts ` , ` pages ` , ` tutorials ` , ` talks ` , ` ideas ` is a source-root.
108- These directories make it easier to distinguish blog posts from everything else.
100+ | Directory | Description |
101+ | ----------------| ----------------------------------------------------------------------|
102+ | ` src ` | Code for building a website and database |
103+ | ` content ` | Source root for notebooks (Clojure and Markdown), images, data files |
104+ | ` content/idea ` | The ` idea ` namespace hosts explorations, concepts and insights |
105+ | ` content/lib ` | The ` lib ` namespace is tied to libraries, tools, and projects |
106+ | ` site ` | Temporary build target for the Quarto website |
109107
110- Namespace selection for notebooks follow standard Clojure namespace conventions to avoid conflicts .
108+ Shared images can go in ` content/images ` , but prefer images and data files as siblings to your namespace .
111109
112- Library-related notebooks: Use the library’s namespace prefix (e.g., scicloj.clay.v2.guide.getting-started) .
110+ The difference between a posts and a page is identified by the presence or absence of ` date ` metadata .
113111
114- Disambiguation: If a topic exists, qualify with additional context (e.g.,
115- scicloj.clay.v2.guide.getting-started.intellij).
112+ Namespace selection for notebooks follow standard Clojure namespace conventions to avoid conflicts.
113+ Choose namespaces that fit with the content-first hierarchy.
114+ Files are grouped by what they’re about (not who wrote them or where they were presented).
115+ Author, date, tags and categories are included in metadata and will be used for grouping, filter of views.
116116
117- Dependent utils/modules: Nest under a parent namespace (e.g., ...getting-started.index, ...getting-started.utils) .
117+ Disambiguation: If a topic exists, qualify with additional context .
118118
119119Civitas invokes [ Clay] ( https://github.com/scicloj/clay ) to convert Clojure notebooks into Markdown files, placing them
120120in the ` site ` directory.
@@ -132,18 +132,13 @@ Goal: Align with Clojure’s code organization while allowing organic, practical
132132
133133### Topic organization
134134
135- Notebooks are tagged with a primary topic (first in list) and optional additional topics.
136-
137- Fixed top-level topics: ` :community ` , ` :core ` , ` :data ` , ` :system ` , ` :tooling ` , ` :web ` .
138-
139- Subtopics: Semi-open (e.g., : web /frontend implies : web ). Expect these to evolve.
140-
141- Topics are one tagging method; others may emerge.
142-
143- Tags want to be free:
144- https://gwern.net/doc/philosophy/ontology/2005-04-shirky-ontologyisoverratedcategorieslinksandtags.html
135+ Follow the Quarto convention of categories, tags, and keywords.
136+ Fixed categories; ` community ` , ` clojure ` , ` data ` , ` system ` , ` tooling ` , ` web ` .
137+ Tags; flexible, open-ended for finer-grained labeling (e.g. ` frontend ` , ` reagent ` ).
138+ Keywords; for SEO or search indexing; typically fewer and focused on discoverability.
145139
146- But also we can help curate the content with a good set of top-level topics.
140+ Tags and metadata are the preferred organization principle:
141+ [ Categories, Links, and Tags] ( https://gwern.net/doc/philosophy/ontology/2005-04-shirky-ontologyisoverratedcategorieslinksandtags.html )
147142
148143Goal: Constellations, not cabinets.
149144
0 commit comments