Skip to content

A fully indexed, browsable and searchable unicode explorer with wikipedia integration

License

Notifications You must be signed in to change notification settings

srobinson/unicode-wiki

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Build Status

Unicode browser with wikipedia integration

Motivation

unicode.wiki is a fully indexed, browsable and searchable dictionary of unicode characters spanning the basic and supplementary unicode planes. The project attempts to render all codepoints using sourced fonts, however in some cases you will see either a blank rendering or the missing glyph character 𞸁. Integration with wikipedia.org is implemented though the https://en.wikipedia.org/api/rest_v1 page api and https://en.wikipedia.org/w/api.php search api. Not all codepoints have a wiki page.

The idea behind the project has been lurking inside me for some years now, and was born out of an interest in unicode, World travel and the origin or languages.

I also wanted to experiment with a monorepo and decided to use this as a means of testing out Lerna and yarn workspaces. The exercise has taught me a great deal and I will be sharing my discoveries an upcoming blog.

References:

Project features

  • Indexed and searchable dictionary of unicode characters spanning the basic and supplementary planes sourced from http://www.unicode.org/Public/UCD/latest/
  • Browsable codepoints categorized following the unicode charts spec http://www.unicode.org/charts
  • Integration with wikipedia.org via api's
  • Responsive, mobile first design allowing easy browsing from any device

Core technology used

Disclaimer

This project is very early beta stage and serves as a proof of concept/exploration of Lerna monorepos and continuous integration with Travis and GKE. Should you discover any bugs please do create an issue/pr.

Deployment Description

The project consists of a web app, 3 core services and an apollo graphql server:

  • uw-app: React/Redux/Typescript web app
  • uw-api: Node/Express/Mongo REST API serving unicode meta data
  • uw-search-service: Node/Express/Elasticsearch REST API serving typeahead functionality
  • uw-wiki-service: Node/Express/Wikipedia API integration serving wiki pages and search results
  • uw-api-graph: Apollo Server/GraphQL client - act as an API gateway between client/service service/service

Other packages include:

  • uw-components: React component lib
  • uw-containers: Connected redux containers
  • uw-domain: Typescript object model
  • uw-hoc: React higher order component lib
  • uw-logging: Common logging lib
  • uw-seed: Parses UCD docs and populates Mongo/Elasticsearch
  • uw-store: Redux store/actions/reducers
  • uw-utils: Common utils lib

Commits are linted pre commit using husky to ensure a consistent messaging. commitizen is used to facilitate generating semantic-versioning commit messages.

PR branches are built/tested on Travis. Merges to master kicks off a versioning process and rolling deployments to GKE.

Local dev installation

If you already have mongo and elasticsearch running locally, skip ahead..

To quickly get a mongo/elasticsearch environment up and running

./compose.sh up

compose.sh up will install and make available the following containers:

  • mongo on localhost:27017
  • elasticsearch on localhost:9200
  • kibana on localhost:5601
  • logstash on localhost:5000

Edit compose.sh if you do not want/require kibana/logstash

  docker-compose \
    -f ./.docker-compose/mongo.yml \
    -f ./.docker-compose/elastic-search.yml \
    -f ./.docker-compose/kibana.yml \
    -f ./.docker-compose/logstash.yml \

To cleanup when you are done:

# shut down composed services
./compose.sh down

Starting the services

If you are not running mongo/elasticsearch on the following ports, update the config in .env

  • mongo: 27017
  • elasticsearch: 9200
# compile the source
yarn bootstrap

# run the web app/api server
yarn dev

# if you want to make edits with live reload
yarn watch

# alternatively run the production server
yarn start

# seed the dbs
# one time operation - seed data is persisted to disk
yarn seed

That's all for now... Comments/questions welcome. Thank you for reading.