-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add page links to Blog pagination #349
Comments
hey @vossisboss , I would love to work on this issue, can you assign? |
hey @vossisboss, I'm interested in working on this issue, can you assign it? |
Hey @vossisboss, mam can I work on this issue? |
Hi @vossisboss , I want to work on this issue. Is someone working on it already? |
hey @vossisboss can i work on this ? |
Hello Everyone. Sorry I haven't been very responsive recently. I was out for a big chunk of time dealing with a dodgy health issue that required surgery. Anyway, if you'd like to work on this issue, please go ahead and do so. You don't need permission from me to get started and I'm not planning to assign issues to particular people unless there's a project management need for that. I look forward to seeing what you all come up with! |
Can I still work on it. Is it still unresolved? |
@vossisboss Do you know if this issue is still open?? Do we have to convert the current pagination system (12 pages one by one only; we can't skip) to a pagination system like Google's? Am I right? |
Issue Fixed #450 |
Currently, our Blog pagination offers you the chance to page through all the different pages of content to get to the page you need (see screenshot). Since we only have 12 pages of content currently, that's a task that isn't too annoying.
As we add more content though, we should make it easier for people to skip to the page they need to get to. Something more similar to Google's search results pagination:
We want users to be able to get to the content they need in our blog quickly and efficiently.
The text was updated successfully, but these errors were encountered: