There’s a great list of ~75 commonly asked/searched WP tasks that can be accomplished with quick snippets instead of plugins. These snippets should make it into a CP snippet repo if one comes to fruition. Obviously, the descriptions would have to be rewritten for CP/copyright, but, it’s a nice reference nonetheless.
Nice, I think the only question is where to put it - under a Developer Guides section or else.
I think the developer Guides would not be the wrong place, perhaps one main page with inside all sub-pages listed, or, one big long page with all snippets (although that gets long with the time I think.
Perhaps:
Developer Guides
- [other menu items]
- Code Snippets
Then on the code snippets page a simple menu (links) to each a sub page, each page one snippet.
That gives room to search for snips but also room for displaying them nicely.
3 Likes
Snippet repo, I like it.
1 Like
I have called for a repo of gists before. Glad to see it getting traction now!
2 Likes
Does everyone agree with the structure?
If so - it needs no new CPT and can be implemented immediately. We can then also think about some submission process of new snippets.
I can do this quickly, while adding a New CPT takes a tad more time (not much thou)
Perhaps a new CPT is better after all because snippets aren’t necessarily only for devs. If this where a code section I’d seay “it is used both in public and admin and thus goes to the includes folder” 
Hence a standalone CPT?
Definitely a new CPT. Keep different things separate. It will make things much easier to manage.
1 Like
…and with a CPT, you also have access to core import/export. 
1 Like
Indeed, good point!
1 Like
Hi guys. New convert here. I’m not a developer, just a regular WordPress user, and so all I can do is encourage you all.
I believe in the vision of ClassicPress, and I really hope that this project will succeed. And as a sign of my faith, I’m building my first-ever self-hosted dynamic website using ClassicPress 
10 Likes
As a brand new ClassicPress user, but a fan since the beginning, I came to that conclusion the day I finally got someone to install ClassicPress for me. (I’m not a developer.)
No one should want to be running bloated Gutenberg-ready plugins if they detest Gutenberg as much as I do.
So the obvious solution is that we need at least one solid theme to use. (Is there one now?)
For the same reason I don’t want to use a Gutenberg-ready plugin I certainly don’t want to use a Gutenberg-capable theme.
So I really need a theme today – any suggestions? And then I need some capability that used to come from plugins.
Are there folks who are coding plugins or code we can have added directly? Is anyone interested in a plan to promote CP to serious bloggers?
I’m a contributor on major sites, fairly well known in some circles, and run a Small Business Mastermind Community of 40k members.
Oh, bummer. The developer has pulled the page and his site says:
“Winding Down - I am winding down my site for now. I will no longer support Canuck CP or Endorse.”
Bless you anyway! That may have been way more than I needed. But it would have been a place to start to get my site back up.
(Crash - long story - but finally got a non-CP WP person who hates Gutenberg to agree to install CP for me.)
Anyone know of any active ClassicPress theme?
I wish when a developer creates something great that they would let someone else take it on if they decide to retire.
There are so many! All the ones in the WP repo that haven’t been updated lately.
I’ve mentioned mine in the the forums before, but here it is again: twenty8teen
1 Like
That is NOT what I mean. I mean a Classic Press specific theme. One that doesn’t have all that Gutenberg crap in it. And that won’t stop working without warning?
I don’t want blocks. That is specifically what I detest about Gutenberg. I write long-form content. It has to be editable.
The first thing on the page about twenty8teen is “Block oriented by using widgets”.
If the theme works on the current ClassicPress version, it won’t “stop working without warning” because we have committed not to make any breaking changes to ClassicPress. That’s one of the differences between what we promise and how development at WP currently works.
I don’t mean because CP will break it. I mean because updates the theme developer makes because of Gutenberg may cause it to not work on CP.
Themes get updated for security reasons. What is to stop an update from causing a theme to stop working?
A security update shouldn’t have that effect because it’s just about doing the same thing in a more secure fashion.
1 Like
What exactly do you mean? The themes do not have Gutenberg crap. There is nothing in ClassicPress to be specific for a theme. I have submitted a PR to add something, but it hasn’t been merged yet.
I don’t want blocks.
None of us do. That’s why we are here. Themes don’t have blocks.
The first thing on the page about twenty8teen is “Block oriented by using widgets”.
Yes, I built my theme during the beginning of the block editor, but it came out before WP 5.0 did. Everyone wanted blocks, and it’s not a bad concept, but the editor is a poor implementation. My theme uses widgets instead. It is quite flexible. It has very minimal styling for a few block thingies, so that anyone trying Gutenberg and switching back could still have the content look good.
1 Like
I have a ClassicPress blog and a DokuWiki wiki that are both under construction — a blog-wiki combo that I’ve dedicated to supporting this project via articles, tutorials, etc. They’ll be part of my writing portfolio as a Christian blogger and technical writer.
But the work on them is slow, because:
- I have many other concerns as I build my writing business
- I’m not a developer, and I’m not yet very familiar with the WP/CP platform, and so I still need to study a lot before I can teach others
- I’m new to technical writing, and so I still need to study on that also
1 Like