Comments (3)
In §2.4.2 the second example uses labels, a concept that has not yet been introduced to the reader. Maybe we can remove them from the example, so it becomes less confusing?
There are a couple of similar instances in both documents. I also found them confusing initially. It's also true that writing a specs doc without incurring in similar situations is not easy, but if it's avoidable I agree that it would be better to remove such examples and (if strictly required) provide a cross reference to the topic section (for the benefit of those who are re-reading the documents).
I think that readers tend to spend some time studying the examples in order to make sense of what they've learned so far, so I'm totally in favor for this type of revision. What do you think @alvisespano?
(Actually, this suggestion also applies to the italian documentation).
Yes, this would be better moved to an independent Issue, so I can track it under the mliestone for both documents. But first let's see what @alvisespano thinks about these changes.
EDIT: Now moved to Issue #32.
from polygen-docs.
@RBastianini, I hope you don't mind if I've edited the original post — because multiple issues are being mentioned here, I need the checklist so I can track which were fixed and which are still pending (I'm fixing all typos in a single commit, but will handle contents changes later on, to allow unrolling changes if the need arises).
from polygen-docs.
Ok for the typos and the modifications mentioned in the checklist above.
As for the wrong example with labels without having introduced them yet: yes, you're right, you can remove it. And replace it with something else without labels perhaps?
from polygen-docs.
Related Issues (20)
- Highlight Assets no Longer Required HOT 2
- Create Release v1.1.0 HOT 1
- Switch Downloader to Bash Script and Use Tar HOT 1
- PML EN: Typos in §2.3
- PML EN: Typo in §1 HOT 1
- Preparing Release 1.1.1
- Misc suggestions for section 2.5 and 2.6
- Implicit / missing details about label selection HOT 5
- Document Repo and Docs Versioning Scheme
- Release 1.1.1 Checklist
- Examples with Labels before They Are Introduced HOT 1
- Fix PP Macros to Work with Latest PP HOT 1
- Add CHANGELOGs
- Misc suggestions for section 2.7 - 2.10 HOT 3
- Revising and Improving PML Docs Contents
- Fix Examples in §2.7 Permutazioni
- PML Spec IT: Fix Title Style in §4.2.2.1
- Suggestions for sections 2.11 up to section 3 HOT 2
- Duplicated paragraph in section 3 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from polygen-docs.