Phyllux TechLearn · free
Say what is true
You sit down to write a product description. The temptation arrives immediately: make it sound bigger, smoother, more transformative than it is. Resist that temptation. Write what the thing does, not what you wish it did.
A product description tells the reader what they get. If your software exports to three file formats, say three. Not "multiple formats" or "extensive export options." Three. If a feature fails on large files, say so in the description. The reader who has those files can decide before they spend a day.
When you write about a product you made, you know its limits intimately. You know the workaround you built for the thing that should work automatically but does not. You know which button confuses people. Say these things. The person who buys anyway becomes a better user because you were honest. The person who does not buy saves money they would have asked back anyway.
Price honesty means you write the number a person would pay, in the currency you mean, before anyone sends money. On this house an hour is 120 Canadian dollars, lessons stay free, and a priced desk records a fee without charging a card. Payment waits for a written quote that is approved. If you show two ways to pay, show both numbers in the same size.
If you offer a free tier, say what it includes and what it lacks. Free for projects under 100 entries. Free without export. Free with a small logo in the footer. Whatever the constraint is, name it. Someone will pick the free tier, use it happily within those limits, and recommend you to others because you did not bait and switch.
Field House writes the number first and does not charge a card until a written quote is approved. The number starts the talk. If the job is larger or smaller, the quote says why.
Lessons are teaching. When you write that a lesson is free, it stays free. You do not require an email to access it. You do not gate the second half. You do not end with a pitch for the paid course. The lesson contains what you said it contains. If you want to mention a paid offering, you do that separately, clearly labeled.
If you write a lesson and AI helped draft sections, you say so. Not a confession. A disclosure. "OpenRouter seats drafted parts of this lesson. I checked the words on this PC." One sentence. You do not pretend the machine wrote nothing. You do not pretend you wrote nothing. The reader knows a collaboration happened and can weigh that however they weigh it.
When you use AI to draft, you remain responsible for every word. The machine makes mistakes. It invents facts. It hedges with empty phrases. You read carefully. You cut the nonsense. You check claims. You rewrite unclear sections. If something wrong gets published, "the AI wrote it" is not a defense. You published it.
Copyright is simple. You do not paste text you do not own. Not a chapter from a book. Not an article from a site. Not a poem. If you want to reference someone else's writing, you quote a short passage and link to the source. If you want to teach using someone else's material, you get permission or you use something else. You do not rationalize. You do not figure fair use covers it. You just do not paste what is not yours.
Accessibility means the reader can read what you wrote. Sufficient contrast. Text that reflows. Headings that mark structure. Alt text on images that carry meaning. No meaning conveyed by color alone. You do this because the reader deserves to read, not because you want credit for doing it. You do not write "accessibility certified" or put a badge on your site. You make the site work and you move on.
Surveillance is naming the harm when you add tracking. If you put an analytics script on your site, you say so. If you use a third party form that sends data elsewhere, you say so. If you embed a video that loads tracking cookies, you say so or you find another way to share the video. You do not hide this in a privacy policy no one reads. You do not assume consent. You tell the reader what you are doing and let them leave if they object.
Professional conduct means you write until the job is done, then you stop. A lesson does not need to be long. It needs to be complete. You do not pad to hit a word count. You do not write three more sections because you think it looks more substantial. You teach the thing, you give an example, you stop.
You are not a lawyer. You do not give legal advice. When a client asks if their project needs a terms of service, you say "I am not a lawyer, ask one." You do not research for an hour and offer your interpretation. You stop at the edge of your expertise.
You are not a philosopher. You do not write a history of ethical frameworks. You do not cite Kant. You write what to do on the page you are making today.