|
| 1 | +# Yu Lab Website Writing Policy |
| 2 | + |
| 3 | +This policy applies to every reader-facing sentence on the site, including metadata, |
| 4 | +captions, accessibility labels, news, recruitment copy, and Korean localization. |
| 5 | + |
| 6 | +## 1. Reader and author |
| 7 | + |
| 8 | +- Write for prospective graduate students and public-sector readers who do not yet |
| 9 | + know computational chemistry. |
| 10 | +- Write as a computational chemist. Lead with the question and the modeling choice; |
| 11 | + use an application system as evidence, not as a claim of domain authority. |
| 12 | +- English is the source text. Korean is a fresh rendering of the same meaning, not a |
| 13 | + sentence-by-sentence translation. |
| 14 | + |
| 15 | +## 2. House voice |
| 16 | + |
| 17 | +The reference style is compact, factual, and result-led. A research paragraph should |
| 18 | +normally move through three functions: |
| 19 | + |
| 20 | +1. Name the material behavior or scientific problem. |
| 21 | +2. State the computational approach in plain language, defining the one term the |
| 22 | + reader needs. |
| 23 | +3. Give the finding and why it changes what can be predicted or designed. |
| 24 | + |
| 25 | +Use concrete verbs such as `compute`, `compare`, `trace`, `resolve`, and `predict`. |
| 26 | +Prefer one claim per sentence. End when the finding lands; do not add a generic promise |
| 27 | +about future impact. |
| 28 | + |
| 29 | +State the claim directly. Avoid rhetorical antithesis such as `not X but Y`, `rather |
| 30 | +than`, `instead of`, `A가 아니라 B`, `뿐 아니라`, and concessive `~지만` framing. |
| 31 | +Scientific scope belongs in the subject or domain of the claim: |
| 32 | + |
| 33 | +- Write “For the salts and models examined, the results follow one comparison curve.” |
| 34 | +- Write “Training coverage defines the chemistry represented by the MLFF.” |
| 35 | +- Write “The trajectories measure reduced mobility; the model attributes it to |
| 36 | + confinement resistance.” |
| 37 | + |
| 38 | +Keep functional negation when it conveys an actual state or instruction, such as an |
| 39 | +eligibility rule, empty result, loading error, or genuinely unoccupied orbital. |
| 40 | + |
| 41 | +Avoid mission-language and AI boilerplate: `delve`, `robust`, `comprehensive`, |
| 42 | +`innovative`, `transformative`, `leverage`, `foster`, `enhance`, `pivotal`, |
| 43 | +`multifaceted`, `crucial`, `vital`, `furthermore`, `moreover`, and `it is worth noting`. |
| 44 | +Delete claims such as “X is important” unless the sentence states what X changes. |
| 45 | + |
| 46 | +## 3. Depth and length by section |
| 47 | + |
| 48 | +### Home |
| 49 | + |
| 50 | +- Purpose: identify the lab, its method-centered identity, and the class of questions it |
| 51 | + answers. |
| 52 | +- Hero description: 18–30 English words. |
| 53 | +- Section subtitle: no more than 24 English words. |
| 54 | +- Specimen captions may identify the modeling scale, system, and one size cue. Do not |
| 55 | + list software, ensembles, temperatures, runtimes, electronic-structure settings, or |
| 56 | + other protocol details. |
| 57 | + |
| 58 | +### Multiscale |
| 59 | + |
| 60 | +- Purpose: teach why several representations are needed and what each can answer. |
| 61 | +- Interactive `question`: 12–28 English words. |
| 62 | +- Interactive `concept`: 45–80 English words. |
| 63 | +- Interactive `takeaway`: 12–30 English words. |
| 64 | +- Method-page body: 220–320 English words, excluding publication citations. |
| 65 | +- Explain the tradeoff between resolution and reach. Do not teach basis sets, levels of |
| 66 | + theory, thermostat or barostat choices, integration schemes, software packages, or |
| 67 | + parameter recipes. |
| 68 | + |
| 69 | +### Research Topics |
| 70 | + |
| 71 | +- Purpose: show what the lab has actually studied, why, how, and what the papers found. |
| 72 | +- Use the paper corpus as the evidence boundary. |
| 73 | +- Keep each description near 45–55% of its August 2026 pre-edit length: |
| 74 | + |
| 75 | +| Topic | English target | |
| 76 | +| --- | ---: | |
| 77 | +| Polymer-directed self-assembly | 215–255 words | |
| 78 | +| Aqueous chemistry with ML force fields | 205–240 words | |
| 79 | +| Glass dynamics and microrheology | 150–185 words | |
| 80 | +| Colloidal structure, transport, and optics | 220–260 words | |
| 81 | +| Multiscale modeling of hydrogels | 130–165 words | |
| 82 | +| Collaborative projects | 65–90 words | |
| 83 | +| Research directions under development | 125–160 words | |
| 84 | + |
| 85 | +- Two paragraphs are usually enough for a multi-paper topic. Use a short list only when |
| 86 | + the reader is genuinely choosing among independent projects. |
| 87 | +- One informative number may remain when it changes the interpretation. A chain of |
| 88 | + temperatures, exponents, sample counts, rates, or dimensions does not belong here. |
| 89 | +- Define the evidence boundary in positive terms. Name the systems, models, observables, |
| 90 | + and training domain covered by the claim. A matching exponent supports a proposed |
| 91 | + mechanism; a direct mechanism test requires its own evidence. |
| 92 | + |
| 93 | +### Publications, People, News, Funding, and Contact |
| 94 | + |
| 95 | +- Publication summary: 25–45 English words; method plus principal finding. |
| 96 | +- PI biography, if shown: 110–150 English words; research identity before chronology. |
| 97 | +- News body: 80–140 English words unless the announcement needs instructions. |
| 98 | +- Recruitment instructions: direct, welcoming, and specific. State explicitly when |
| 99 | + beginners are welcome. |
| 100 | +- Official paper titles, grant names, affiliations, dates, and bibliographic metadata are |
| 101 | + records, not prose; preserve them exactly. |
| 102 | + |
| 103 | +## 4. Terms for non-specialists |
| 104 | + |
| 105 | +Do not use a specialist term before explaining it. Define it in the sentence where it |
| 106 | +first matters, then use the short form: |
| 107 | + |
| 108 | +- `density functional theory (DFT)`: a quantum-mechanical calculation of how electrons |
| 109 | + are distributed. |
| 110 | +- `machine-learning force field (MLFF)`: a model trained on quantum calculations to |
| 111 | + predict atomic energies and forces. |
| 112 | +- `molecular dynamics (MD)`: a simulation that follows molecular motion over time. |
| 113 | +- `coarse-graining`: grouping several atoms into one interaction site to reach larger |
| 114 | + systems and longer collective motion. |
| 115 | +- `active microrheology`: reading local mechanics from the force on a small driven probe. |
| 116 | + |
| 117 | +Definitions should serve the immediate claim. Do not turn them into textbook asides. |
| 118 | + |
| 119 | +## 5. Korean localization |
| 120 | + |
| 121 | +- Rebuild the sentence around natural Korean information order. Do not mirror English |
| 122 | + subjects, passives, or article structure. |
| 123 | +- Keep standard acronyms and names such as DFT and MLFF in English. On first use, pair an |
| 124 | + English technical term with a short Korean explanation when the acronym alone would |
| 125 | + exclude the reader. |
| 126 | +- Prefer direct verbs over nominalized chains. Remove `이를 통해`, `나아가`, `종합적으로`, |
| 127 | + `~라고 할 수 있다`, and `~에 기여할 수 있다` unless they carry real logical content. |
| 128 | +- Research and explanatory copy uses concise `-다` style. Recruitment may address the |
| 129 | + reader directly and politely. |
| 130 | +- Preserve chemical formulas, proper names, paper titles, and protected technical tokens. |
| 131 | + |
| 132 | +## 6. Evidence and review gates |
| 133 | + |
| 134 | +Every substantive sentence must pass all of these checks: |
| 135 | + |
| 136 | +1. **Purpose:** Does it belong in this section at this depth? |
| 137 | +2. **Actor or claim:** Does someone do something, or could the claim be tested and found |
| 138 | + wrong? |
| 139 | +3. **Evidence:** Is it supported by the provided paper, an official record, or the actual |
| 140 | + visualization source? |
| 141 | +4. **Definition:** Can a non-specialist understand every necessary term from context? |
| 142 | +5. **Deletion:** If the sentence disappears, does the paragraph lose information? If not, |
| 143 | + delete it. |
| 144 | +6. **Balance:** Does the sentence make its claim and evidence boundary directly, without |
| 145 | + promotional overreach or defensive retreat? |
| 146 | +7. **Specificity:** Is it concrete without drifting into protocol trivia or number lists? |
| 147 | +8. **Parallel meaning:** Do English and Korean make the same claim without sounding like |
| 148 | + translations of one another? |
| 149 | + |
| 150 | +## 7. Final polish workflow |
| 151 | + |
| 152 | +1. Finish and fact-check the English source copy. |
| 153 | +2. Write the Korean version from the settled meaning. |
| 154 | +3. Run the English copy through the site’s human-writing review rules. |
| 155 | +4. Run only the Korean prose through the pinned `im-not-ai` v2.3.0 workflow at commit |
| 156 | + `82137e858763dadb99561f194c5c00465735017b`. The tool is Korean-only; never feed it the |
| 157 | + English source or live TypeScript/JSON files. |
| 158 | +5. Protect acronyms, formulas, names, and headings in the staging document. Review the |
| 159 | + generated diff by hand and re-integrate only changes that preserve scientific meaning. |
| 160 | +6. Re-run word budgets, terminology checks, type checks, tests, build, and bilingual |
| 161 | + visual review. |
0 commit comments