New user documentation#154
Conversation
|
Looks fine to me. Do you want to add something on top of it? |
|
I think you're right, each feature should be documented. That would go in a dedicated doc/ folder though. Or docs / ? Or keep them at root / with .md to know they are doc ? I rather have them in dedicated folder, even though it makes links more awkard (starting with Now I don't think we should doc each feature about code, as those are better kept up-to-date with tests. I made it a draft and will think about it once you give your opinion about the location, and the creation of additional test/example classes. Should I make an issue ? This way we can list what we want. |
e2baebc to
8b13b8c
Compare
|
No answer, I put the doc in |
|
Super - sounds good :-) Thanks for your efforts |
|
Usually, I call the order |
|
No, we use docs. No point in being confused, I personally don't care. And I also usually go with docs/ . |
|
@phax can you check the two md files ? Note that I also changed the root readme. |
|
Sounds all fine for me - ready to merge? |
|
I need to add part on using the plugins (in using.md) . edit : plus a part on the general architecture (overview.md) alongside the scripts present, and a part on how to produce new generators (extending.md). |
|
@phax I added tasks at the top. Can you check that you can tick the README ; then check if README changes are correct, untick it if not ? I made a second pass on starting. If you think it's good, tick it please. |
initial :
@phax please make a pass to check if that is clear. The goal is to help other people, not make them more confused :D