Very confused by the docs
See original GitHub issueQuestion
Hey guys, I just wanted to get started with spectacle, but the docs are confusing me quite a bit. These are the issues i am having:
- “Getting Started with Development” - this paragraph tells me, that all my source files have to be inside the
src/
dir. So far so good. But this also reads a bit like there should already be such a directory after installing spectacle withyarn/npm
. I assume spectacle just wants me to createsrc
myself? Edit: My bad - i completely missed the Getting Started section. It might be benefitial to move Getting Started before Basic Concepts. - The next part tells me to start a development server with ominous npm-scripts which are not yet part of my package.json. Instead I should look inside
examples/js
- I realize these are part of the spectacle repository. But how am I supposed to access these just after runningyarn add spectacle
? Ofcourse I could look inside my node_modules, but is this what you want users to actually do? - Is there a way to use spectacle with multiple markdown or even js/jsx files? I can’t seem to find anything inside the docs
Thanks in advance 😃
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:7 (2 by maintainers)
Top Results From Across the Web
I'm very confused by the docs - Dgraph - Discuss Dgraph
The docs shows this way of definining a schema once type Person { name string } type Car { regnbr string owner Person...
Read more >I'm very confused! HELP. I was writing a project and I went offline ...
I was writing a story and I went offline after my document had saved. While there was no internet I went to use...
Read more >Confused by two parts of the react docs for hooks - Reddit
React determines if the dependencies array has changed by looping over both the previous and current deps arrays, and seeing if any index...
Read more >Extremely Confused how to progress with core docs. :: Project AURA ...
Extremely Confused how to progress with core docs. What am i missing, so much needed to do basic things past the buildings you...
Read more >Painless Configuration — Confuse 1.7.0 documentation
The Confuse API is based on the concept of views. You can think of a view as a place to look in a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi Theo! Thanks for opening this issue. We spent a lot of time rewriting these docs and issues like these help us better understanding where we might have missed our mark. 🙂
It seems like our use of the phrase “Getting Started” in two places is confusing. The “Getting Started with Development” paragraph you initially refer to here is about developing against the Spectacle src. I agree, this blurb should probably be moved into a Contributing section or somewhere else, where it’s more obvious that this is about the dev process and not deck creation. If you navigate to “Getting Started” (second from the bottom in the lefthand navigation), you will find the tutorial we wrote to introduce newcomers to the library.
By “the next part” are you referring to the “Writing Your Presentation” sub section? We did link to the
spectacle-cli
repository and documentation directly in this section, but I understand if the link decoration wasn’t obvious at first read. We intended to make it more clear that use ofspectacle-cli
was just another option for developing with Spectacle, but it sounds like we missed that mark with our phrasing as well. To address the second half of your question here, it sounds like we should once again better indicate that “Getting Started: A Tutorial” will be your better bet for clear, step-by-step instructions, and not the “Basic Concepts” subsections.I don’t believe we have a process documented anywhere for using multiple markdown or jsx files, but I do know we have a couple of open issues surrounding imported slides (#871, #870) so we will need to resolve the existing bugs before we formalize a process around imported slides. I can spend some time on this today.
Hopefully I’ve addressed your concerns here, but please don’t hesitate to ask more clarifying questions. Additionally, I will try to reorg our docs to make them more intuitive to navigate. I’m sure you’re not the only one with these questions. 👍
@slorber unfortunately I didn’t (if I remember correctly - it’s been a while since I last used spectacle)