community-content
community-content copied to clipboard
[REQUEST] Simple, non-SPA, non-hype-framework tutorial: ExpressJS + EJS + PostgreSQL + Strapi for Rich Text Blog.
I can't seem to find a Strapi Tutorial that doesn't use a SPA framework. I see GraphQL all over the place as well.
I'd like a tutorial that gets back to the basics, because in my opinion, a SPA is overkill for a simple rich text blog. I want a zero-hype-framework Strapi tutorial. No SPA, no GraphQL. Back to the basics.
So, Ill continue hunting for a set of instructions for quickly creating the following blog:
RichText headless blog with strapi Hosted on ExpressJS with EJS template. Preferably with a simple, low-key CSS framework such as BulmaCSS. (Such as Blog or Blog 2 templates here: https://bulmatemplates.github.io/bulma-templates/ )
Strapi-hosted Blog consists of: Blog content (Hero-image for blog post main image, RichText & content-images), Author, Date, BlogCategoryTag(s)
One user, who will write the posts.
The posts are pulled from Strapi via postgres REST API. The blog content (hero-image, richtext of text & image content, author name, date, blog-category-tags) is injected into the ExpressJS-hosted EJS template, which is formatted with BulmaCSS framework.
Keepin it reaaaallly simple and low-tech.
I really like what Strapi offers. But I think the Strapi tutorial authors are wayyy too focused on hyped up frameworks. All I see is "Yay, you can use Strapi with the latest overhyped SPA/SSG framework & GraphQL!!!" repeated ad-nauseum.
Crawl before you run. Show me the simple-to-host, minimal-webpage-file-size version first. From there, I can understand the fundamentals. But don't throw a bunch of trendy new hyped up stuff at me (SPAs, SSGs, GraphQL, MongoDB). Just show me in Node (express), and SQL. From there, trust me, I can over-engineer it too. But I think the hallmark of good engineering is simplicity and not running after shiny new objects (with unnecessarily large file sizes).
I am Seeking to use Strapi on my ExpressJS + EJS-view-template portfolio site. I'm planning on decoupling these two things: A. ExpressJS project. Hosts portfolio. Alongside this, it will host publically accessible blog content. It will pull that blog content from Strapi. But it looks like it will need to pass Strapi content into a markdown converter (to convert markdown to EJS/html), and also properly reference image files and/or file paths. I'll use BulmaCSS as it's simple. B. Strapi Project. Just a simple blog. Accessible via REST API.
hey @pmeaney would you be willing to write this article(s)? you bring up some valid points. There is room for what you're requesting.
I would like to write a tutorial for this request.
@Marktawa That's awesome! Sorry I haven't gotten around to it. Got distracted learning react-native, then ended up landing a full time job, and now working towards DevOps skills instead. Mark if you write this, I'd love to see the result! 😄
To ensure that we can review and publish articles promptly, we will start closing inactive issues after two weeks of inactivity.
I know it has been a while @Marktawa, but I just wanted to follow up with everyone here to see if anyone is still interested in writing this article. If not, we will be closing this issue due to inactivity.
Hi @PaulBratslavsky
For now I want to work on issue #670. Someone else can take over.
This a great topic, will leave it open for now.
Hello @PaulBratslavsky can I work on this
Hello @ajibade3210 Please note that due to a problem with our payment provider Wise, we are unable to pay writers with Nigerian bank accounts, as a result, we won't be accept submissions from writers in Nigeria until we find an alternative.
Due to an overwhelming articles open in the issues will be closing this for the time being to reduce number of issues.