GithubHelp home page GithubHelp logo

tetrakern / fictioneer Goto Github PK

View Code? Open in Web Editor NEW
72.0 6.0 6.0 103.81 MB

A web fiction theme for WordPress.

Home Page: https://fictioneer-theme.com

License: GNU General Public License v3.0

PHP 74.66% CSS 0.41% HTML 0.09% JavaScript 11.22% SCSS 13.63%
php theme wordpress wordpress-theme creative-writing web-fiction fanfiction webnovel lightnovel epub

fictioneer's People

Contributors

tetrakern avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

fictioneer's Issues

Improvement on Chapter Title System?

Hi tetrakern. Just wanna say that I appreciate everything you've been doing with Fictioneer so far. However, I do have one issue regarding the chapter title system. I'll start with what I did with my site first.

image

If you look at pic above, I prefer naming my chapters with [Series Acronym - see highlighted yellow] followed with whatever chapter number. Hwv, i don't really like to include the chapter title since it can be really long sometimes and partly because its easier for me to navigate the hundreds, if not thousands of chapters I have on my site. But! this leads to an issue that i have now.

While i don't want to include the chapter text title in main title box, and its slug... i do want to write the title somewhere else (not in the content box), preferably in a separate metabox so that it'll be reflected on both chapter page and stories page.

What I mean is something like this which was screenshot from other theme that i have (refer Pic 2, Pic 3 and Pic 4)

Pic 2: Chapter Text Title Metabox
image

Pic 3: Title reflected on chapter page
image

Pic 4: Title reflected on stories page
image

Is this something that you could consider to work on? Or is there a roundabout way I can do this?

Thanks in advance for any advice or help!

Spoiler BBCode not always working properly

The [spoiler] BBCode does not work properly when wrapping multiple lines and/or other BBCodes. The issue is somewhat softened through a bit of CSS trickery (displaying direct paragraph children inline) but it would be better to have a proper regular expression to match all cases. Or several in sequence, for that matter.

So far my nearly non-existent regex skills have failed me. Unsurprisingly.

Index Page for All Stories Available

Current stories page as seen in fictioneer demo site is not really convenient when readers want to navigate a site that has 50+ stories around. So, this is just a suggestion but will you consider create a separate stories index page with simple letters-navigation, or a different template for stories page where user can view all stories available at once?

https://fictioneer-theme.com/stories/

Improve Accessibility

Accessibility has not been a priority in the development up to 5.0 because, frankly, I was running on fumes the whole time and this felt just like another burden on a pile I was already struggling with. So I ignored the most of it. Not all โ€” I did not actively try to sabotage screen readers โ€” but I cannot say I cared much.

The most simple issues are missing aria attributes, but I suspect the tab order is not particularly great either.

Improve Spam protection

Currently, the spam protection is extremely simple (although surprisingly effective). Just a combination of limiting the number of links (can be set) and a client-side generated field (if enabled). Any bot not running JavaScript, which is the vast majority, automatically fails here. However, the field is static and could easily be fooled by more sophisticated spammers.

Anti-spam plugins should still work, so perhaps going crazy here is not necessary.

Possible Enhancements:

  • Randomized field value that must match (requires a session)
  • Hashcash (make spamming expensive)
  • Additional honeypots

Resources:

Light/Dark Mode Switcher is not visible!

Expected Behavior: image
Actual Behavior: image

Dark/Lightmode switcher should be visible but it's not! But, buttons are there! On the previous version, it was working expectedly but on the latest version, it isn't!

Bug: Shortcodes don't work as intended on child base theme

Shortcodes such as latest updates, or latest chapters, failed to show the intended count amount. Instead, it shows the default count=4.

For eg:

[fictioneer_latest_chapters count="10"]
or
[fictioneer_latest_updates count="10"]

is showing the default count="4" on child theme. In other words, only 4 cards are showing on the page.

Hwv, it works properly when I switched my theme back to Fictioneer main theme.

No backlink for suggested text comments

I believe its easier for original author to refer back to text if the suggested proofreading appended text also contains backlink to main text as seen in Picture 2.

Picture 1 (Suggested Text)
image

Picture 2 (Quoted Text)
image

Suggestion: Show support author buttons for locked chapter posts + Global password note for all chapters under specific story

Just like how we have those support buttons on regular posts, it would be cool to see them on protected posts too.

Plus, instead of just having a password note for each post, how about a global one that works for all chapters under the same story? I get that there's already a way to add a note for each chapter, but it's a bit of a hassle to repeat the same note for all my protected posts, especially since I'm juggling a tiered membership thing. Is this something you'd think about adding?

Anyway, great work as always!

Rating

How do I rate the work?

Allow metrics for non-chaptered oneshot stories

Posting oneshot/single chapter stories can be achieved by creating a chapter and parenting it to a story, but this creates unnecessary additional drilldown for readers. The story could exist as an orphan chapter too, but this means it won't appear in a list of all stories. The easiest thing to do for these is to just put the text in the story body.

The problem with this is that because the story has no chapters, it shows as having 0 total words. It would be nice if there were an option during story creation/editing to specify that this is what you are doing that measures the story body's wordcount instead of total chapters and hides the chapter count.

Follows/Reminders/Finished counts not always accurate

The objects holding the list data are not updated when a post is privated or trashed, causing the list counts to deviate. This is a minor issue which does not affect any other functionality. However, fixing this would require several database hits since you need to check whether the stored post IDs are still accessible and then update the storage. Doing this every time a list is called is just inefficient, so a better solution needs to be found.

It is hard to apply your theme for wordpress newbie

I have suggestion that you make tutorials on how to make a website using your theme that looks exactly like the demo. The documentations only told how each elements work, but do not tell where to put those elements (short codes) so I think it is better to you to make a tutorial about it.

Make comment links reliable

Currently, links to comments are unreliable and will not work unless the comment in question is on the first page and not loaded via AJAX. Because an anchor does not know about pages and certainly not about AJAX. This is not a bug, just a non-feature of the theme's comment system.

Enhancement:

  • Make comment links work in all cases. Somehow.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo 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.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.