Browse Source

chore(docs): Remove blog posts from master branch

They are kept on the vendure-io branch now.
Michael Bromley 6 years ago
parent
commit
1a16d83ee4

+ 0 - 80
docs/content/blog/2019-02-11-introducing-vendure/index.md

@@ -1,80 +0,0 @@
----
-title: "Introducing Vendure"
-date: 2019-02-11T10:27:46+01:00
-draft: false
-author: "Michael Bromley"
-images: 
-    - "/blog/2019/02/introducing-vendure/introducing-vendure.jpg"
-aliases:
-    - /blog/introducing-vendure/
----
-
-Vendure is a new open-source headless e-commerce framework built on [Node.js](https://nodejs.org) with [TypeScript](http://www.typescriptlang.org/) and exposing a [GraphQL](https://graphql.org/) API. Today it is available to try with its first alpha release. In this post I'll outline some of the of major features and give some background to its development.
-
-{{< figure src="./introducing-vendure.jpg" >}}
-
-## Headless Architecture
-
-The term "headless" or "API-first" refers to an architecture in which the server does not concern itself with rendering HTML pages. Instead, it exposes an API which can then be consumed by a client application which can be developed and evolve independently of the back end. This is in contrast to the traditional "monolithic" e-commerce frameworks wherein the storefront is part of the back-end framework and is typically customised via themes or templates.
-
-Headless architecture is becoming increasingly popular with the advent of powerful browser-based frameworks, mobile applications, and the trend toward progressive web apps (PWA). Several of the established e-commerce frameworks are moving towards this approach, and there is a crop of new front-end solutions such as [Vue Storefront](https://www.vuestorefront.io/) and [Deity](https://deity.io) which build upon this trend.
-
-## GraphQL 
-
-Vendure exposes a GraphQL API, through which all interactions with the back end are conducted. GraphQL offers a number of advantages over REST-like APIs, such as the ability of the client application to ask for only the data that it needs, and the improved tooling afforded by static typing. The [2018 developer survey](https://blog.npmjs.org/post/180868064080/this-year-in-javascript-2018-in-review-and-npms) conducted by npm (the package manager for JavaScript) had this to say about GraphQL:
-
-> GraphQL, tracked by its most popular client library Apollo, continues to explode in popularity. We think it’s going to be a technical force to reckon with in 2019.
-
-{{< figure src="/features-code.png" >}}
-
-## TypeScript and Node.js
-
-TypeScript is a statically-typed superset of JavaScript. Also from the 2018 npm survey:
-
-> Something of a surprise, however, was TypeScript, with 46% of survey respondents reporting they use Microsoft’s the type-checked JavaScript variant. This is major adoption for a tool of this kind and might signal a sea change in how developers write JavaScript.
-
-Since the survey quoted above, a number of major JavaScript projects have announced a switch to TypeScript, including Vue, Jest and Yarn. It is also gaining massive traction in the React ecosystem. It seems it will take the place as the de facto language for large-scale JavaScript projects. *Note: Vendure also works just fine with JavaScript*.
-
-{{< figure src="/features-dev.png" >}}
-
-## History & Motivation
-
-The development of Vendure is sponsored by [Ken Bromley Art Supplies](https://www.artsupplies.co.uk/), a leading UK art supplies retailer which has been in the e-commerce business for over 15 years, starting from a static HTML site built with [Netscape Composer](https://en.wikipedia.org/wiki/Netscape_Composer).
-
-As our business expanded, our requirements outgrew the capabilities of the available off-the-shelf e-commerce solutions (even Magento was 5 years away from its first release at that point). So I did what any over-confident youngster would do; I rolled up my sleeves, dived into a couple of 6-inch-thick PHP & MySQL books (replete with CD ROMs in the back cover) and built one myself.
-
-This solution has served us well, but over the years it became apparent that we needed something new. The e-commerce software landscaped had changed drastically in the intervening decade or so, but broadly there are two options available to retailers looking to build a store:
-
-1. A hosted, SaaS solution requiring little custom development such as Shopify or BigCommerce.
-2. A dedicated e-commerce framework to build on top of such as Magento or WooCommerce.
-
-For a number of reasons (which could fill an entire blog post) we chose the second option. So I started to look around at what e-commerce frameworks were available. For context, I've spent the past five years primarily as a front-end developer, mainly working with TypeScript. For three of those years I was part of the team building the pioneering [Gentics Mesh](https://getmesh.io/) headless CMS. So I had a number of items on my wish list:
-
-1. **Headless architecture**. During my time working on Gentics Mesh, I came to appreciate the power and flexibility afforded by this approach.
-2. **Modern workflow & tooling**. I am at home in the Node.js, npm & JavaScript world and the rich ecosystem around it. I don't want to be locked in to outdated libraries and tools dictated by the back-end framework.
-3. **A programming language I know and like to use**. TypeScript's type system is powerful, expressive and massively boosts my productivity and my confidence in my code. It would be tough to go back to working without it.
-4. **GraphQL support**. After evaluating it for a while I became convinced of its value. Its statically-typed nature is a perfect complement to TypeScript.
-5. **Easily extensible**. I need to be able to faithfully model the business requirements and processes without bending to the dictates of the tools we use.
-
-There are a number of excellent frameworks out there which answer one or two of these criteria - [Spree](https://spreecommerce.org/) for Ruby, [Sylius](https://sylius.com/) for PHP, [Saleor](https://getsaleor.com/) for Python, [ReactionCommerce](https://www.reactioncommerce.com/) for JavaScript and so on. 
-
-But I saw a gap for something that aimed for all of the above, and with Vendure I aim to fill it!
-
-## Roadmap
-
-This is an alpha release and is not intended for production use. However, I'd love to get feedback on the implementation so far. Over the coming months I'll be working on rounding out the features for a beta phase, including:
-
-* Third-party integrations for things like search, payment, tax and shipping.
-* Improved customization options.
-* Multi-channel support.
-* A reference storefront PWA app.
-* Load testing and performance tuning.
-* Expand the documentation.
-
-## Try it out!
-
-A primary goal of mine is to bring a simple and enjoyable developer experience to e-commerce development. To that end I've worked to make installation as painless as possible. As the video below demonstrates, you can be up and running with Vendure in a matter of minutes.
-
-Please [try it out]({{< relref "getting-started" >}}) and let me know your feedback!
-
-{{< vimeo id="315862294" >}}

BIN
docs/content/blog/2019-02-11-introducing-vendure/introducing-vendure.jpg


+ 0 - 44
docs/content/blog/2019-05-27-beta-release-and-roadmap-2019/index.md

@@ -1,44 +0,0 @@
----
-title: "Beta Release & Roadmap 2019"
-date: 2019-05-27T10:27:46+01:00
-draft: false
-author: "Michael Bromley"
-images: 
-    - "/blog/2019/02/introducing-vendure/introducing-vendure.jpg"
-aliases:
-    - /blog/beta-release-and-roadmap-2019/
---- 
-
-Vendure, a new headless e-commerce framework built on Nodejs, TypeScript and GraphQL, has just graduated from *alpha* to *beta*! 
-
-This means that the basic foundations of an e-commerce application are now in place - [check the demo](https://demo.vendure.io/); the GraphQL APIs are pretty stable; the codebase has been reworked into a more maintainable core/plugins monorepo; the developer experience has vastly improved with the introduction of [@vendure/create](https://github.com/vendure-ecommerce/vendure/tree/master/packages/create).
-
-## Next Steps
-
-For the remainder of the year I will be building a shop with Vendure, rounding out the features and fixing issues as I go along. By the time Vendure comes out of beta into v1.0.0, it will be production-ready and battle-tested on a shop with ~10k products. Along the way, there will be regular beta releases, which will be fully documented in the [changelog](https://github.com/vendure-ecommerce/vendure/blob/master/CHANGELOG.md).
-
-## Roadmap 2019
-
-As I build out our Vendure-based shop, I plan to work on the following features which we require:
-
-* Elastic search plugin
-* Payment provider plugins (exact providers to be determined)
-* Shipping provider plugins (exact providers to be determined)
-* More advanced promotions capabilities (free gifts, voucher codes, limited use etc.)
-* Reward points plugin
-* Product reviews plugin
-* Support for digital goods
-* More advanced control over custom entity fields
-* A database migrations story to make plugin & custom field usage safe for production
-* Reporting capabilities
-* System monitoring dashboard
-* Improved product import
-* Performance tuning
-* Improved developer documentation
-* Administrator documentation
-
-## Should I use Vendure yet?
-
-I know a number of you will be wondering whether it is "safe" to invest time building on top of Vendure right now. My honest advice is that if you have a large, critical application, you should wait until Vendure comes out of beta.
-
-However, if you have a smaller e-commerce project, the latitude to experiment and the willingness to roll up your sleeves and pitch in as an early adopter, I'd welcome your feedback and support! If this describes you, then [go get started now](https://www.vendure.io/docs/getting-started/)!

BIN
docs/content/blog/2019-08-28-summer-update/falkert-austria-michael-bromley.jpg


+ 0 - 53
docs/content/blog/2019-08-28-summer-update/index.md

@@ -1,53 +0,0 @@
----
-title: "Vendure Summer Update: Towards v1.0"
-date: 2019-08-28T10:00:46+01:00
-draft: false
-author: "Michael Bromley"
-images: 
-    - "/blog/2019/08/vendure-summer-update-towards-v1.0/falkert-austria-michael-bromley.jpg"
----
-
-After pausing for a refreshing week high in the Austrian Alps, development of Vendure continues apace. This blog post explains an upcoming change to the version numbering prior to 1.0, as well as a discussion of the remaining work to be done for the first stable release.
-
-{{< figure src="./falkert-austria-michael-bromley.jpg" caption="View from Mt. Falket, Austria. Photo © Michael Bromley" >}}
-
-## Changed numbering scheme
-
-Vendure started at version 0.1.0, and up until May this year, it had the suffix `-alpha.x`. The idea was to clearly indicate the "alpha" nature of the project, (translation: "This is barely functional - don't try to use it yet!"). According to the [SemVer spec](https://semver.org/):
-
-> A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version. 
-
-In May, I decided that Vendure was sufficiently complete to enter the "beta" phase (translation: "Still lots of work to do, but it *is* possible to build something on top of it") and added the `-beta.x` suffix which we have now. Again, the purpose of the explicit suffix was to signal the incomplete nature of the project.
-
-While Vendure is not yet feature-complete, the core API seems to have settled to a reasonable degree over the past few releases. From the next release, we'll be dropping the `-beta.x` suffix and using a regular major-minor-patch version number, starting with 0.2.0. The [relevant portions of the SemVer spec](https://semver.org/#spec-item-4) are:
-
-> 4 . Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.
-
-> 5 . Version 1.0.0 defines the public API. The way in which the version number is incremented after this release is dependent on this public API and how it changes.
-
-Up until the 1.0 release, breaking changes will be signified by an increase in the minor version (0.2.0 -> 0.3.0), and all other changes will result in a patch version increase (0.2.0 -> 0.2.1).
-
-So in summary, Vendure should still be considered to be in "beta", as per the major version of "0", despite not having an explicit `-beta.x` suffix. 
-
-## Recent progress
-
-Over the past couple of months, a new version has been released roughly weekly. Each release typically includes a whole host of new features and fixes. Here are some highlights from the recent releases:
-
-* A new [plugin format]({{< ref "docs/developer-guide/plugins" >}}) which allows any [NestJS module](https://docs.nestjs.com/modules) to be plugged directly into Vendure. This major change allows you to harness the full power of NestJS in extending the Vendure server.
-* Extended [custom fields configuration options]({{< ref "docs/typescript-api/custom-fields" >}}). Now you can extend your models with a rich set of custom data types, as well as specifying contraints, defaults and validation functions.
-* A timeline view of each Order's history, including state transitions, payments, fulfillments and notes.
-* A vastly improved product creation flow in the Admin UI.
-* Integrated shipping method testing - pass a mock order and an address to Vendure and receive all eligible ShippingMethods and prices. This is also integrated into the Admin UI and makes development and testing of complex shipping rules much easier.  
-* An [Elasticsearch plugin](https://www.vendure.io/docs/plugins/elasticsearch-plugin/) for advanced product search capabilities.
-
-See the [Vendure changelog](https://github.com/vendure-ecommerce/vendure/blob/master/CHANGELOG.md) for a detailed breakdown of each recent release.
-
-## Towards version 1.0
-
-It is my opinion that Vendure should be subject to real-world usage and validation before the release of version 1.0. I am currently building a storefront application for our business which, when it goes into production, will validate Vendure against ~10k products and on the order of hundreds of orders per day. As part of this project I'm also developing functionality around product reviews, promo codes, reporting, advanced shipping calculations, advanced product search, gift vouchers, and more. All of this is good for Vendure - some of this work will find its way back into Vendure core, some into plugins, and all of it will inform the futher design and development of Vendure's APIs to facilitate this kind of highly custom e-commerce development.
-
-In addition to this, there are a number of other Vendure-based projects currently under active development by others. All of this activity provides very focused feedback as to what are the key missing features required before we reach the 1.0 milestone.
-
-Time estimates in software projects are notoriously difficult, but my personal aim is to have my Vendure implementation completed and ready for testing by the end of this year. I would then expect a period of work rounding out any missing features and fixing bugs revealed in a real-world deployment, and then the release of version 1.0.
-
-In the meantime, please do [join us on Slack](https://join.slack.com/t/vendure-ecommerce/shared_invite/enQtNzA1NTcyMDY3NTg0LTMzZGQzNDczOWJiMTU2YjAyNWJlMzdmZGE3ZDY5Y2RjMGYxZWNlYTI4NmU4Y2Q1MDNlYzE4MzQ5ODcyYTdmMGU), where you can get any questions answered, provide feedback, and help me shape the development of Vendure.

+ 0 - 6
docs/content/blog/_index.md

@@ -1,6 +0,0 @@
----
-title: "Vendure Blog"
-date: 2019-02-06T11:27:46+01:00
----
-
-# Vendure Blog